content
stringlengths 7
2.61M
|
|---|
Story highlights Luiz Inacio Lula da Silva served as Brazil's President from 2003-11
He was charged as part of a wide-ranging anti-corruption investigation
(CNN) Luiz Inacio Lula da Silva, Brazil's former President, was found guilty Wednesday of corruption and money laundering charges, a representative of the federal court in Parana state told CNN.
Brazilian Federal Judge Sergio Moro sentenced Lula da Silva to nine-and-a-half years in jail. He will remain free during his appeal, and faces corruption, obstruction of justice and money laundering charges in four other court cases.
Wednesday's sentencing stems from a wide-ranging corruption investigation into the state-run oil company Petrobras, dubbed "Operation Car Wash." The accusations against Lula da Silva emerged after he left office in 2011.
Moro said the former President benefited from the renovation of a triplex in a beach town near Sao Paulo by the construction company OAS.
The charges were connected to 3.7 million reais' ($1.1 million) worth of bribes received from OAS through the beachfront apartment. In return, Lula da Silva helped the builder acquire contracts from the oil company, the prosecutor's office said.
Read More |
A rationale for the absolute conservation of Asn70 and Pro71 in mitochondrial cytochromes c suggested by protein engineering. The absolutely conserved residues Asn70 and Pro71 of mitochondrial cytochrome c have been targeted for protein engineering by semisynthesis. Neither residue has even been implicated in mechanistic schemes, and we reasoned that the conservation of this dipeptide was to fulfill a crucial structural role. Semisynthesis was through condensation by autocatalytic fragment religation of natural fragment 1-65 (H) of the horse protein and synthetic 39-residue peptides containing noncoded amino acids prepared by solid-phase methods. High yields of the purified analogs, homoserine70 and norvaline71 cytochromes c, were obtained. Functional tests revealed minor destabilization of the Hse70-containing structure, with little adverse effect in in vitro assays, but cytochrome c was essentially devoid of activity in these systems. This appeared to be a consequence of a shift, more pronounced than any yet reported, in the conformational equilibrium between the active state III conformer and the inactive, 'alkaline' state IV. The results support our view that this dipeptide is optimal for, and rigidifies, the right-angle bend between two alpha-helices, thus determining the conformation of the 70s loop that terminates in the sixth ligand Met80, and 'forcing' the coordination of iron by thioether sulfur in the presence of the adjacent more avid amine ligands of state IV. Not only is cytochrome c inactive at pH 7, but it also proves to be an extremely potent inhibitor of electron transfer by native state III, thus providing the rationale for the evolutionary conservation of a high pK for the ligand exchange reaction. |
The personal knowledge of family physicians for their patients. The physician-patient relationship has always been of interest to family physicians. This paper describes a component of the physician-patient relationship in family medicine, originally identified by Michael Balint, that operates parallel to and in conjunction with the biopsychosocial model: the family physician's personal knowledge of patients. The physician's personal knowledge of patients is a personal information network about particular patients who the physician has cared for over a series of encounters spanning several years. It is a detailed portrait painted with layers of fact, intuition, and experience and is comprised of a mix of clinical art, science, psychodynamics, and ethics. It may be factual, intuitive, or contain components of countertransference; it differs from Kleinman's concept of explanatory model in that it belongs to the physician and is employed for the benefit of the patient. It is neither paternalistic nor static. The family physician's personal knowledge for his or her patients is a seldom-measured but common component of the process of making medical, ethical, and pragmatic patient care decisions. The presence of this knowledge and its skillful use may mark one difference between novice and seasoned clinicians. Qualitative methods are most appropriate for exploring the breadth and depth of this concept, while quantitative methods are useful for studying its implications for clinical decision making and quality of care in family practice. |
Predictably, the “grassroots” and “spontaneous” women’s march wasn’t so grassroots, after all. It may have started as such, but things changed rather quickly. Ultimately, more than 50 groups, PACs, and assorted organizations backed by billionaire agitator George Soros were deeply involved in the march.
A self-declared “life-long liberal Democrat who voted for Trump” uncovered the tangled web of the money trail for the New York Times. Asra Q. Nomani explains that “the march really isn’t a ‘women’s march.’ It’s a march for women who are anti-Trump. As someone who voted for Trump, I don’t feel welcome . . . .”
Part of the problem, she contends, is that the march is neither the spontaneous grassroots rallying cry for women nor the nonpartisan love-fest it was portrayed as being. She decided to “follow the money” and discover what, if anything, that would reveal.
She writes:
Following the money, I poured through documents of billionaire George Soros and his Open Society philanthropy, because I wondered: What is the link between one of Hillary Clinton’s largest donors and the “Women’s March”? I found out: plenty. By my draft research, which I’m opening up for crowd-sourcing on GoogleDocs, Soros has funded, or has close relationships with, at least 56 of the march’s “partners,” including “key partners” Planned Parenthood, which opposes Trump’s anti-abortion policy, and the National Resource Defense Council, which opposes Trump’s environmental policies. The other Soros ties with “Women’s March” organizations include the partisan MoveOn.org (which was fiercely pro-Clinton), the National Action Network (which has a former executive director lauded by Obama senior advisor Valerie Jarrett as “a leader of tomorrow” as a march co-chair and another official as “the head of logistics”). Other Soros grantees who are “partners” in the march are the American Civil Liberties Union, Center for Constitutional Rights, Amnesty International and Human Rights Watch. March organizers and the organizations identified here haven’t yet returned queries for comment. On the issues I care about as a Muslim, the “Women’s March,” unfortunately, has taken a stand on the side of partisan politics that has obfuscated the issues of Islamic extremism over the eight years of the Obama administration. “Women’s March” partners include the Council on American-Islamic Relations, which has not only deflected on issues of Islamic extremism post-9/11, but opposes Muslim reforms that would allow women to be prayer leaders and pray in the front of mosques, without wearing headscarves as symbols of chastity. Partners also include the Southern Poverty Law Center (SPLC), which wrongly designated Maajid Nawaz, a Muslim reformer, an “anti-Muslim extremist” in a biased report released before the election. The SPLC confirmed to me that Soros funded its “anti-Muslim extremists” report targeting Nawaz. (Ironically, CAIR also opposes abortions, but its leader still has a key speaking role.)
The list is extensive and Soros ties are often a few steps removed, but Nomani persevered, discovering still more ties and hitting a nerve sufficiently hard enough to evoke a formal response from Soros’ Open Society Foundation.
Nomani continues:
Another Soros grantee and march “partner” is the Arab-American Association of New York, whose executive director, Linda Sarsour, is a march co-chair. When I co-wrote a piece, arguing that Muslim women don’t have to wear headscarves as a symbol of “modesty,” she attacked the coauthor and me as “fringe.” Earlier, at least 33 of the 100 “women of color,” who initially protested the Trump election in street protests, worked at organizations that receive Soros funding, in part for “black-brown” activism. Of course, Soros is an “ideological philanthropist,” whose interests align with many of these groups, but he is also a significant political donor. In Davos, he told reporters that Trump is a “would-be dictator.”
Professor Jacobson posted a partial list of the women’s march “partners”:
At the bottom of Nomani’s article is an editor’s note:
EDITOR’S NOTE: This story has been updated to include a statement from the Open Society Foundations.
Here is what was apparently added:
A spokeswoman for Soros’s Open Society Foundations, said in a statement, “There have been many false reports about George Soros and the Open Society Foundations funding protests in the wake of the U.S. presidential elections. There is no truth to these reports.” She added, “We support a wide range of organizations — including those that support women and minorities who have historically been denied equal rights. Many of whom are concerned about what policy changes may lie ahead. We are proud of their work. We of course support the right of all Americans to peaceably assemble and petition their government—a vital, and constitutionally safeguarded, pillar of a functioning democracy.”
Nomani concludes with the following observation:
Much like post-election protests, which included a sign, “Kill Trump,” were not “spontaneous,” as reported by some media outlets, the “Women’s March” is an extension of strategic identity politics that has so fractured America today, from campuses to communities. On the left or the right, it’s wrong. But, with the inauguration, we know the politics. With the march, “women” have been appropriated for a clearly anti-Trump day. When I shared my thoughts with her, my yoga studio owner said it was “sad” the march’s organizers masked their politics. “I want love for everyone,” she said.
Wanting “love for everyone” may well be a genuine desire among many Democrats. However, even the most well-meaning marches rooted in identity politics are not the path to that worthy goal.
While I understand Nomani’s frustration that her group was appropriated, complaining that a “women’s march” was hijacked by other left-wing groups and thus not a pure “women’s march” about women is a step shy of a meaningful condemnation of identity politics.
Until they realize that “love for everyone” entails breaking through the barriers imposed by identity politics, they will continue to be used, “organized,” and funded by persons and groups whose agenda is based on anything but love. |
<reponame>itouhiro/renamex<filename>renamex.c<gh_stars>1-10
// -*- coding:utf-8 -*-
// Time-stamp: <Feb 08 2012>
// rename all arguments as a file list
// this program will do
// - add extension to files
// - delete extension to files that already have the extension
// usage:
// put a shortcut icon of 'renamex' to
// C:\Users\<YOUR USERNAME>\AppData\Roaming\Microsoft\Windows\SendTo (Windows7)
// C:\Documents and Settings\<YOUR USERNAME>\SendTo (WindowsXP)
// how to compile (with gnupack-devel 7.02):
// gcc -O2 -mwindows -o renamex.exe renamex.c ; strip renamex.exe
#define DEFAULT_EXTENSION ".xx"
#include <sys/types.h> // stat()
#include <sys/stat.h> // stat()
#include <unistd.h> // stat()
#include <stdio.h> // printf(), rename()
#include <stdlib.h> // exit(), system()
#include <string.h> // memset(), strncpy(), strncat()
#include "getopt.h" //getopt()
int main(int argc, char **argv){
// variables for getopt
//
int opt;
extern char *optarg;
extern int optind, opterr;
// variables
//
struct stat sb;
int i;
char ext_str[256];
memset(ext_str, 0x00, 256);
// command line option
//
while((opt = getopt(argc, argv, "e:")) != -1){
switch(opt){
case 'e':
//printf("dir = %s\n", optarg);
strncpy(ext_str, optarg, 255);
break;
default:
break;
}
}
argc -= optind;
argv += optind;
// confirm existance of argv[0]
//
if(argc < 1) exit(EXIT_FAILURE);
//printf("error arg (%d) = %s\n", argc, argv[0]); exit(-1);
// confirm specifying ext_str
//
if (*ext_str == '\0'){
strncpy(ext_str, DEFAULT_EXTENSION, 255);
}
for (i=0; i<argc; i++){
if (stat(argv[i], &sb)){
printf("%s is not found\n", argv[i]);
}else{
char newname[1024];
char *p;
memset(newname, 0x00, 1024);
strncpy(newname, argv[i], 1023);
//if newname = "aa.xx", strlen(newname)== 5, strlen(ext_str)==3
p = newname + strlen(newname) - strlen(ext_str);
if (strncmp(ext_str, p, 1023) == 0){
//delete extension
*p = '\0';
}else{
//add extension
strncat(newname, ext_str, 1023);
}
if (rename(argv[i], newname)){
printf("err: rename %s to %s in fail\n", argv[i], newname);
exit(EXIT_FAILURE);
}
}
}
exit(EXIT_SUCCESS);
}
|
/*
* @Author: souravray
* @Date: 2014-10-12 01:31:40
* @Last Modified by: souravray
* @Last Modified time: 2015-03-02 07:30:44
*/
package polybolos
import (
"time"
)
// default configuration for Worker
var DefaultRetryLimit int32 = 3
var DefaultWorkerTimeout = 90 * time.Second
var DefaultAgeLimit time.Duration = 0 * time.Second
var DefaultMinBackoff time.Duration = 1 * time.Second
var DefaultMaxBackoff time.Duration = 6 * time.Second
var DefaulrMaxDoubling int32 = 0
// default configuration for Bucket
var DefaulrMaxConcurrentWorker int32 = 10
var DefaulrMaxDequeueRate int32 = 2
// constants
|
<reponame>vm-mishchenko/origin
import {ChangeDetectionStrategy, Component} from '@angular/core';
import {EventBusService} from '../../../../../application/event-bus';
import {StorageService} from '../../../../../infrastructure/storage';
import {LogoutAction} from '../../../actions/logout.action';
import {LoginDataStreams} from '../../../login-data-streams.class';
@Component({
selector: 'o-user-info',
templateUrl: './user-info.component.html',
styles: [`
:host {
display: flex;
align-items: center;
padding: 0 1rem;
}
`],
changeDetection: ChangeDetectionStrategy.OnPush
})
export class UserInfoComponent {
constructor(public loginDataStreams: LoginDataStreams,
public storageService: StorageService,
private eventBusService: EventBusService) {
}
onLogout() {
this.eventBusService.dispatch(new LogoutAction());
}
}
|
Policing Domestic Violence in Greece: The Cooperation of the Police with Women-Victims of Domestic Violence as a Key Factor in the Prevention and Treatment Addressing a complex social problem, such as intimate violence, is neither simple nor easy. Since the period of the recognition of domestic violence as an independent criminal act in the international Conventions and the law of states, police performing was one of the main factors at the center of studies. In spite of interventions in the field of Police action, several studies have so far revealed the low level of domestic violence reporting to Police Authorities and the well-held perception in the consciousness of women victims that the Police cannot provide them with meaningful help, which is complicated by the very effect of abuse on their lives and their decisions. This article presents the findings of two surveys conducted in Greece during the implementation of a European project. The findings of these studies highlight once more the reasons for under-reporting domestic violence crimes to the Police, as well as the attitudes and perceptions of police officers on the phenomenon, the assessment of the operational preparedness and the obstacles in managing relevant incidents. Introduction Domestic violence against women by their spouse/ partner is a form of gender-based violence which undermines the physical and mental health of victims, their social and economic well-being, and keeps modern societies accountable for the inability to protect the human rights of this specific population group. For several decades, field research has been developed and intervention programs have been designed to protect victims of domestic violence (DV). The interventions of feminist movements have been decisive not only in interpreting and understanding the phenomenon of intimate violence (IV), but also in criminalizing domestic violence and integrating it into the political agenda of states and international organizations. The latest developments in the recognition of crimes of IV and the implementation of measures to combat it in the Member States of the European Union are reflected in the Directive 2012/29/EU (the Victim"s Rights Directive) and the Council of Europe Convention on preventing and combating violence against women and domestic violence, also known as the Istanbul Convention 2. Yet, the rate of violence against women is still extremely high across the world. A WHO report estimates that 35% of women worldwide have experienced either physical and/or sexual intimate partner violence or non-partner sexual violence (In UNCRI, 2014: 7). In Europe, according to the EU-wide survey on Violence Against Women, commissioned by EU Fundamental Rights Agency, an estimated 13 million women had experienced physical violence in the course of the 12 months before the survey interviews (7% of women aged 18-74 years in the EU), while 3.7 million women experienced sexual violence in the same period (2% of women aged 18-74 years in the EU). Two out of five women (43 %) have experienced some form of psychological violence by either a current or previous partner (European Union Fundamental Rights Agency (FRA), 2014). All of the above considerations call for a critical look at how society and the state respond to the recording of IV cases, the criminal treatment of the perpetrators, the assistance to victims and their children, as well as the raising of awareness among citizens in order to prevent DV. For several decades, since the phenomenon has begun to stimulate the interest of researchers and concern practitioners working in the field of assistance to crime victims, a number of agencies and services have been developed to provide more effective support for victims and to attribute responsibility for violence to perpetrators. By its nature, the phenomenon calls for the co-operation of a multitude of Services of different character and diversity, not only among themselves, but also internally. Thus, when a case of IV is revealed or denounced, a number of Agencies and Services are activated (or should be activated) such as Police and prosecuting Authorities, medical and forensic Services, legal Services, counseling centers, even shelters for hosting the victims and their children. In this chain of intervention and activation of agencies, the Police have a key role, as it represent the official state institution which comes in direct contact with victims and perpetrators, collect evidence of the offense, and also activates the criminal mechanism in cooperation with prosecuting Authorities. At the same time, the Police should interconnect the victim with community or other social networks and Services that undertake to support the victims and their children at a practical level (medical care, housing, legal support, etc.) but also emotionally (empowerment, crisis management, coping with mental trauma, etc.). While the role of the Police recorded as particularly important, however, research studies show a low degree of mobilization, as well as low level of cooperation of IV victims with the Police. It is a fact that women who are being abused by their husband/spouse do not usually resort to the Police, nor as a matter of priority. As it was rightly pointed out by Birdsey and Snowball (2013: 1) the failure to report the abuse to the Police hides dangers and raises concerns because a) DV is not recorded on the actual dimensions and the perpetrators are not identified and remain unpunished, b) the high "dark number" of DV cases can lead to erroneous assessments of the extent and severity of the phenomenon, and thus to remove the social and scientific interest of its study, its degradation in the political agenda and deprivation of resources to address it, and c) the non-cooperation of victims of DV with the Police may deprive their spiritual and physical support and the benefits that could have arise from it. Research findings on the role of the Police in addressing the phenomenon of intimate violence Early studies following the criminalization of domestic violence and female abuse in Europe and the United States have highlighted the failed attempt of police interventions for a holistic approach. Police tactics usually include delaying engagement or avoiding active action on DV, due to unwillingness to interfere with matters relating to the "private sphere" of the relationship between two adults, while there are few times where compromise is sought between perpetrator and victim of abuse. Indeed, earlier surveys show that documented reports about the number of perpetrators of abuse is incomplete (Fleury-Steiner, Bybee, Sullivan, Belknap and Melton, 2006) and the rates of arrest ranging only between 7% and 15% of the cases. This recording had already been done in the past by Dobash and Dobash, who pointed out that arrests against perpetrators of violent crimes are more likely than against spouse abusers. Dawson and Holton (In Medie, 2015) point out that Police usually mediate only when serious physical attacks and death threats against women are committed. Police officers may also be indifferent to the victims or criticize them, demonstrating negative behavior that is humiliating for battered women and may lead to re-victimization. Accordingly, such behaviors often inhibit the willingness of victims to exercise their legal rights, and their trust in the Authorities (Mufti & Cruze, 2014). It appears that the Police have not been embedded in the perception of domestic violence victims as a provider of assistance. On the contrary, in many cases, victims of IV feel that their co-operation with police Authorities can put them at greater risk of escalating violence against them when the perpetrator's actions are revealed and the arrest process initiated. Recent studies show that while the overall percentage of women experience systematic violence is around 20% -30%, officially, only half of them are in contact with the Police. The probability of a failed police intervention in cases of domestic violence increases if one considers the working culture of the "security forces", which wish to participate in the prosecution of criminals and not to standard procedures that lack action (Artinopoulou and Maganas, 1996). The multidimensional role of the Police also acts as a pretext for many officers, creating room for self-action and devaluation of events that are inconsistent with their "tasks". An interesting study of Papakonstantis et al. points out that the factors influencing the behavior of police officers towards domestic violence are summarized as follows: (a) official rules and ethics; (b) professional culture (ideology-personal experiences-mentality of the Police force) (c) education, (d) the social perceptions of police officers on the phenomenon of domestic violence, (e) the stereotypes and prejudices that exist before entering the force (Papakonstantis, Antoniades, Manolidaki and Panagiotidou, 2007:295-304). Other factors that affect police decisions to deal with an incident of DV include the circumstances of the incident, the organizational status of the officers and the police station as a distinct unit, the community-area, the race /nationality of perpetrators and victims (Lee, Zhang, and Hoover, 2013). In Greece, due to the absence of official data, there is no clear picture of how the police Authorities respond to incidents of DV. More generally, there seems to be a difficulty in Police cooperation with other agencies, health professionals and victim support structures (Chatzifotiou, Fotou, and Moisides, 2016). The need for a comprehensive record of perpetrators by the Police Authorities is also highlighted. The only nationwide effort to gather statistical data shows that in 2011 in 19 of the 53 Police Head Departments of the country, 409 incidents of DV were reported with 422 offenders, of whom 94% were men (Petropoulos, Fotou, Ranjan, Chatzifotiou, and Dimadi, 2016). In December 2017, a two-year European project was launched in Greece, co-funded by the European Union's "Rights, Equality and Citizenship 2014-2020" program 3. The project was titled "ARIADNE: Developing and supporting multi-sectoral police reporting procedures to prevent and respond to domestic violence against women" and included, among others, the reporting of DV against women to the Police, managing cases in the light of the victim-centered approach, as well as police cooperation with agencies, professionals and victim support services. 4. The main findings of the surveys contacted in the project are presented below. Research results of ARIADNE project Within the framework of "ARIADNE" project has been several research actions aimed at recording the perceptions of women victims of IV, as well as the perceptions of police officers, about the role that the Police can play in the management of relevant incidents in addition with the evaluation of the cooperation between the two parties. The views of women victims of intimate violence One of the studies carried out in the framework of the project concerned interviews with eighteen women who were victims of IV and during the research period were staying in shelters for abused women, in Athens. The purpose of the interviews was to investigate the use of police assistance from the women victims in the process of reporting incidents of violence to police Authorities. The main findings of the survey show that compared to the past, the level of cooperation between the abused women and the Greek Police has improved according to the findings of previous studies (Papakonstantantis, Antoniadou, Manolidakis and Panagiotidou, 2007); Gatsas, 2008), although Police remain an agency to which women not easily addressed. In particular, the respondents said they did not seek help from official agencies, since the beginning of the violence, as they hoped that abuse would not continue. One important reason not to disclose their abuse is the fear of the offender's reaction, but above all the feeling of "helplessness", especially when they have nowhere to go / stay with their children. It seems that revealing their abuse and seeking help comes when violence becomes more serious or more dangerous for themselves and their children, when they feel their life is threatened. However, even when most of the women in the sample decided to ask for help, they approached friends and relatives, while 28% turned to a counseling center or a welfare structure and only 5, 5% approached the Police. The reluctance of victims to contact the Police appears to be largely related to their attempt to protect the image of the family (offender and children), their desire not to harm the perpetrator, or the consideration of the reporting process as a stressful event. It is worth mentioning that 17% of respondents consider that the Police / Public Prosecutor cannot help them. These findings corresponding to other studies, where it appears that victims of DV are less likely than victims of other forms of violence to contact the Police, mainly because of the fear of retaliation by the perpetrator or their attempt to protect him (Birdsey and Snowball, 2013;Felson, Messner, Hoskin and Deane, 2002). If someone does not know the characteristics of an abusive relationship, he/she will surely wondering with the victim"s attitude, which is reluctant to denounce the offender and try to protect him. As Hoyle and Sanders have pointed out, arrest policies that emphasize victims' preferences are naive if they ignore the conditions that shape the victim's preferences. The cooperation of the victims of abuse with the Police usually starts after having contact with a counseling center or entering a shelter. Victims of the sample who have come in contact with the Police (83%) report that they are usually informed that domestic violence is a criminal offense and that the crime is prosecuted ex officio. In more than half of the cases (57%) the police Authority initiated the criminal proceedings with most common actions, the automatic procedure and the referral of the victim to a forensic assessment. There remain a 43% of cases in which no criminal proceedings initiated by the Police. It is noteworthy that as reported by women in 36% of cases, the police officers encouraged victims to reconcile with the perpetrator, and very often (64%) there is no referral to victim support agencies by the Police. The sample population is positively assessing the behavior of the police officers with whom they collaborated. Typically, women said that they were polite, reassuring, showing interest and tried to help them. The general assessment of the victims for the role that the Police can play in DV cases includes, proposals on the upgraded role that Police should have in providing victim and child safety, better information, more direct response / intervention, specialized knowledge / skills to manage these incidents and support victims, both psychologically and practically, through referral to specialized professionals / Services. The views of the police officers In "ARIANDE" project, in addition to the survey of women -victims of IV, interviews with sixteen police officers (12 men and 4 women) and a focus group discussion involving eight police officers (5 men and 3 women) were contacted. The purpose of the interviews and the focus group discussion was to record the attitudes and perceptions of police officers on domestic violence against women, as well as recording through self-report and evaluation the operational readiness, and the obstacles they face in managing relevant incidents. The main findings of the interviews include the fact that the large majority (88%) of the respondents believe that domestic violence should be treated as a social problem, while 56% believe that the extent of the IV in Greece has increased, on the one hand due to information and other legal provisions favorable to the victim (ex officio offense, non-payment fee, etc.) on the other, because of the economic crisis from which the country is suffering the last ten years. They pointed out that there are still an undefined "dark" number of non-reported cases. Police officers, based on their professional experience, state that the majority of abused women resort to the police department primarily to get advice and psychological support and not to sue the perpetrator. They consider that inhibiting factors for not reporting abuse are the economic and emotional dependence of the victim on the perpetrator and the existence of children. A remarkable finding that reflects the attitudes of police officers on domestic violence is the fact that respondents in their vast majority (81%) believe that in cases of small-scale domestic violence (verbal violence or aggressive behavior), namely "light" violence, the couple should find a way to resolve its differences in order to preserve the family/ relationship. If there is a repeat of the incidents, then the couple should refer to specialists and if there is physical violence to be reported directly to the Authorities. Therefore, respondents consider that only the serious incidents of physical and sexual violence must be immediately reported to the Authorities in order to prevent further abuse. In line with this view, the majority (75%) of the questioned police officers reported that they have attempted to change the opinion of a woman in order to reconcile with the perpetrator, but only in cases of verbal / psychological violence and only when the episodes were not repetitive. Instead, their mobilization is immediate in cases of physical violence, with visible signs of physical harm, where the ex officio procedure is followed in reporting the crime. An interesting finding of the study demonstrating the low level of cross-sectoral police cooperation with institutions and services for the assistance of victims of DV, as well as the weak role the Police perform in relation to the referral of victims to other agencies, is that 50% of police respondents did not know to which agencies (counseling centers, shelters, etc,) to refer victims of abuse or state that should not have had to do so. Regarding, the assessment of the operational preparedness of the Police in dealing with cases of DV, the overwhelming majority of respondents (93%) state that they need further training on domestic violence issues. In particular, the need for training is focused on the management of incidents of abuse in an practical way (case studies and on the job training by specialized scientists and police officers), the management of the offender and the victim, the approach and communication with the victim, the way of filing and collecting data to refer the cases to the Prosecutor's Office. Finally, for the respondents, the most critical points for the Police in dealing with DV cases are (a) the shortcomings of the legal framework (for example: a case may take between 2 and 2.5 years until it is judged and by that time the offender is free, there is a serious problem for the protection of the victim after the prosecution, etc.), b) the interconnection of the Police with specialized Services and professionals as well as with public hospitals and educational institutions, c) shortages in the shelters that can hosted the victims of IV and their children; and (d) coordinating the actors involved in domestic violence. Limitations of the Current Studies Some limitations of the ARIANDE project"s studies that are presented are worth noting. Initially, although the surveys were qualitative and were based on interviews, the representativeness of the participants with respect to the ranked populations and their characteristics (abused women and police officers) should be examined with caution. Specifically, the sample of women victims of intimate violence was living during the period of the study in shelters for victims of gender-based violence. It may have been a sample of convenience, but it should not be overlooked that the interviewed women are victims who have already been mobilized and received support to cope with the crisis they are experiencing. Also, they might have contact Police as their entry into shelters means that they have experienced serious physical and / or sexual violence and their life is in dangerous. In that case, the level of cooperation is probably different because of their reality. Future research is suggested to reach also abused women who are experiencing other forms of violence (psychological, social and economic) and have less involvement in the system of aid agencies. Also, the police population should not be considered representative of the police force in Greece, as the sample had limitations on its characteristics (age, educational level, marital status) in addition to the small number of participants. Future research will be useful to examine the attitudes and perceptions of police officers about domestic violence based on gender and other socio-demographic characteristics. Conclusions The role of the Police Authorities in modern states worldwide, concerns the control and enforcement of public order, which make imperative that law and police officers operate seamlessly, equally and without discrimination towards every citizen. Particularly in the cases of DV it is necessary the Police to operate as an institution properly, in order to respond more effectively to the phenomenon. However, the action of the police towards the arrest of domestic violence perpetrator is not a panacea, nor sufficient in itself. According to Xie and Lynch the risk for the escalation of violence against the victim of domestic violence does not only depend on the arrest of the offender, but mainly from services provided to victims on the basis of their needs and the assessment of their situation. Despite the efforts that have been made in the past with regard to the role that the Police can play in preventing and managing cases of DV against women, it appears that the goals have not yet been achieved. Victims find it difficult to report the perpetrators to the Police for reasons relating to both the relationship, and the perception that they still have on the effectiveness of the Police to support and help them. On the other hand, while there is a legal obligation on the part of the Police to assist the victims of any crime and to prosecute the perpetrators, in practice there is a reluctance and weakness of the police officers to deal with the particular crime of domestic violence. The failure of the Police to respond to its role appears not only in the low rates of victims" reporting and the small number of perpetrators' arrests, but also in the incomplete recording of statistics relating to domestic violence. It is a fact that the Police play a very important role in collecting data from the early stages of the criminal proceedings. Even in cases that do not result in criminal prosecution, the collection of information and accurate recording spousal violence incidents as reported to the police, can give a more complete picture of the extent of the phenomenon and the characteristics of the involved parties. Usually, judicial statistics include more information about the perpetrator of crime, and there is a shortage of information about the victim, which can be covered through information and data collection from the Police side. Police data reveals how many recorded crimes do not reach court and the effectiveness of policies meant to protect victims of violence (European Institute for Gender Equality, 2018a). In Greece there is currently no legal or policy framework in place to regulate data collection on intimate partner violence or violence against women. According to the text of Recommendations from the European Institute for Gender Equality (2018b:2): «Developing such frameworks would be useful to support the move towards a comprehensive harmonisation of data collection across the police and justice sectors. It would also provide a catalyst for the implementation of policies which aim at improving the quality of the data collected on intimate partner violence and would strengthen the collaboration between institutions responsible for collecting data on intimate partner violence at the national level. On the other hand, the reluctance of the Police to deal with DV cases looks more like perplexity and is closely linked to the operational action and preparedness of the Police in dealing with DV cases, the culture of the "force", but also the stereotypical perceptions of the Police regarding the privacy of relationships, the social stereotypes for both genders and the real causes of the phenomenon. It is a common assumption and also a finding of the surveys conducted in "ARIANDE" project that, police officers seeking to improve cross-sectoral cooperation with other agencies and specialized training on the treatment of the DV victims. Particularly in the field of cross-sectoral cooperation must be included that the police Authorities are called upon to resolve cases of DV, to protect the victim, and other family members, in an environment where not only the victim of the abusive relationship acts, but many other groups of actors, formal and informal, which affect the life and the decisions of the victim. Informal actors include groups more or less familiar to the victim, such as the familyfriendly environment, friends, colleagues, etc. Typical (formal) actors include those organizations that are active in providing relief and support to the victim of domestic violence, counseling centers and shelters, even religious and therapeutic groups. Many factors interact with the decisions taken by an abused woman, but also with the perception that shapes her, the others and the abusive context where she lived in. The cooperation of police Authorities with other actors and professionals who play an important role in the life of the victim during the disclosure of abuse and search for assistance should be considered as a prerequisite for effective intervention. For that reason, the Police need to be encouraged, but also seek to participate in groups of professionals from various sectors (such as social workers, doctors, nurses, psychologists, lawyers, etc.) who represents agencies and Services that assist victims of domestic violence. A co-ordinate cross-sectoral group can effectively deal with various issues arising in the management of domestic violence, such as (Domestic Violence Police Guidelines, 2013: 5): Defining roles and responsibilities for actors involved in providing services to the victim Providing assistance to the victim and her children even when no criminal prosecution is involved or the case never reached the court Establish criteria for case assessment, process control and quality assurance in service provision Coordination of intervention in the case of cross-sectoral cooperation Ensuring the privacy and protection of personal data of parties involved in the exchange of information between agencies Risk assessment and planning of a safety plan for the victim and her children Develop a local strategy to prevent repeat victimization, including monitoring the progress of victims of DV Development of early intervention and prevention programs addressing DV. Regarding the training of police officers on issues related to the analysis and interpretation of the phenomenon of DV in general, and the spouse abuse in particular, it should be noted that it remains a constant demand and a challenge. We must confess that professionals who come into contact with victims of DV can understand that the reality experienced by the victims is harsh and causes intense emotional pain, regardless the presence of physical pain. Victims of domestic violence, as recorded in the literature, live in a constant crisis, experience intense feelings of fear, despair, shame, distress, emotions that express when they are in front of a professional from whom they expect to be lead to a safe path for themselves and their children. Emotional charge is transferred to the professional and intensifies especially when the woman brings with her, her children, directly or indirectly victims of abuse. In the case of professionals who have been trained, techniques are developed to decongest the professional from emotional tension. But what about the police officers who have to handle such situations? As noted in the "Handbook for Police Responding to Domestic Violence", published by the Centre for Children and Families in the Justice System (2004:2) "domestic violence intervention is one of the most difficult aspects of policing. Any training efforts have to begin with an appreciation of the perspectives of police officers" According to Horwitz et al. although the criminalization of DV has brought police officers to the front line to tackle it, little is known about the way they perceive this serious social problem and even less about the way they are experiencing their role in it. The authors, through a focus group discussion with 22 police officers, attempted to record, inter alia, their emotional response to calls to manage cases of DV. The participants reported their disappointment about the repeat nature of DV and the lack of accountability of other systems involved in dealing with cases, following police actions, such as the courts, public prosecutors and the community. Additionally, police officers said that they need more professional training and expertise, guidance from other professionals, especially regarding the treatment of the DV victim, better and more detailed information on the cases they have dealt with, including feedback and follow-up and better co-operation between other professionals (Horwitz, Mitchell, LaRussa-Trott, Santiago, Pearson, Skiff and Cerulli, 2011). Therefore, training programs aimed at police officers to improve their knowledge and to develop their skills for better management of DV cases should be designed based on real needs, as experienced by the professionals themselves. At the same time, training programs for the Police should not omit issues such as: Analysis and interpretation of domestic violence as a form of gender-based violence Analysis of the offending relationship and its physical, psychological and social effects on victims Presentation of the risks faced by victims of abuse and how these risks affect their decisions Cultivation of empathy and the "art of collaboration". Each training intervention should be accompanied by practical tools for police officers to perform their duties, advisory support from other more experienced police officers, as well as experts, control and accountability. Of course, it should not be forgotten that the success of police action in safeguarding the safety of the victim, preventing crime, investigating and detecting crimes and prosecuting offenders can only take place in steady and continuous steps, commitment to the goal by the political leaderships of the relevant Ministries and the leadership of the Police. The involved actors " must act decisively to make this an operational reality. It must become everyone"s business rather than someone else"s problem" (HM Inspectorate of Constabulary, 2014:18). |
from marshmallow import (
Schema,
fields,
INCLUDE,
RAISE,
)
class Person(Schema):
name = fields.String(required=True)
age = fields.Integer()
class Person_AdditionalProperties_True(Schema):
name = fields.String(required=True)
age = fields.Integer()
class Meta:
unknown = INCLUDE
class Person_AdditionalProperties_False(Schema):
name = fields.String(required=True)
age = fields.Integer()
class Meta:
unknown = RAISE
|
/*
* Complete the 'fizzBuzz' function below.
*
* The function accepts INTEGER n as parameter.
*/
void fizzBuzz(int n) {
for(int i=1; i<n + 1; i++){
if(i%3 == 0 && i%5 == 0){
printf("FizzBuzz\n");
}
else if(i%3 == 0 && i%5 != 0){
printf("Fizz\n");
}
else if(i%5 == 0 && i%3 != 0){
printf("Buzz\n");
}
else{
printf("%d\n", i);
}
}
} |
A bitcoin startup, Coins.ph launched Teller, a new service for its bitcoin wallet which enables money remittance without a bank account.
This feature is designed to facilitate remittances in Philippines, Indonesia and Thailand by using the blockchain technology.
The new bitcoin app will allow users to make money transfers in local currency via Coins.phaccounts by finding a third-party “teller” who will accept local currency payment in exchange for bitcoins. After the payment is made, the teller transfers the equivalent amount in bitcoins into the user’s mobile wallet for a small transaction fee. The maximum amount per transaction is limited to $50 USD.
Rremittees can withdraw money using their Coins.ph wallet or through bank and ATM withdrawals, door-to-door delivery by logistic firms or cash pick-up at partner pawnshops and remittance centres.
Addressing security level, Coins.ph CEO Ron Hose said to Tech In Asia, that the service was being rolled out first with the existing money exchangers and retail establishments that are familiar with handling such transactions. He added that these companies perform retailer screening, run identity checks on them and train them. The system is similar to Uber’s network management.
Hose also said that Teller aimed to provide basic financial access to unbanked individuals. In the Philippines over a third of municipalities don’t have any form of banking facilities. “We think this will augment banks in areas that are hard for them to serve. Our vision is to help the banks drive services there, not to replace them,” he said.
A Manila-based company, Coins.ph was founded in 2014. The company is a mobile remittance and financial services platform built on the blockchain technology. With Coins.ph the users can easily transfer cash, pay the bills, and top up their phones instantly.
CoinFox already wrote that more than 12 million Filipinos live abroad and many of them send money home, creating a huge market for remittances. There is a remittance corridor between Hong Kong and Philippines, established by Bitspark and Coins.ph, and a payroll system created by Bitwage that makes it possible for American businesses to pay their workers in the Philippines in local currency. Recently CoinFox wrote about the first bitcoin ATM installed in the Philippines.
Daria Petushkova |
def checkGameRunning(bot):
updateGameRunning(bot) |
Design of Nonlinear Controllers for Active Vehicle Suspensions Using Parameter-Varying Control Synthesis Nonlinear suspension controllers have the potential to achieve superior performance compared to their linear counterparts. A nonlinear controller can focus on maximizing passenger comfort when the suspension deflection is small compared to its structural limit. As the deflection limit is approached, the controller can shift focus to prevent the suspension deflection from exceeding this limit. This results in superior ride quality over the range of road surfaces, as well as reduced wear of suspension components. This paper presents a novel approach to the design of such nonlinear controllers, based on linear parameter-varying control techniques. Parameter-dependent weighting functions are used to design active suspensions that stiffen as the suspension limits are reached. The controllers use only suspension deflection as a feedback signal. The proposed framework easily extends to the more general case where all the three main performance metrics, i.e., passenger comfort, suspension travel and road holding are considered, and to the design of road adaptive suspensions. |
Privacy settings of memorialised profiles will be changed Facebook has announced that it will be giving friends and family the option to "memorialise" the profiles of members who have died. It follows some cases of members receiving updates about dead friends. If a user is reported as deceased, Facebook will remove sensitive information such as status updates and contacts. When reporting a death, users must offer "proof" by submitting either an obituary or news article. "When someone leaves us, they don't leave our memories or our social network," Max Kelly, head of security at the firm, wrote in the official Facebook blog. "To reflect that reality, we created the idea of "memorialised" profiles as a place where people can save and share their memories of those who've passed." Memorialised accounts will have new privacy settings so that only confirmed friends can see the profile or locate it in search. Contact information and status updates will be removed and the person will no longer appear in the newly-introduced Suggestions panel which, according to its blog it is designed "to remind people to take actions with friends who need help on Facebook". But there have been some some cases where people were 'reminded' about dead friends or relatives. "We understand how difficult it can be for people to be reminded of those who are no longer with them, which is why it's important when someone passes away that their friends or family contact Facebook to request that a profile be memorialised," Mr Kelly wrote in his blog. In separate news, Facebook has once again been targeted by cybercriminals. Security firm Websense has reported thousands of fake messages, purporting to come from Facebook Support, with a malicious payload. The fake message invites users to download a new password as part of ongoing security messages. If users click on it it will download a piece of software which could allow their machine to be taken over by malicious hackers. In one day, Websense has seen 90,000 such messages.
Bookmark with: Delicious
Digg
reddit
Facebook
StumbleUpon What are these? E-mail this to a friend Printable version |
package bg.tusofia.draw.view;
import java.io.IOException;
import java.io.PrintWriter;
import javax.servlet.ServletException;
import javax.servlet.annotation.WebServlet;
import javax.servlet.http.HttpServlet;
import javax.servlet.http.HttpServletRequest;
import javax.servlet.http.HttpServletResponse;
import org.slf4j.Logger;
import org.slf4j.LoggerFactory;
import bg.tusofia.draw.controllers.ElementsController;
import bg.tusofia.draw.controllers.SessionController;
import bg.tusofia.draw.controllers.TLController;
import bg.tusofia.draw.model.SessionParams;
import bg.tusofia.draw.utils.GF;
@WebServlet(name = "ImagePreView", urlPatterns = { "/img-prev/*" })
public class ImagePreView extends HttpServlet {
private static final long serialVersionUID = 1L;
private static Logger logger = LoggerFactory.getLogger(ImagePreView.class);
@Override
protected void doGet(HttpServletRequest request, HttpServletResponse response) throws ServletException {
String uri = request.getRequestURI();
if (uri != null && !uri.isEmpty()) {
int idx = uri.indexOf("/img-prev/");
uri = uri.substring(idx + 10);
}
response.setContentType("text/html; charset=UTF-8");
response.setCharacterEncoding("UTF-8");
PrintWriter out;
try {
out = response.getWriter();
SessionParams sParams = SessionController.loadSession(request);
out.append("<!doctype html><html>");
out.append("<head>");
out.append(ElementsController.generateHeader(request.getContextPath(),
TLController.getTl(sParams, "imgprev.header.title"), sParams));
out.append("</head>");
out.append("<body>");
out.append("\n");
request.getRequestDispatcher("/header.jsp").include(request, response);
out.append("<div class=\"draw-body-wrapper\">");
out.append("<div class=\"img-prev-wrapper\">");
out.append("<img class=\"img-prev-img\" src=\"/Draw/" + uri + "\"/>");
out.append("</div>");
out.append("</div>");
request.getRequestDispatcher("/footer.jsp").include(request, response);
out.append("\n");
out.append("</body>");
out.append("</html>");
} catch (IOException e) {
logger.error(GF.getError(e));
}
}
} |
Jessica Simpson’s little ones are keeping her spirits high as her due date for baby No. 3 nears.
“The only thing that gets me through this pregnancy is knowing I will get another one of these cuties,” the fashion designer, 38, captioned a sweet Instagram photo of daughter Maxwell, 6, and son Ace, 5, embracing on Wednesday, February 6.
Simpson has been candid with fans about the struggles she has faced in her last month of pregnancy. “After a month of sciatica pain, followed by 3 weeks of Bronchitis, I figured since my feet fit in my sneakers today … I needed to walk out a lot of anxiety!!” The “A Public Affair” singer captioned a selfie on Sunday, February 3, weeks after she posted a photo of her swollen foot, a common side effect of pregnancy.
The Employee of the Month actress also revealed via Instagram on Monday, February 4, that she’s been battling insomnia throughout her pregnancy.
In September, the MTV alum and her husband, Eric Johnson, revealed they are expecting their third child. “This little baby girl will make us a family of five,” Simpson captioned a sweet Instagram snapshot of her brood. “We wouldn’t be happier to announce the precious blessing of life.
The Dukes of Hazard alum hosted a chic, birds nest-themed baby shower in January after revealing that she and Johnson will name their second daughter Birdie. |
A visual approach to the economic evaluation of vaccines: opening the health economic black box ABSTRACT Objectives The economic evaluation of vaccines has attracted a great deal of controversy. In the academic literature, several vaccination advocates argue that the evaluation frame for vaccines should be expanded to give a more complete picture of their benefits. We seek to contribute to the debate and facilitate informed dialogue about vaccine assessment using visualization, as able to support both deliberation by technical committees about the substance of evaluation and communication of the underlying rationale to non-experts. Methods We present two visualizations, an Individual Risk Plot (IRP), and a Population Impact Plot (PIP), both showing the beneficiary population on one axis and the degree of individual benefit and cost of an individual dose on the second axis. We sketch out such graphs for 10 vaccines belonging to the UK routine childhood immunization schedule and present our own analysis for the rotavirus and meningitis B vaccines. Results While the IRPs help classify diseases by morbidity and mortality, the PIPs display the health and economic loss averted after introducing a vaccine, allowing further comparisons. Conclusion The visualizations presented, albeit open to provide an increasingly complete accounting of the value of vaccination, ensure consistency of approach where comparative judgments are most needed. Introduction Vaccination has an enormously successful track record in public health. Diseases which were previously a scourge in even the most developed countries are now a distant memory. Vaccines can take credit for the elimination of smallpox and the near elimination of polio, two diseases which blighted the lives of millions and killed millions more throughout human history. Most commentators see the development of a vaccine as humanity's best hope of permanently defeating Covid-19. More than any other technology, vaccines truly deserve to be designated as a miracle of modern medicine. Nevertheless, not all vaccines merit deployment everywhere. This may be because of the local disease burden: there is no need for universal dengue vaccination in the west of Scotland, for example, as the climate is inhospitable to Aedes aegypti and Aedes albopictus which are the principal vector for this disease. However, it may also be because of constraints imposed by the local financing situation: lack of funding is a critical reason for the poor utilization of influenza vaccines in low-and middle-income countries. Thus, as with other technologies, vaccines are and should be subject to some form of economic evaluation, to determine whether they represent value for money for the funder. The economic evaluation of vaccines, however, has also attracted controversy in both the scholarly and lay circles. There exists disagreement to what extent the social benefits of a proposed immunization should be factored into the decision-making. For example, a new immunization program benefits not only the recipients but to their families and carers, so there is an argument for broadening the scope of the analysis to cover these benefits. Public perceptions of the benefits of vaccines are complex and labile, as highlighted by the phenomenon of widespread vaccine hesitancy but also by (at least in the UK) deep public concern about the lack of access to meningitis B immunization. To contribute to the debate on the evaluation of vaccines, we propose a visualization that may facilitate informed dialogue among the various parties. Data visualization is a useful tool in healthcare decision-making by effectively distilling down data so that it can be digested both experts and the patients. Our visualization design carries sufficient data that can support both the deliberation by technical committees about the substance of the economic evaluation yet is simple enough for communication to non-expert stakeholders. In this paper, we describe the design of the visualization and the data encoded in it. The core idea of our graph is to show the beneficiary population on one axis and the degree of individual benefit and cost of an individual dose, measured as QALY (Quality-Adjusted life years) loss on the second axis. We use the work by Panovska-Griffiths et al. to generate the graphs for 10 vaccinepreventable diseases currently in the UK routine childhood immunization schedule and present our own analysis of the rotavirus and meningitis B vaccines. Furthermore, the visualizations which we present in this paper could be developed in several ways to incorporate many of the factors which other authors have suggested are important to take into account. Background Lately, several commentators have highlighted the limitations of current evaluation frameworks in accounting for the range of benefits flowing from immunization programs. Previous valuations, it is argued, failed to reflect the full magnitude of the overall health, social and economic outcomes of vaccines, and focused heavily on a narrow subset of factors, that present fewer methodological challenges and for which there is greater data availability. These are: Health gains: the reductions in morbidity and mortality yielded. Healthcare cost savings: the direct (medical and nonmedical) costs averted for care providers and private citizens, due to fewer episodes of illness. Productivity gains ('care-related'): indirect costs associated with the productivity losses that would have been incurred due to absenteeism (working or schooling days lost) by those seeking and providing care. Drawing on several frameworks and lines of research, we provide a comprehensive taxonomy (Fig. 1) and description of these novel elements of value. First, the scope of valuation efforts may be widened to include secondary health endpoints for vaccinated individuals, thus accounting for the reduced probability of developing comorbidities or nosocomial infections that may co-occur with the primary vaccine-preventable disease (VPD). Socalled 'health spill overs', given that health-related consequences (e.g. physical or emotional strain, anxiety, grief) accompany productivity losses for those who take on caring responsibilities within the social network surrounding ill individuals, could also be considered. Secondly, the evaluation frame could be extended to include 'outcome-related' and 'behaviour-related' productivity gains. The prevention, during childhood, of the long-term physical or neuro-cognitive impairments of numerous VPDs can enhance the wellbeing and human capital accumulation of an individual over the lifespan. Also, household resources may be devoted to meet the developmental needs of fewer children, who, being vaccinated, have greater survival chances. The resulting demographic dividend further may facilitate parental labor participation. Additionally, the consequent boost in economic growth and workforce productivity Article highlights Economic evaluation of vaccines needs to encompass a more complete picture of the benefits of an immunization program Our visualization designs allow these benefits (social and economic) to be expressed and compared across different programs The visualizations are demonstrated on 10 vaccines, with emphasis on rotavirus and meningitis B results in greater net transfers to public budgets. Finally, a country with higher vaccine coverage and reduced transmission rates of VPDs benefits from greater social and political stability, while better attracting flows of financial and human resources. Third, compared to other health interventions, vaccination stands out for particularly striking health-related community externalities (or 'ecological effects'). By limiting the occurrence and spread of VPDs, immunization schemes ensure: that unvaccinated individuals incur indirect protection, thanks to the health choices of those immunized ('herd effects'); a reduction in the consumption of antibiotics and of the pace at which antimicrobial resistance (AMR) develops; and a reduction in risk and fear of being exposed to VPDs outbreaks. Individuals, whether immunized or not, may derive from vaccine protection greater peace of mind and gains in well-being due to reduced anxiety and worry. This factor can be particularly valuable to the society and partially operationalized in terms of 'insurance value'. Furthermore, all the positive externalities yielded by advances in the field can be appropriated by those who have not directly contributed to them, such as future generations ('scientific spill overs'). Conversely, there might be unintended negative externalities on population health too (shown in the square orange boxes), such as a raise in disease serotypes other than those covered by a vaccine and a shift in the age distribution of infection, to the expenses of age groups that might be more severely affected by infectious diseases. Overall, the aforementioned factors jointly contribute to short-and long-term changes in macroeconomic conditions, by avoiding the shocks exerted by VPD outbreaks or shifting over time overall labor force participation and levels of productivity, health, well-being, and equity. Finally, further complicating the broad picture, valuations and decision-making processes concerned with prioritization of immunization programs are required to account for how health preferences are informed by the value attached to definite health gains and risk reductions and to embed routine/crisis healthcare management considerations. Empirical evaluations should embrace the possibility that the choices of individuals or entire communities are influenced by: Value of hope: individuals who value hope, as risk-takers, might prefer the intervention displaying higher uncertainty as regards the likelihood to gain an equal amount of health gains. Severity of disease: individuals might value differently equivalent gains in health if gained by preventing a single episode of highly severe illness, rather than multiple milder episodes. Option value: health gains being equal, individuals might prefer interventions that extend life, rather than improving its quality, to have greater chances to access more effective treatments and technologies yielded by possible future advances. Inequity aversion: according to the values endorsed at the societal level, funding decisions might embed the will to mitigate health, social and economic inequalities, to the benefit of age or socio-economic groups disproportionately burdened by VPDs. Catastrophe aversion: decision makers may have heightened concerns related to epidemic outbreaks that hit particularly harshly restricted geographical areas or escalate rapidly. Having illustrated the components that populate this extended framework, we now describe the visualization approach developed. Remarks on how it can accommodate for a number of the nonstandard factors just outlined are drawn in the discussion. Methods This section describes the visualization. Developing from a basic model which captures individual impact of disease, we progressively add new pieces of information about the health impact, in terms of QALY loss, of the disease on the population as well as the economic impact of the immunization program. The sources of data which we use to generate the plots will also be described. Visualization design In this paper, we present two plots, an Individual Risk Plot (IRP) and a Population Impact Plot (PIP). The IRP communicates the QALY loss suffered by a non-fatal case of the disease in question along with the fatality rate of the disease. The summary plot consists of a horizontal red bar, with the height taking the number of QALY loss and a vertical blue bar, where the width represents the fatality rate, the x-axis being in the percentage of the population affected. The width of the red bar and the height of the blue bar will be used later to convey more information in the PIP. The plot illustrates the possible impact of the disease on the individual patient and also allows one to compare the health impact over different diseases by comparing the dimensions of the two bars. The QALY losses for the diseases are calculated from global records of disability weights D using the equation with a discount rate r of 3.5% [4, and t as the duration of the disease in question. Beyond the individual health impact, it is important for the general public and decision makers to know the population health impact. To build the PIP, we change the x-axis to be the absolute number of patients annually, the width of the red bar to be the number of non-fatal cases, and the width of the blue bar to be the number of fatal cases. The Quality of Life lost will be expressed in days (QALD), instead of years (QALY) for reasons to be explained in a bit. The height of the blue bar is the QALD loss for a fatal case. The QALD loss must be calculated for the fatal cases using equation where the duration is taken to be the difference between life expectancy and the estimated age of death from the disease. Due to the difference in magnitude of how diseases affect the population, a log scale is used, as otherwise some bars would be too small to read. 1 Another parameter that can be conveyed in this scale is the cumulative QALD loss for fatal and non-fatal cases suffered in the population. Prior to applying the log scale, this parameter is the area of the blue and red bar, respectively. The logarithm translates this parameter from an area to a length, by which we may compare the population QALD loss. This length is highlighted along the x-axis. The higher the cumulative QALD loss in the population, the longer this line would be. The Quality of Life is measured in days in order to generally ensure that we deal with positive values after taking logarithm. However, if one can be reasonably sure that QALY is greater than 1, then this conversion will be unnecessary, provided that any comparison between multiple diseases employs consistent units. Information about costs of the immunization program is expressed in the lower right quadrant of the plot. We divide the costs of the vaccine into the product cost per one immunization course from the pharmaceutical company and the human costs of administering the disease. These are expressed by the height of a green and yellow bar, respectively. However, the existence of an immunization program also leads to a trade-off in the sense that the cost of the program can offset the future costs spent on the treatment of patients, including costs of GP visits, ambulances, hospitalizations, etc. One way to visualize the cost saved is to have a brown bar expressing the cost of treatment in height and number of cases averted in width. In the results section, we generate IRPs with the basic design for a series of diseases based on data collected in. We use the size of the red and blue bars to categorize a list of diseases according to their morbidity and mortality. The PIP is then generated for the diseases meningitis B and rotavirus. Data sources The data required in generating the plots are from a variety of government, academic, and business sources. For our initial plot design, we use the data listed in, the sources from which are listed in Table 1a. In our subsequent detailed visualization, we acquire the data on disease QALY loss, fatality rates, vaccine costs, the staff costs for administering vaccines, and the cost saved in the implementation of vaccines (see Table 1b). QALY loss for fatal cases are obtained by using equation, with the duration of diseases set as the difference between average life expectancy and estimated age of fatality. Priority of the sources is given to government records and then to reports and studies conducted in the UK. In absence of UK specific data, we refer to studies in highincome countries using the same vaccines as the UK. Assumptions made about QALY loss and healthcare costs are also listed (see Table 1c). Due to a lack of studies on QALY loss and associated parameters post-immunization for some diseases, some parameters will remain unchanged in our construction of the plots. Results In this section, we give several examples of IRPs and PIPs. A series of IRPs is produced for a list of diseases, where the QALY losses and mortality rates can be found in Appendix B of. These allow us to classify these diseases by morbidity and mortality. We then provide pre-vaccination and post-vaccination PIPs for the diseases rotavirus and meningitis B. Individual risk plots (IRPs) As presented in the IRPs (see Figure 2), we can easily see that how the profile varies for the different diseases. The red bar allows us to compare the damage done by the disease on surviving patients; polio and meningitis causes the most QALY loss for patients whereas rubella, hib and rotavirus affects patients the least. The height of the blue bar is roughly the same, indicating that the average age of death from the diseases is roughly the same; the one exception is pneumococcal disease for which death occurs with similar likelihood over different age groups compared to the others that mainly affect infants. The width of the blue bar compares the casefatality rate of the disease, with tetanus and meningitis having the highest fatality. Morbidity and mortality. Using these plots, we can categorize the diseases according to morbidity and mortality, the former defined by the average QALY loss of surviving patients and the latter by the QALY loss of patients that die. Specifically, we can create four categories of high/low mortality against high/low morbidity as presented in the matrix below (Table 2). Diseases with low mortality and morbidity are relatively unthreatening diseases from which most patients can easily recover from. High mortality but low morbidity can point to a disease that has effective treatment but access to treatment may be limited or time-sensitive. High morbidity, low mortality diseases are those that are not quite as deadly but take time to recover from or leaves the patient with lasting effects. The final category of high mortality, high morbidity are the most serious diseases. Rotavirus and Men B Our PIP displays (Figure 3) are demonstrated for patients suffering from rotavirus and those from meningitis B (henceforth, 'men B') before and after the introduction their respective vaccines. We focus on these two diseases because they occupy the two ends of the spectrum with respect to morbidity and mortality, as seen from the matrix. To highlight the benefits of vaccination, we use a lighter purple and the orange to represent the post-vaccination QALD losses for fatal and non-fatal cases, respectively. QALY loss is calculated by the formula in with disability weight from using the life expectancy recorded in Rotavirus Prevalence UK Public Health England Detailed record for number of cases per year for the past decade. Rotavirus Fatalities pre vaccination England and Wales Department of Health Jit et al. [ QALY loss is calculated by the formula in with disability weights in using the life expectancy recorded in. Men B cost of vaccine UK FiercePharma A report on the deal between Health Minister and pharmaceutical company GSK. Rotavirus cost of vaccine UK GSK List price for vaccine per dose on pharmaceutical company GSK website. Vaccine staff cost UK Mokiou The only study that focuses on vaccination administration costs. Men B cost saved UK H. Christensen et al. The study lists the estimated public health response cost for a case of men B. Rotavirus cost saved UK NIHR Study shows the reduction in number of GP, hospitals, and emergency departments and their corresponding savings. The only costs relating to the vaccine and its implementation are healthcare costs. These two bars are smaller compared to the pre-vaccination blue and red bars for both rotavirus and men B. In particular, for rotavirus, the fatality rate is zero, represented by the dotted purple line. Due to the lack of studies regarding QALD loss for both pre and post vaccination, the QALD losses are taken to be the same. Between the two diseases, men B has a higher fatality rate (wider blue and purple bars) and has a much greater impact in QALD loss for patients (taller red and orange bars), whereas rotavirus is more prevalent (longer red and orange bars). With these added features, we can make several more comparisons. The highlighted intervals help us compare the population QALD loss for the two diseases, with a longer interval yielding a higher cumulative QALD loss. The intervals are calculated as logarithm of the area of the rectangle if the data were presented on a natural scale. The cumulative QALD loss obviously decreases (comparing intervals, purple and orange shorter than blue and red) after introducing the vaccine. Men B, due to a comparatively high fatality rate, inflicts a greater cumulative QALD loss than rotavirus for fatal cases (both purple and blue lines are longer for case of men B) and non-fatal cases (both orange and red lines are longer for case of men B) although men B is less prevalent. We remark here that when QALD loss does not change postvaccination, which is true in our case, we can conclude that there is a greater proportional decrease in cumulative QALD in rotavirus due to a greater drop in cases. However, if QALD does change post-vaccination, we can compare the proportional decrease in cumulative QALD by comparing the length differences between intervals. For example, in non-fatal cases, the difference between the length of red and orange intervals is greater for rotavirus. On the bottom right quadrant, we can compare the costs of vaccine production per course, which is three doses for men B at £20 per dose and two for rotavirus at £34.76 per dose, and the administration cost. The similar size of the green bar means one immunization course costs roughly the same, while the human resource cost of administering the vaccine, due to the difference in doses, is more expensive for men B. The human resource cost, however, is difficult to attribute to any single vaccine because multiple vaccines can be scheduled at one appointment. Men B also surpasses rotavirus in treatment cost saved per case averted, but the number of averted cases is lower; in total, the amount of treatment cost saved by the rotavirus vaccine is higher than that of men B. Due to the cost saved per case averted being much higher than that of rotavirus, we opted to not plot the entire bar in order to keep the green and yellow bars visible. Discussion Our approach shows many of the positive features highlighted by advocates of visualization tools. The IRP and PIP designs allow users to make judgments on immunization programs as well as quick comparisons across diseases, without loss of the essential details such as the prevalence and costs. Hence, users can make informed decisions at the level of detail they choose to extract from them. Furthermore, the design is flexible in the way and amount of data presented. If comparing over multiple diseases, all comparisons are valid as long as the scales are kept consistent, which may be necessary to make the bars visible when dealing with diseases of low morbidity and/or mortality. Additionally, our designs are also customizable. In this respect, as long as reliable input data are available, our models easily lend themselves to the incorporation of additional data such as rates of GP visits, hospitalizations, or ER visits and their respective QALY losses, or saving items other than the direct healthcare costs averted, should such information be available. Also, provided that the budget holders' remit is to allocate available resources to pursue socially desirable though not strictly health-related objectives, 'care-related' productivity gains accrued to immunized individuals and their potential carers could also be included. Similarly, in line with the goal of maximizing the entirety of population health, QALY losses potentially incurred by carers of infected individuals, if measured (e.g.), can be easily incorporated. Expert opinion We began the paper by noting that the evaluation framework for vaccines is disputed, and several commentators advocate for additional value dimensions to be included in the costeffectiveness calculations. While it may be desirable to have a more complete accounting of the costs and benefits of vaccination, a major risk form this agenda is that the body of cost-effectiveness studies for vaccines become even less comparable than they already are. We believe that the most urgent challenge facing the research community, rather than trying to develop the most complete possible index of benefits for vaccine programs, is to develop a framework which surfaces the logic of the cost-effectiveness calculation and makes it possible to sense-check the assumptions and ensure broad consistency of approach where comparative judgments are required. Such a framework is what we have tried to develop in this paper. True, we restrict in these visualizations our attention to the aggregate health burden imposed to the population due to mortality and morbidity. However, this information can serve as a building block for assessing the magnitude of many nonstandard impacts, where primary data is not available. For instance, the share of burden imposed on infants suggests what may be the potential long-term human capital loss or the health and productivity burden on their caregivers. Similarly, by knowing the distribution of health impacts on different population groups, concerns related to equity or severity of disease can be embedded in decision-making. Additionally, for quantifying the extra priority to be given to a certain vaccine under the effect of a spread of fear within a community, the models can support the elicitation of context-specific preferences, since a disease with a higher case fatality rate is presumably more fearinducing than one where the health losses accrue over a large number of low-intensity episodes. Current and forthcoming studies that seek to expand the scope of value assessments are surely deemed promising and worthwhile, as further insights into these novel elements of value can advance the understanding of the impacts of immunization programs and, ultimately, better inform their funding. However, to date, accurate primary data for quantifying thoroughly certain factors are often sparse and unevenly available. Also, although fresh evaluation practices are being put forward (e.g.), they still remain narrowly applied, while asking for emergent methodological challenges to be tackled. In light of the current limitations in data and methods, the pursuit of such broad-spectrum valuations risks not only to prove burdensome but also to prevent research from altering and impacting real-world policies as it could, since making it scarcely able to serve the primary function of allowing the prioritization of health spending decisions on the basis of comparisons. Provided that enlarging the array of impacts to factor into the decision-making would increase the complexity of modeling, we advocate that a promising area the scientific community should pay greater attention to is the development of models, as the ones here illustrated, that -albeit (or precisely because) essential -can guarantee that evidencebased immunization decision-making is extensively carried out, as well as widely and transparently communicated. Conclusion This paper demonstrates how a visual design can deliver the relevant information in a compact form, through two plots, IRP and PIP. While the design is open for future improvements, the approach shows promise in being an informative guide to both the public and to decision makers, both of whom are crucial for the future implementation and review of vaccination programs. Note 1. Along both the x and y-axes, any n is assigned to the length log 1 n. The addition by 1 is so that zero is set at zero. Acknowledgments We thank the broader project team for the HAPIOR project as well as the helpful advice from staff at the Department of Health and Social Care, particularly Tom Irving. Declaration of interest E Kung and MV Bufali report no conflicts of interest. Dr A Morton reports having been supported by grants from Department for International Development, during the conduct of the study; personal fees from Office of Health Economics, Wellcome Trust, and Astra Zeneca; non-financial support from EFPIA (e.g. Roche, Astellas, AZ, Pfizer and others). The authors have no other relevant affiliations or financial involvement with any organization or entity with a financial interest in or financial conflict with the subject matter or materials discussed in the manuscript apart from those disclosed. |
Rich-Club Analysis in Adults With ADHD Connectomes Reveals an Abnormal Structural Core Network Objective: Whether the abnormal connectome of brains rich-club structure in adults with attention-deficit hyperactivity disorder (ADHD) remains unclear. Method: The current study used diffusion tensor imaging (DTI) and resting-state functional magnetic resonance imaging (fMRI) to compare the performance of 42 adults with ADHD and 59 typical development (TD) adults. Results: A reduced density of rich-clubs among structural hub nodes, including the bilateral precuneus, the insula, the caudate nucleus, the left putamen, and the right calcarine, was found in adults with ADHD. Moreover, lower global efficiency was found in adults with ADHD than in TD, which might be caused by a reduced density of rich-club connections in ADHD patients. Conclusion: Given that adults with ADHD have greater coupling strength between structural and functional connectivity than TD adults, connectome abnormalities with a reduced rich-club connectivity density might be accompanied by altered functional brain dynamics in ADHD patients. |
Semantic Textual Similarity Methods, Tools, and Applications: A Survey Measuring Semantic Textual Similarity (STS), between words/ terms, sentences, paragraph and document plays an important role in computer science and computational linguistic. It also has many application sover several fields such as Biomedical Informatics and Geoinformation. In this paper, we present a survey on different methods of textual similarity and we also reported about the availability of different software and tools those are useful for STS. In natural language processing (NLP), STS is a important component formany tasks such as document summarization, word sense disambiguation, short answer grading, information retrieval and extraction. We split out the measures for semantic similarity into three broad categories such as (i) Topological/Knowledge-based (ii) Statistical/Corpus Based (iii) String based. More emphasisi s given to the methods related to the WordNet taxonomy. Because topological methods, plays an important role to understand intended meaning of an ambiguous word, which is very difficult to process computationally. We also propose a new method for measuring semantic similarity between sentences. This proposed method, uses the advantages of taxonomy methods and merge these information to a language model. It considers the WordNet synsets for lexical relationships between nodes/words and a uni-gram language model is implemented over a large corpus to assign the information content value between the two nodes of different classes. |
Infant mortality and the American Academy of Pediatrics. In recent years, there has been a surge of renewed interest on the part of numerous groups in the subject of infant mortality, a source of continued concern to pediatricians for many years. The constancy of concern of the American Academy of Pediatrics about infant mortality is evident in the fact that Pediatrics has published a summary of national statistics on the subject annually since 1950. That yearly analysis by Dr Myron Wegman appears in this issue.1 In addition, a statement of the Academy's current position on infant mortality also appears in this issue.2 As this position paper makes clear, there are several reasons for a renewed concern about infant mortality. |
/**
* Print some text into this field, making the fields preferred width larger if necessary
* @param label
* @param date
*/
private void updateGridLabel(Label label, String text) {
label.setText(text==null?"":text);
GridData data = (GridData)label.getLayoutData();
int drawnWidth = label.computeSize(SWT.DEFAULT, SWT.DEFAULT, true).x;
if (drawnWidth > data.widthHint) {
data.widthHint = drawnWidth + 5;
}
label.redraw();
} |
#include<stdio.h>
#include<math.h>
int main(void)
{
double avg;
int n,x,y;
int xy[9][2];
int i,j;
double sum=0;
scanf("%d",&n);
for(i=1;i<=n;i++){
scanf("%d%d",&x,&y);
xy[i][0]=x;
xy[i][1]=y;
}
for(i=1;i<n;i++){
for(j=1;i+j<=n;j++){
sum+=sqrt(pow((xy[i][0]-xy[i+j][0]),2)+pow((xy[i][1]-xy[i+j][1]),2));
}
}
avg = sum*2 / n;
printf("%lf",avg);
return 0;
}
|
Republicans are in an uncomfortable position because many urged President Donald Trump not to declare a national emergency to fund the border wall.
WASHINGTON – The House voted 245-182 Tuesday to block President Donald Trump's declaration of a national emergency along the southern border, but Democrats didn’t win enough support from Republicans to overcome Trump’s threatened veto.
Only 13 Republicans joined all Democrats in backing the measure, even though many had warned against the declaration.
GOP Rep. Cathy McMorris Rodgers of Washington said she was “100 percent in favor of President Trump’s wall" but Congress shouldn't give up its power delegated by the Constitution.
"When that power is delegated to the executive or judicial branches, representatives become elected bystanders and ‘We the People’ no longer have a voice," McMorris Rodgers said.
The GOP-controlled Senate must weigh in on the "privileged resolution" within 18 days.
Vice President Mike Pence and legal experts discussed the emergency declaration with Republican senators during their weekly caucus lunch Tuesday. Several senators said afterward they were still processing the information.
Trump declared an emergency this month after Congress sent to the president a bipartisan funding bill that failed to meet his demand for $5.7 billion for a wall along the U.S.-Mexico border. Trump took the action to free up billions from other sources to pay for the barrier.
Democrats have said the declaration is unconstitutional and are using a provision from the National Emergencies Act to try to halt the president.
"If the president is successful in getting his way on this, rest assured he will come back, he will try this again, probably on other issues, as will future presidents. The Congress must step up," said Rep. Joaquin Castro, the Texas Democrat leading the effort.
Hours before the vote, Trump formally threatened to veto the legislation.
House Speaker Nancy Pelosi said the core of the Constitution that lawmakers swore to uphold is the separation of powers between the three branches of government.
"Perhaps it’s time for our country to have a civics lesson," Pelosi said before the vote. "Our founders rejected the idea of a monarch."
Which Senate Republicans have said they’ll support the measure?
The national emergency has been controversial for Republicans, many of whom warned the president his move could set a bad precedent. But it is unclear how many will publicly oppose the president and vote to terminate the order.
On Monday night, North Carolina Sen. Thom Tillis, a Republican, announced he would vote in favor of a resolution that disapproved of the national emergency in an op-ed in the Washington Post.
"As a U.S. senator, I cannot justify providing the executive with more ways to bypass Congress," Tillis wrote. "As a conservative, I cannot endorse a precedent that I know future left-wing presidents will exploit to advance radical policies that will erode economic and individual freedoms."
GOP Sens. Susan Collins of Maine and Lisa Murkowski of Alaska have also indicated support for the measure in its current form.
Sen. Martha McSally, R-Arizona, said Tuesday night she was "seeking assurances that the money will not come from Arizona military construction projects" for her vote.
Will the resolution pass the Senate?
After passing the House on Tuesday, the resolution must be taken up within 18 days by the Senate, where its future remains unclear.
Most legislation that comes up in the Senate requires 60 votes to pass. However, because this resolution is considered "privileged," it needs just 51 votes, increasing the chances of passage. There are 47 Senate Democrats – none of whom have spoken against the resolution – so if the Democrats stay unified only four Republicans would need to cross party lines. Tillis, Collins and Murkowski already have said they would if the legislation remains the same as it was introduced.
Why does this resolution get special treatment?
Normally legislation comes up for a vote at the discretion of the speaker or majority leader. That means if a lawmaker introduces legislation the leadership doesn't want to deal with, the bill may not be brought up for a vote. But because this resolution comes from the National Emergencies Act, once it is introduced it must come up for a vote.
If Congress is unable to halt the national emergency through the legislative process, members could still file lawsuits, a move Pelosi did not rule out during a press conference last week.
California and 15 other states have already filed a lawsuit over the declaration, arguing it exceeds the power of the president and unconstitutionally redirects federal money that would have gone to their states.
And the liberal watchdog group Public Citizen filed a lawsuit on behalf of Texas landowners who were told their property would be seized for the wall. |
Addition of Teicoplanin or Vancomycin for the Treatment of Documented Bacteremia due to Gram-Positive Cocci in Neutropenic Patients with Hematological Malignancies: Microbiological, Clinical and Economic Evaluation A prospective, randomized, double-blind trial was conducted on 124 febrile patients with hematological malignancies to compare teicoplanin with vancomycin as an addition to the initial empiric amikacin-ceftazidime regimen after documented bacteremia due to gram-positive cocci. At enrolment, patients in both groups were comparable with respect to age, sex, underlying hematologic disorders and duration of neutropenia. Rates of therapeutic success were 55/63 (87.3%) in the teicoplanin group and 56/61 (91.8%) in the vancomycin group (p = 0.560). The mean duration of treatment was similar, being 12.2 and 11.4 days, respectively (p = 0.216). Patients treated with teicoplanin remained febrile for slightly longer than those treated with vancomycin (4.9 vs. 4.0 days) (p = 0.013). Thirteen patients experienced an adverse drug reaction, but without any significant difference in the two arms. Isolated staphylococci showed a progressive and significant decrease in susceptibility to both glycopeptides during the 8 study years. The economic analysis performed showed that the addition of vancomycin is cost-saving. |
Structure and Magnetic Properties of Boron Doped Fe50+xCu25−xM25(M = Al, Ga) and Fe50+xCo25−xGa25 Heusler Alloys In this paper, we study the effect of B introduction in various Heusler alloys on their structural and magnetic properties. Samples with nominal stoichiometry Fe<sub>50+x</sub>Cu<sub>25-x</sub>Ga<sub>25</sub>, Fe<sub>50+x</sub>Cu<sub>25-x</sub>Al<sub>25</sub>, and Fe<sub>50+x</sub>Co<sub>25-x</sub>Ga<sub>25</sub>(x= 0-10) with the addition of excess B up to 12 at% were prepared with Ar arc-melting as base materials. The starting materials were subsequently converted to ribbons using melt-spinning technique with velocity of 35 and 40 m/s, while the other parameters were kept fixed. Basic study of the alloys was conducted with various characterization techniques (energy dispersive X-ray spectrometry, X-ray powder diffraction, and magnetization versus temperature and field). The materials were thermally treated at various temperatures between 873 and 1073 K and the effect on the structure and magnetic properties was studied. |
<reponame>illusi0n/construction
package com.mlinvest.construction.persistence.model;
public enum TenderStatus {
OPEN,FINISHED;
}
|
Bakhtin and Cassirer : The Event and the Machine / Bakhtin e Cassirer : o evento e a mquina The influence of Cassirers work on Bakhtins writings from the 1930s has been studied in some detail but scholars have not examined Bakhtins early work, Toward a Philosophy of the Act (K filosofii postupka), in connection with Cassirers philosophy. The article first reveals how attuned Bakhtin was with the intellectual Zeitgeist not only of his own times, but also that of the 20 century. The uncanny intellectual harmony between the ideas of Bakhtin and Cassirer can be seen at the very beginning of Bakhtins career. The two thinkers are united in their reception, transformation, and attempt to reconcile two antithetical philosophical positions dominant at the beginning of the 20th century: the transcendental philosophy of Kant, Neo-Kantianism, and the Lebensphilosophie of Simmel, Bergson, and Heidegger. Bakhtin and Cassirer were alarmed by the cultural pessimism and potential nihilism inherent in the position of Lebensphilosophie. Next, the author shows ways in which Bakhtins and Cassirers ideas resonate with those of the later 20 century Jacques Derrida. RESUMO A influncia da obra de Cassirer nos In the last few years, a number of critics have drawn our attention to the important influence of Cassirer's philosophy to the Bakhtin Circle in general and to Bakhtin's own notions of laughter, the carnival, dialogue, and language in particular. Many of the references are limited to statements of fact that are rarely followed up by any sustained systematic analysis of the core issues or tenets of Cassirer's philosophy and their relation to Bakhtin's thought. In his often quoted article Bakhtin and Cassirer: The Philosophical Origins of Bakhtin's Carnival Messianism What interests me here is not so much the degree of influence Cassirer may have exerted on the work of the later Bakhtin, as the uncanny intellectual harmony of their thinking right from the beginning, as well as the degree to which they have anticipated, as Derrida says, "a concern of thinking that has kept a certain number of 'us' working for the last few decades" (DERRIDA, 2002, p.74). The primary goal of this article will be to demonstrate the uncanny harmony between Bakhtin and Cassirer's thought, especially in terms of their concern for the nature of subjectivity. This done, I would like to illustrate how their mutual interest for subjectivity can be seen to resonate with later twentieth century thinkers and in particular with the thought of Jacques Derrida. But first, to Bakhtin and Cassirer. It is safe to say that by the early 20s, when Toward a Philosophy of the Act (TPA) is said to have been written, Bakhtin was well on his way to being a mature and original thinker in his own right. That said, in this 1921 text, we find the traces of a young philosopher hastily and passionately working in the thralls of the moment of inspiration, struggling to give objective form to his ephemeral ideas as they evaporate into the ether of time, disappearing forever into the nothingness from which they emerged. One can feel the frustration of its author as he is forced to fabricate, bricoler one might say, new modes of expression from old ones because he lacks an adequate technical vocabulary to articulate his lucid but elusive insights into the truth of his existence. Perhaps, in this text more than in any other by Bakhtin, we come closest to encountering Mikhail the individual giving birth to Bakhtin the author. As Holquist so eloquently notes in the introduction, we catch Bakhtin here in the very moment of the creative act itself: "we are here at the heart of the heart, at the center of the dialogue between being and language, the world and mind, 'the given' and 'the created' that will be at the core of Bakhtin's distinctive dialogism as it latter evolves" (BAKHTIN, 1993, p.ix) The central philosophical question for both Bakhtin and Cassirer was twofold: 1) how can we, as Cassirer puts it, "reconcile the immanence of life with the transcendence of spirit" (CASSIRER, 1958, p.42) once-occurrent Being-as-event. Such a first philosophy," Bakhtin insists, "does not exist, and even the paths leading to its creation seem to be forgotten" (BAKHTIN, 1993, p.19; author's italics). The reader familiar with Heidegger's project of fundamental ontology will no doubt wonder at the similarity of Bakhtin's claim here, for Heidegger too will claim that the tradition has forgotten the question of being. Being and Time seeks to reawaken the question of the meaning of being before answering it concretely. Much, if not all, of Heidegger's thought can be understood as a sustained quest to uncover the "paths leading to" a thinking of being that seems to have always already been "forgotten." Heidegger, too, will claim that the neo-Kantian attempt to provide the transcendental structures of culture cannot be complete before its "ultimate foundations" have been established through a complete analytic of Dasein. The reader familiar with Heidegger's analytic of Dasein cannot help but feel that it would have been the ideal term for Bakhtin's view of the I that exists: I, too, exist actually -in the whole and assume the obligation to say this word. I, too, participate in Being in a once-occurrent and neverrepeatable manner: I occupy a place in once-occurrent Being that is unique and never repeatable, a place that cannot be taken by anyone else and is impenetrable for anyone else (BAKHTIN, 1993, p Bakhtin's language, not about the "once-occurrent event" but about the "actual-eventness of the once-occurrent event" (BAKHTIN, 1993, p.1; my italics). Here too the "theoretical" and the "aesthetical" always already form "a constituent moment in the once-occurrent event of being" (BAKHTIN, 1993, p.2) itself. "Aesthetic intuition" provides the once-occurrent event with its "image or configuration" and in this way is "objectified" into the actual-event-ness of the once-occurrent event (BAKHTIN, 1993, p.1). The split between "the historical actuality of its being, the actual and onceoccurrent experiencing of it" from the "content or sense of a giving act/activity" (BAKHTIN, 1993, p.2) provided by the theoretical interpretation and aesthetic configuration proves, in the final analysis, to be untenable for Bakhtin. An act of our activity, of our actual experiencing, is like a two-faced Janus. It looks in two opposite directions: it looks at the objective unity of a domain of culture and at the never-repeatable uniqueness of actually lived and experience life (BAKHTIN, 1993, p.2). Thus, Bakhtin does not speak of experience (Erlebnis) per se but of the "active experience of experience" (BAKHTIN, 1993, p.34) -the Erfahrung of an Erlebnis. Experience (Erfahrung) is, in the language of transcendental philosophy, the product of a process of transfiguration that transforms and organizes a particular lived experience (Erlebnis) of particularity (in fact by means of a synthesis of a series of lived experience of particularities) into a unified, stable, and meaningful experience (an Erfahrung) of a given object (Gegenstand) standing over and against a subject. Through the process of configuration (Gestaltung) and formation (Bildung) of "discursive theoretical thinking," the radically particular actual eventness of the once-occurrent event is transformed into the general occurrence of a thing that is understood as being this or that -that is to say, that has a self-identical, unchanging, and enduring Wesen -essence or being. As such, constitution. "Symbolic pregnance" is "the way (die Art) in which a perception as a sensory experience contains a meaning which it immediately and concretely presents" (CASSIRER, 1957b, p.202). It is interesting to note that for both Bakhtin and Cassirer, language and the aesthetic imagination are the two primordial modes of meaning constitution. While language can provide a conceptual configuration of the world, this remains a purely logical framework of relational structures. In order for this system of conceptual classifications to manifest itself, it requires the aesthetic imagination that provides the differential-relational logic of language with its (aisthetikos) presence (Darstellung). Experience, be it the experience of the self, an object or a word, is thus the synthetic product of the work of language and aesthetic imagination. However, it is here that the proponents of through this objective presence that we can become an object of consciousness, become, that is, self-conscious. However, on the other hand, this process of articulation leads to a limitation and burden on the I that endangers its liveliness, its free spontaneous movement. Spirit invests itself in its work, and in fact must invest itself in its work, but this work stands before it as something foreign, as something fixed and stable, something external and objective, as something dead. "It is," as Simmel writes, "as if the creative motion of the soul were to die in its own products" (CASSIRER, 2000, p.106 a conclusion, the thing-become (das Gewordene) succeeding the thing-becoming (dem Werden), death following life, rigidity following expansion, intellectual old-age and the stone-build, petrifying world-city following mother-earth and the spiritual childhood of Doric and Gothic. They are an end, irrevocable, yet by inward necessity reached again and again (SPENGLER, 1991, p.24). Ernst Jnger, the author of the Die Arbeiter and Der Kampf als inneres Erlebnis echoes Spengler and Simmel's views: here is still much of the animal in man who slumbers on the comfortable woven carpets of a polished, honed, and silently intricate civilization and yet when the point of the dial of life swings back to the red line of the primitive, the mask falls, and he emerges, naked as ever before, the original man . Whenever life reverts to its primal functions, his blood, which up until then has flowed coolly and regularly through his veins in the mechanistic activity of his stony, urban skeleton, foams up, and the ancient rock which has lain for long ages, cold and rigid, in hidden depths, melts once again into white-hot lava (JNGER, 1922, pp.17-18 apud BEASELY-MURRAY, 2007). If I have quoted Spengler and Jnger at length, it is to remind us -Bakhtin and Cassirer needed no such reminder -that words and ideas are never just words and ideas as opposed to real life: words and ideas are the life blood of spirit and, as such, they constitute and pre-figure our very understanding of ourselves, others, and reality. In the end they are productive, in that their meanings "are so woven into the reality of action (Realitt des Wirkens) as to form an indispensable part of it" (CASSIRER, 1957a, p.39) -they produce that which they name. These quotes and the cultural pessimism to which they gave expression must be situated in their proper historical context, for Der Kampf als inneres Erlebnis was published in the same year as Mein Kampf and the Nremberg Rallies announced and gave form, and thus reality, to a direction of concrete events that would lead to unspeakable horrors: words are never just words. While both Bakhtin and Cassirer acknowledge the existence of a certain tragedy of culture, this alienation is for them not the whole story. Both counter by arguing that we need to follow the creative process to its logical conclusion in an ethical act. We need, as Cassirer notes, to "return here from the forma formata to the forma formans, from the became (Gewordenen) to the principle of becoming (Werdens)" (CASSIRER, 1985, p.43). For Bakhtin and Cassirer, culture is comprised of two antithetical but interrelated and equiprimordial forces: a "centripetal force" that seeks the conservation of the traditional status quo and a "centrifugal force" that seeks the renewal of the creative act: the former they call "mythical consciousness" and the later is termed "critical consciousness." 4 The thing created does not simply stand over against the creative process; on the contrary, new life continually pours into these 'molded forms,' preserving them and preventing their rigidification (CASSIRER, 2000, p.113). iving consciousness finds cultural values to be already on hand as given to it, and its whole self-activity amounts to acknowledging their validity for itself (BAKHTIN, 1993, p.35). For the work, in whose enduring existence the creative process congeals, does not stand at the end of this path, but rather the 'you,' the other subject who receives this work in order to incorporate it into his own life and thus transform it back into the medium from which it originates (CASSIRER, 2000, p.110). n answerable deed must not oppose itself to theory and thought, but must incorporate them into itself as necessary moments that are wholly answerable (BAKHTIN, 1993, p.56). Thus, the recipient does not take the gift as he would a stamped coin. For he takes it up only by using it, and in this use he imprints upon it a new shape (CASSIRER, 2000, p.114). An act must acquire a single unitary plane to be able to reflect itself in both directions -in its sense or meaning and in its being; it must acquire the unity of two-sided answerability -both for its content and for its Being (BAKHTIN, 1993, pp.2-3). A poem is but ink on a page until someone breathes life into it, and by doing so participates in the creative act that brings it into existence. Thus, for Bakhtin and Cassirer, no act of speech, however small, does not transform in some way language itself. In other words, their response to the cultural pessimism of Spengler and Lebensphilosophie is to argue that the creative spontaneity of life is always already a form of re-naissance, a renewal of life through responsible participation in the creative process of the event of life itself, where the responsibility stems from the ability to respond to the work (the utterance) of the other. For both Bakhtin and Cassirer the I's relation to the other is always already mediated by the work, the product of the creative act-or perhaps better, the I, the work, and the other form the "modes of mediation itself" (CASSIRER, 1995, p.132). Cassirer calls these the Urphnomene of the symbolic function, whereas Bakhtin calls them "the architectonic of an event." (BAKHTIN, 1993, p.75). But, as we have seen, the event is always a symbolic-event, a textual-event. By taking the givenness of the word as the end of the creative process, the other to whom one speaks is negated entirely from the creative process of meaning; it becomes enough to be a solipsistic subject standing alone in the abyss speaking to oneself about another who is never more than a This is what happens in the mythical consciousness which is ruled by a logic of fusion, establishing an imaginary identification between the act and the meaning of the act. The result is a homogeneous, enclosed and mono-logical sphere of meaning that is blind to the heterogeneous existence of another centre of life beyond its own, that sees in the other only the reflection of its own narcissistic unity. In the end, as there is no nonmediated experience, be it an experience of the self or an experience of the other, we are always already enveloped within the self-identical existence of the narcissism of the same. However, Bakhtin and Cassirer would agree with Derrida that, while there is no narcissism and non-narcissism, there are narcissisms that are more or less comprehensive, generous, open, extended. What is called non-narcissism is in general but the economy of a much more welcoming and hospitable narcissism. One that is much more open to the experience of the other as other (DERRIDA, 1995, p.199). The individual cannot remain within itself, as a being-in-itself, but must express itself by articulating itself, externalizing itself in an objective form not only in order to become a being-for-itself, but also in order to become a being-for-and-with-others. Only in this way can the individual experience itself as a being that is, which is what we mean when we say a being is self-consciousness: For the 'conversation of the soul with itself' is only possible if the soul, as it were, splits itself . In soliloquy the soul ceases to be a mere particular, an 'individual.' It becomes a 'person' in the basic etymological meaning of the word, which goes back to the mask and the role of the actor (CASSIRER, 2000, p.54). But Cassirer recognizes that, here too, every initial expression is already the beginning of an alienation" that can never be overcome or be resolved, for "the life of spirit consists in this very act of severing what is so that it can, in turn, even more securely unite what has been severed" (CASSIRER, 2000, p.134). Thus, Bakhtin concludes I shall not find myself in that life ; I shall find only a double of myself, only someone pretending to be me. All I can do is play a role, i.e., assume, like a mask, the flesh of another-someone deceased (BAKHTIN, 1993, p.18). The truth of my existence, of the once-occurrent event, which Bakhtin calls pravda, can only be thought of in terms of "the truth (istina) that is composed of universal moments; that the truth of a situation is precisely that which is repeatable and constant in it" (BAKHTIN, 1993, p.37). The act can only be understood in terms of its meaning or sense of the act. And in fact, "we act confidently only when we do not act as ourselves, but as those possessed by the immanent necessity of the meaning of some domain of culture" (BAKHTIN, 1993, p.21). In other words, we act most confidently when we have an alibi for our actions, an alibi that unburdens and distances us from the site of the crime, from our responsibility for this happening, an alibi that determines a priori the raison d'tre and thus the meaning of both our actions and our being; as a once-occurrent event, I cannot be responsible for what has been done, nor for what is being done, as it is not I myself who determines the meaning of my action; the act is done in the name of meaning, for the sake of a system of meaning, as an expression of its existence and not mine. I am but an agent, a representative, of this linguistic machine that operates through us. In this sense, George Bush is not the President of the United States -it was the President of the United States and not George Bush who began the Iraq war. The soldiers in Goya's "The Third of May, 1808" have no faces; they are not responsible for the event that takes place before them, through them, and ultimately to them, for they are only automatons executing their orders to execute the revolting peasants: their alibi will be that they were just following orders. But to act with alibi, to act not as ourselves, means to act with impunity, to have reduced one's being to a function of meaning, to a cog in a machine that is, as Derrida says, "destined to repetition to reproduce impassively, imperceptibly received commands" (DERRIDA, 2002, p.72) -in other words, it is to act 'as if' we did not act, as if we did not exist -and yet, we exist -no, I exist! "It is not the content of an obligation that obligates me, but my signature below it -the fact that at one time I acknowledge or undersigned the given acknowledgement" (BAKHTIN, 1993, p.38). To act without alibi is to give one's life, to assume one's once-occurrent event by being it, by saying yes, and this goes to the heart of what we would like to call a 'response' or a 'responsibility,' be it ethical, juridical, or political. This responsibility, will never be able to avoid appealing to someone who would dare say, 'Here I am, without alibi, and here is the first decision that I sign' (DERRIDA, 2002, p.xxxiv). However, after all that has been said: How can one continue to say, 'Here I am'? How can one reaffirm the ineffaceable passivity of a heteronomy and a decision of the other in me? How can one do it without giving in to the alibi? (DERRIDA, 2002, pp.xxxiv-xxxv). You cannot -but nor can you ever "acquit yourself" -"The impossibility of acquitting oneself, the duty not to want to acquit oneself"-that is what you attest to at the "moment of signing without alibi" (DERRIDA, 2002, p.xxxv But "pure performativity" is impossible. Derrida, as Bakhtin and Cassirer before him, recognize what we might call the "tragedy of performativity," its ultimate failure. Within speech-act theory, a performative is a discursive practice that enacts or produces that which it names. But Derrida makes clear that the power of the subject to bring forward, to express itself relies upon the formative power of the language spoken and is therefore always derivative of it: Could a performative utterance succeed if its formulation did not repeat a 'coded' or iterable utterance, or in other words, if the formula I pronounce in order to open a meeting, launch a ship or a marriage were not identifiable as conforming with an iterable model, if it were not then identifiable in some way as a 'citation'? in such a typology, the category of intention will not disappear; it will have its place, but from that place it will no longer be able to govern the entire scene of the system of utterance (l'nonciation) (DERRIDA, 1988, p.18). Thus, performativity is never pure performativity, it is never a radically unique act or a pure event, for it is always pregnant with the normative structures that provide it with iterable presence and being. The problem of reconciling the immanence of life with the transcendence of spirit without reducing the one to the other brought Bakhtin and Cassirer to consider, as Derrida latter puts it, "the dynamics of the borderline between the work and life, between the system and the subject of the system" (DERRIDA, 1985, p.5). The subject for Bakhtin, Cassirer, and Derrida can no longer be a modern autonomous pre-existing agent of meaning, a pure transcendental ego. Nor can it be understood la structuralisme, as a mere effect of discourse, as the effect of the machinery of language: there can be, for them, no question of the death of the authorrather the contrary. If the rift -if one can still speak of a separation at all between life and the work -between the act and the meaning of the act can no longer be located, if it can be located, between the once-occurrent event of life and the machine of cultural configuration, because "an oeuvre is an event there is no oeuvre without singular event, without textual event," (DERRIDA, 2002, p.133) then it must now be located within the subject as the locus of the work-life-event, producing a split-being that is both author and authored, spectator and spectacle. Thus Bakhtin and Cassirer can ask with Derrida: Who is it that is addressing you? Since it is not another, a narrator, or a deus ex machina, it is an 'I' that is both part of the spectacle and part of the audience, an 'I' that, a bit like you, undergoes its own incessant violent re-inscriptions within the arithmetical machinery. An 'I' that functioning as a pure passageway for operations of substitution is not some singular and irreplaceable existence, some subject or life, but, rather, moves between life and death, between reality and fiction (DERRIDA, 2004, p.357 rethinking what it means to be a subject after the linguistic turn. While recognizing that our very sense of self is always already constituted by the normative cultural structures of language, that we can never be that autonomous Cartesian subject, they do not abandon us to the impersonal sphere of the "they" of Heidegger or the alienated worker of Marx. Their unity of project is not accidental; it is, as Derrida says, "a concern of thinking that has kept a certain number of 'us' working for the last few decades" (DERRIDA, 2002, p.74). |
SEASIDE — Monterey County is in a huge crisis as the dramatic rise in family homelessness along the coast and rural areas continues to grow each day.
The National Center for Youth Law and Pivot Learning hosted a presentation for the report “Crisis on the Coast: The Bay Coastal Foster Youth and Homeless Student Populations” inside the Community Center at Soper Field on Thursday afternoon.
The event, which was co-hosted with Monterey Peninsula Unified School District, featured a panel of experts on homeless and foster youth populations and a public forum.
The panel featured Adrienne “Bing” Goldsworth, who’s the National Center for Youth Law program manager for FosterEd in Monterey County and was on hand to talk about ways to help reduce the number of homeless and foster youth students in the area.
Other panelist included Darius Brown of the Monterey County of Education, MPUSD board trustee Wendy Root Askew, MPUSD Social Emotional Support director Donnie Everett and MPUSD homeless liaison Carlos Diaz.
Brown, who’s the coordinator for McKinney-Vento Homeless Education Services, said getting all the experts, liaisons and families in the same room to talk about the subject means people are acknowledging it is an issue.
“If your district is not talking about the situation then that means you haven’t acknowledged family homelessness as an issue,” he said.
Pivot Learning CEO Arun Ramanathan and program manager Hannah Melnicoe were at the forum to present the report findings.
The report highlighted that homelessness is not just an urban issue. A slideshow presentation showed that rural areas in Monterey County have seen steady increases in the number of homeless and foster students they serve.
A chart showed that 286 out of the 11,164 enrolled in San Benito County are homeless youths in school, while 7,686 out of 77,517 students enrolled in Monterey County are homeless, which is more than triple that of San Francisco.
Brown said he wasn’t surprised by the information because he’s helped on similar studies in Santa Clara County.
Jon Wizard, a councilman for the city of Seaside, was at the forum and is a big advocate on the homelessness issue in Monterey County. He said it was good to have a local perspective as a follow up to what’s going on statewide and nationally.
Wizard said there are 534 children in Seaside who have been counted that don’t have permanent shelter — nine of them are infants.
Root Askew said during the panel discussion that students aren’t able to learn in the classroom because they’re learning how to survive. Wizard said they need solutions when the talk of creating opportunities for underserved and underrepresented communities, which are typically communities of color, comes up.
“How do we lift up our Latino, black and Asian communities to be the next doctors, lawyers and city managers when they’re not even sure about where they’re sleeping tonight?” Wizard said.
Brown said the homelessness crisis is promoting a lot of dialogue. He said elected officials are wanting to know more about the McKinney-Vento Homeless Assistance Act of 1987, which is a federal law that provides federal money for homeless shelter programs.
Brown said people question the accuracy of the count or wonder why there are so many homeless students and if they being referred to services that could get the families out of residential instability.
But Monterey County schools are serving a high concentration of homeless students. Plus, the existing funding streams and services do not meet the needs of homeless and foster students.
Brown said the goal of Thursday’s forum was to highlight the issue of family homelessness in the Peninsula and within Monterey Peninsula Unified School District. He said districts are starting to implement more family resource centers but that’s because schools aren’t just serving as a classroom to educate students.
The Monterey Office of Education is hosting a second forum Monday at its main building at 901 Blanco Circle in Salinas. The presentation starts at 1 p.m. and will be held in Meeting Room B. |
Understanding social media discontinuance from social cognitive perspective: Evidence from Facebook users Based on social cognitive theory, this study proposes a research framework to investigate two different social media discontinuance behaviours: reduced usage and abandoned usage. Specifically, perceived technology overload, information overload and social overload are the environmental factors that induce negative personal states, including dissatisfaction and social media fatigue, which lead to negative behavioural changes, such as reduced usage and abandoned usage of social media. The proposed research model was tested empirically with data collected among Facebook users. The research results indicate that impacts from perceived technology overload, information overload and social overload on social network fatigue and dissatisfaction vary. Dissatisfaction exerts greater impacts on abandoned-usage behaviour than social media fatigue, but similar impacts on reduced-usage behaviour as social media fatigue. In addition, reduced-usage behaviour was found to lead to abandoned-usage behaviour. Finally, we discuss the theoretical and practical contributions that can be gleaned from the proposed research model. |
export const authTokens = {
authProvider: 'AuthProvider',
authMiddleware: 'AuthMiddleware',
};
|
. The tuberculin skin test is used worldwide to assess the tuberculosis infection in humans and animals. It is conventionally admitted that a reaction larger than 10 mm expresses a consumptive infection. It is possible to find a reaction smaller than 10 mm in patients with active disease, like bacteriological confirmed pulmonary tuberculosis, that is a negative reaction. 1719 patients with recently discovered bacteriological confirmed pulmonary tuberculosis were tested with PPD-IC65 solution 2 U/0.1 ml; 497 of them (28.9%) reacted less than 10 mm; 151 of these were retested with PPD solution 10 U/0.1 ml, in 11.5% of them the test was negative. |
London could see riots again unless more trains and buses are provided at affordable fares for the poorest communities as the population soars, the city's transport commissioner has warned.
He said the city will face "overwhelming" overcrowding on its congested transport networks by 2030 without urgent progress on new rail lines.
Despite an annual investment of about £1bn in tube upgrades and the £14.8bn spent building Crossrail, a rapidly expanding population means an additional 6m trips will be made in the capital each day by the end of the next decade, swallowing up the new capacity on public transport.
In an interview with the Guardian, Sir Peter Hendy, head of Transport for London, said low-paid workers now lived on the outskirts of the capital rather than in inner-city neighbourhoods, and that there could be "social unrest" if they could not easily commute around the city for work.
"London's poor don't live in Harrow Road, they live in Enfield and Tolworth and if you can't get them to jobs they want, your city's going to be in a bad way: it's not going to progress and contribute to national economic growth," Hendy said. "The stakes are pretty high. If you're not able to increase transport capacity, and people find accessing work impossible, you risk social unrest. You can expect trouble."
Bus fares have risen by more than 50% in six years under the London mayor, Boris Johnson – a policy Hendy has backed. But the transport commissioner he warned fares could not continue to rise. "The bus network is the staple of outer London. We're going to need more revenue funding. Otherwise we're going to leave people behind. When you start leaving people behind, you start saying to people in London they may not be able to get to work on time and when that happens, you damage the economy quite severely."
Hendy also warned that unless major infrastructure projects, such as Crossrail 2, were started and new rail lines were built, overcrowding in central London would be "overwhelming". Transport chiefs say it will take at least 15 years to build Crossrail 2.
"You just won't be able to get into or on to many of our transport networks at peak times if you don't start [these infrastructure projects] now. When Crossrail opens, it will be full within months; the population will go on towards 10 million and you'll soon need Crossrail 2. You won't be able to do without it. In central London the overcrowding will grow to be overwhelming."
London's population is officially estimated at 8.4 million and is rising by about 80,000 people a year. It is expected to reach 10 million by 2030. "If you contemplate a London in 2030 without continuous investment and more revenue money, we will have the kind of congestion you're looking at in Mumbai," he said.
Mumbai was one of several Indian cities that experienced protests over rail fare increases earlier this year, while more than a year of escalating demonstrations in Brazilian cities in the runup to the 2014 World Cup were ignited by fare rises on public transport.
While the completed Crossrail, a revitalised Thameslink line and tube upgrades will bring great leaps in capacity in the next five years, transport chiefs are struggling to keep up with passenger numbers, which have risen by a third on the tube in the past 10 years. The underground ran more services and carried more customers than ever before in 2013-14, with a record 1.265 billion passengers.
The capital's growth was putting pressure in places that "people never expected", Hendy said. "I've been a strong advocate of putting fares up a lot in an era of declining government funding. But if the poor are not living in Tower Hamlets, Stockwell, Hackney and Southwark any more and all the places where people on low incomes used to live, they are living a long way away and a future mayor is going to have to make sure they can afford to get to work."
The chancellor, George Osborne, cut funding for day-to-day operations in London by 25% in the last spending review, meaning fares are likely to rise in coming years. Hendy and TfL will be joining with counterparts in Transport for Greater Manchester in the coming weeks to push for greater powers over revenue and spending for cities. Hendy said TfL was already unable to match the rising demand for buses. "The choice as we look forward is not whether people come to London, but if you have enough revenue to cope with them and whether the people who do the poorer paying jobs can access them.
"In 2016, unless there is more money we will start leaving people behind. We've had a 1-2% increase in mileage every year with a fairly substantial reduction in subsidy. The growth in bus demand has far outstripped the mileage because we haven't had the money."
Transport chiefs believe pressure on road space is likely to be even more intense than on the rail and tube network.
Michele Dix, director of planning for TfL, said: "We'll have to manage it radically better or provide new space. We're looking at more of the space being in tunnels – putting certain vehicles underground. We don't want to generate more traffic. As many people we can get to walk, cycle or use public transport we will."
Dix said road tunnel schemes, primarily designed for freight vehicles and deliveries, were an option TfL was considering. One proposal for a 22-mile inner orbital tunnel has been published, including subterranean dual carriageways, although Hendy said the timescale for completion was likely to be decades.
Dix said any such schemes would be tightly controlled to deter a rise in private car use. Both TfL and independent transport experts argue that increased charging for road access seems inevitable. |
package com.jerey.keepgank.widget;
import android.content.Context;
import android.graphics.Rect;
import android.support.v7.widget.RecyclerView;
import android.view.View;
import com.jerey.keepgank.R;
/**
* @author Xiamin
* @date 2017/9/6
*/
public class MyBottomItemDecoration extends RecyclerView.ItemDecoration {
private int dividerHeight;
public MyBottomItemDecoration(Context context) {
dividerHeight = context.getResources().getDimensionPixelSize(R.dimen.space_normal);
}
@Override
public void getItemOffsets(Rect outRect, View view, RecyclerView parent, RecyclerView.State
state) {
super.getItemOffsets(outRect, view, parent, state);
outRect.bottom = dividerHeight;
int pos = parent.getChildAdapterPosition(view);
if (pos == 0) {
outRect.top = dividerHeight;
}
}
public MyBottomItemDecoration setDividerHeight(int dividerHeight) {
this.dividerHeight = dividerHeight;
return this;
}
}
|
<reponame>inrupt/friend-requests-exploration
import SolidAuth from 'solid-auth-client';
import { getDocument } from './DocumentCache';
import { createDocument } from 'tripledoc';
import { rdf, acl as aclUpstream, foaf } from 'rdf-namespaces';
const acl = Object.assign({
default: 'http://www.w3.org/ns/auth/acl#default'
}, aclUpstream);
const APP_ORIGINS = [
'https://launcher-exploration.inrupt.app',
'https://friend-requests-exploration.inrupt.app',
'http://localhost:3000'
];
export async function ensureContainer(url: string) {
if (url.substr(-1) !== '/') {
url += '/';
}
// console.log('creating container', url);
// FIXME: is there a way to create a container with POST?
const scoutUrl: string = new URL('delete-me', url).toString();
await SolidAuth.fetch(scoutUrl, {
method: 'PUT',
body: 'delete me'
});
await SolidAuth.fetch(scoutUrl, {
method: 'DELETE',
body: 'delete me'
});
}
export async function createAclDoc(webId: string, resourceUri: string, otherAuthMode: string, otherAuthPredicate: string, otherAuthObject: string, recursive = false) {
const resourceDoc = await getDocument(resourceUri);
console.log('got doc', resourceUri);
const aclRef = resourceDoc.getAclRef();
console.log('got acl ref', webId, resourceUri, aclRef);
if (!aclRef) {
throw new Error('Could not determine ACL ref for friends list');
}
let aclDoc
try {
await getDocument(aclRef);
console.log('got acl doc');
} catch (e) {
console.log('creating acl doc');
aclDoc = createDocument(aclRef);
}
if (aclDoc) {
console.log('have aclDoc');
const ownerAuthSub = aclDoc.addSubject();
ownerAuthSub.addNodeRef(rdf.type, acl.Authorization);
ownerAuthSub.addNodeRef(acl.accessTo, resourceDoc.asNodeRef());
ownerAuthSub.addNodeRef(acl.default, resourceDoc.asNodeRef());
ownerAuthSub.addNodeRef(acl.mode, acl.Read);
ownerAuthSub.addNodeRef(acl.mode, acl.Write);
ownerAuthSub.addNodeRef(acl.mode, acl.Control);
ownerAuthSub.addNodeRef(acl.agent, webId);
APP_ORIGINS.forEach((origin: string) => {
ownerAuthSub.addNodeRef(acl.origin, origin);
});
const otherAuthSub = aclDoc.addSubject();
otherAuthSub.addNodeRef(rdf.type, acl.Authorization);
otherAuthSub.addNodeRef(acl.accessTo, resourceDoc.asNodeRef());
if (recursive) {
otherAuthSub.addNodeRef(acl.default, resourceDoc.asNodeRef());
}
otherAuthSub.addNodeRef(acl.mode, otherAuthMode);
otherAuthSub.addNodeRef(otherAuthPredicate, otherAuthObject);
if (otherAuthObject !== foaf.Agent) { // for public, origin isn't checked
APP_ORIGINS.forEach((origin: string) => {
otherAuthSub.addNodeRef(acl.origin, origin);
});
}
aclDoc.save();
} else {
console.log('have no aclDoc');
}
}
export async function createFriendsGroupAclDoc(webId: string, friendsGroupUri: string) {
return createAclDoc(webId, friendsGroupUri, acl.Read, acl.agentGroup, friendsGroupUri);
}
export async function createInbox(podRoot: string, webId: string) {
const inboxUrl = new URL('friend-requests-inbox/', podRoot).toString();
await ensureContainer(inboxUrl);
await createAclDoc(webId, inboxUrl, acl.Append, acl.agentClass, foaf.Agent);
return inboxUrl;
} |
It looks like things may be getting back on track for Dov Charney and American Apparel. Yesterday, news ran across the webs regarding American Apparel's upcoming partnership with eBay. Tentatively scheduled to launch on September 1, the e-commerce section of eBay will house American Apparel products. AA's expected to generate several millions within the first year of this partnership, and eBay, striving to bring in more 18-25 year old customers, is looking to benefit also. |
Mory's
Traditions
Several important traditions are maintained at Mory's that have deep resonance with certain Yale alumni and students.
The Whiffenpoofs
The Whiffenpoofs, the a cappella group made up of Yale seniors who are recruited from other Yale undergraduate singing groups, sings weekly, usually on Monday evenings, in the dining areas of the club. They often perform the famous "Whiffenpoof Song" which mentions Mory's as the "place where Louis [or 'Louie'; pronounced as the latter or the French version of the former] dwells." It was through this song, which was sung and recorded by Rudy Vallee, Bing Crosby and Elvis Presley, that the Club became part of the national consciousness in the early part of the twentieth century.
The Spizzwinks
In 1913, four young men met at Mory's to create a light-hearted alternative to the more serious Whiffenpoofs. They decided upon the "Spizzwinks," a reference to a mythical creature to which the Corn Blight of 1906 had been whimsically attributed.
Cups
Another tradition is the ritualistic consumption of a "Cup," in which a party of members gather to share drinks of assorted colors and ingredients (usually containing alcohol, although a non-alcoholic "Imperial Cup" is available) from large silver trophy cups that look like handled urns and are passed amongst the gathered company. The cups are ordered by color, and some are based on sparkling wines, while others are based on beer. There is an elaborate ritual, including at the completion of a cup a drinking song, associated with the tradition. Cups come in many colors including red, gold, purple, blue, green, and velvet.
When a member is about to finish a Cup, he or she faces the decades-old challenge of "cleaning the cup"—removing all moisture from the cup by using only his or her mouth and, to finish the job, hair. Friends to the left and right are at the ready with napkins to minimize drippage during this process. While the member is finishing, and to give that member extra time to "clean the cup," his or her friends are wont to chant the Mory's Song (an adaptation, for a diametrically opposite purpose, of the Salvation Army camp song "Put a Nickel on the Drum", with the finishing member's name as the hero of the song:
It's [Name], it's [Name],
It's [Name] that makes the world go 'round,
It's [Na-ame], [Na-ame],
[Name] that makes the world go 'round,
It's [Name], it's [Name],
It's [Name] that makes the world go 'round,
It's [Name] that makes the world go 'round!
Sing Hallelujah! Sing Hallelujah!
Put a nickel on the drum;
Save another drunken bum!
Sing Hallelujah! Sing Hallelujah!
Put a nickel on the drum and you'll be saved.
I'm H-A-P-P-Y to be F-R-double-E,
F-R-double-E to be S-A-V-E-D,
S-A-V-E-D from the bonds of S-I-N;
Glory, glory, Hallelujah; hip-hooray, amen!
Sing Hallelujah! Sing Hallelujah!
Put a nickel on the drum;
Save another drunken bum!
Sing Hallelujah! Sing Hallelujah!
Put a nickel on the drum and you'll be saved!
I was lying in the gutter,
I was covered up in beer, (BEER!)
Pretzels in my moustache [or "eyebrows"],
I thought the end was near, (BEER!)
Then along came [Name]
And saved me from my curse [or "the hearse"]!
Glory, glory, Hallelujah; sing another verse!
Sing Hallelujah! Sing Hallelujah!
Put a nickel on the drum;
Save another drunken bum!
Sing Hallelujah! Sing Hallelujah!
Put a nickel on the drum and you'll be saved!
At the conclusion of the Mory's Song, the member places the trophy cup, upside down, on top of a cloth (or, for greater challenge due to the latter's higher absorbency, a paper) napkin, whereupon three friends place their respective hands atop the base of the cup and tap firmly. The cup is then whisked away, and the napkin is inspected for any signs of moisture. In decades past, and to date for some more conservative organizations, if the napkin were wet, then the finishing member would be forced to pay for the cup; if the napkin were dry, the member to the finishing member's left—who himself chose to forgo finishing the cup—would have to pay. (Organizations still following these rules often vary them as to the specifics: Some organizations requiring that the cost of the cup be divided among the two or three previous drinkers rather than only the immediately previous one. Some organizations exempt women preceding the "draining" drinker from having to pay, instead assessing only the man or men to that drinker's left for the cup's cost, on the grounds that a woman should not be expected to drain the cup and therefore did not forgo a clear opportunity to do so.) In more modern times, most toasting parties split the bill evenly amongst members, regardless of who fails to drain or declines the opportunity to drain a cup.
Table carving
Another tradition was the encouraged practice of carving the tops of the dining tables at which one sat. The carving might be simply initials or names, or, in the case of the Whiffs' table, a Pendragon rampant.
Yale Political Union
Since the early-to-middle 20th century, some of the parties of the Yale Political Union (particularly those on the right) have adjourned to Mory's, "as is traditional." While the parties no longer actually go to Mory's after debates as party debates have gotten longer and Mory's hours shorter over the years, the tradition of saying that a debate caucus adjourns to Mory's remains. The parties of the Union have, over time, picked up the tradition of dining at Mory's, though, particularly for weekly Friday lunches, and most hold toasting sessions there as often as two or three times each semester. Current and past club members include John Kerry, Bill Clinton, George H. W. Bush, Gerald Ford, John R. Bolton, George Pataki, Joe Lieberman, John Heinz, Paul Mellon, William Howard Taft, and William F. Buckley, Jr..
Special menu items
There are two special menu items that brings the denizens of Mory's back to the carved wooden tables and the walls covered with trophies of the past. They are Baker Soup, a potage heavy on tomato, curry, and cream and topped with croutons; and The Rabbit, a version of Welsh rabbit. |
Sushma Verma
Early life
Sushma Verma born on 3 November 1992 in Shimla, Himachal Prasdesh. Her father “Bhopal Singh Verma” wanted her to stay back close to home. But Sushma's choice was to go to “Portmore Govt Model” school in Shimla. From flirting with multiple sports – volleyball, handball, and badminton. she has been a state level player at these games but cricket somehow found its way to load Shusma. (official website)
Domestic cricket
Before that, she played for the Himachal Pradesh Cricket Association. Under her captaincy, the Himachal team were the runners-up at the Under-19 All-India women's tournament in 2011. She is the first cricketer from Himachal Pradesh, male or female, to represent India in international cricket.
Owing to fewer opportunities in domestic, she started playing for Railways. She played along with Mithali Raj, Harmanpreet Kaur and Punam Raut.
International cricket
Verma was part of the Indian team to reach the final of the 2017 Women's Cricket World Cup where the team lost to England by nine runs. |
def _match_and_label_boxes(self, proposals, stage, targets):
def label_and_sample_single_image(inputs):
proposals_dict, targets_dict = inputs
is_valid_gt_boxes = targets_dict.pop('is_valid')
is_crowd = tf.cast(targets_dict.pop('gt_is_crowd'), tf.bool)
difficult = tf.cast(targets_dict.pop('gt_difficult'), tf.bool)
valid_bool = is_valid_gt_boxes & ~is_crowd & ~difficult
target_boxlist = box_list.BoxList.from_tensor_dict(targets_dict)
valid_target_boxlist = box_list_ops.boolean_mask(target_boxlist, valid_bool)
crowd_target_boxlist = box_list_ops.boolean_mask(target_boxlist, is_crowd)
difficult_target_boxlist = box_list_ops.boolean_mask(target_boxlist, difficult)
is_valid_proposals = proposals_dict.pop('is_valid')
num_proposals = tf.shape(is_valid_proposals)[0]
image_shape = proposals_dict.pop('image_shape')
proposal_boxlist = box_list.BoxList.from_tensor_dict(proposals_dict)
proposal_boxlist = box_list_ops.boolean_mask(proposal_boxlist, is_valid_proposals)
match_quality_matrix = box_list_ops.pairwise_iou(
valid_target_boxlist, proposal_boxlist
)
crowd_matrix = box_list_ops.pairwise_iou(
crowd_target_boxlist, proposal_boxlist
)
difficult_matrix = box_list_ops.pairwise_iou(
difficult_target_boxlist, proposal_boxlist
)
matched_idxs, proposals_labels = self.proposal_matcher(
match_quality_matrix, crowd_matrix, difficult_matrix)
fg_inds = tf.cast(tf.where(tf.equal(proposals_labels, 1))[:, 0], tf.int32)
bg_inds = tf.cast(tf.where(tf.equal(proposals_labels, 0))[:, 0], tf.int32)
fg_targets = tf.gather(matched_idxs, fg_inds)
gt_classes = tf.dynamic_stitch(
[fg_inds, bg_inds],
[
tf.gather(target_boxlist.get_field('gt_classes'), fg_targets),
tf.zeros_like(bg_inds, dtype=tf.int64) + self.num_classes,
]
)
gt_boxes = tf.gather(target_boxlist.boxes, matched_idxs)
proposal_boxlist.set_field('gt_classes', gt_classes)
proposal_boxlist.set_field('gt_boxes', gt_boxes)
proposal_boxlist.add_field('is_valid', tf.ones_like(gt_classes, tf.bool))
proposal_boxlist = box_list_ops.pad_or_clip_boxlist(proposal_boxlist, num_proposals)
proposal_dict = proposal_boxlist.as_tensor_dict()
proposal_dict['image_shape'] = image_shape
return proposal_dict
proposals_dict = proposals.as_tensor_dict()
targets_dict = targets.as_tensor_dict()
dtype = {
field: value.dtype for field, value in proposals_dict.items()
}
proposals_dict = tf.map_fn(
label_and_sample_single_image,
[proposals_dict, targets_dict],
dtype=dtype,
)
proposals = box_list.BoxList.from_tensor_dict(proposals_dict, trackings=['image_shape'])
return proposals |
Effect of synchronous activation of medullary inspiratory bulbospinal neurones on phrenic nerve discharge in cat. The effects on phrenic nerve discharge elicited by intraspinal stimulation which produced synchronous activation of bulbospinal inspiratory neurones were investigated in chloraloseurethane anaesthetized, paralysed, vagotomized and artificially ventilated cats. Descending respiratory axons were activated in the ventrolateral spinal cord at the second cervical level using either monopolar or bipolar stimulation (25200 microA, 100 microseconds, 1300 Hz). Activation of bulbospinal axons was confirmed by recording both orthodromic phrenic nerve excitation and antidromic spike invasion of single, inspiratory modulated units in either the dorsal respiratory group (d.r.g.) or ventral respiratory group (v.r.g.). Antidromic activation of inspiratory bulbospinal neurones was confirmed by the criteria of high frequency following and collision tests. Spinal cord stimulation at intensities of 100 microA antidromically activated approximately half of the inspiratory bulbospinal neurones in the d.r.g. and v.r.g. Stimulation pulses delivered to the spinal cord elicited an orthodromic excitation of the ipsilateral phrenic nerve lasting 212 ms during inspiration. The onset latency of excitation was 24 ms, decreasing as inspiration progressed. Following the initial excitation there was a 430 ms period of reduced phrenic nerve discharge. Continuous trains of stimuli (less than 100 microA, 100 microseconds, 1300 Hz) or phrenic gated trains delivered during every fourth inspiratory or expiratory cycle had little or no effect on the duration of inspiration or expiration. Brief trains (400 ms, 50 Hz, 100 microA) of bilateral spinal cord stimulation delivered at various delays from the onset of inspiration had only a transient effect on the pattern of phrenic nerve discharge, with no noticeable effect 60 ms after termination of stimulation. Based on the assumption that synchronous activation of a portion of the central pattern generator for respiration would phase shift or reset the rhythm, we conclude that the bulbospinal inspiratory neurones are not responsible for generation of respiratory timing signals and play, at most, a limited role in the generation of the augmenting central inspiratory activity. |
<filename>src/main/java/com/fns/monbox/repository/CloudVirtualNetworkRepository.java
package com.fns.monbox.repository;
import java.util.Collection;
import java.util.List;
import org.springframework.data.repository.CrudRepository;
import com.fns.monbox.model.CloudVirtualNetwork;
import com.fns.monbox.model.NameValue;
public interface CloudVirtualNetworkRepository extends CrudRepository<CloudVirtualNetwork, String> {
CloudVirtualNetwork findByCollectorItemId(String collectorItemId);
Collection<CloudVirtualNetwork> findByTags(List<NameValue> tags);
CloudVirtualNetwork findByVirtualNetworkId(String virtualNetworkId);
Collection<CloudVirtualNetwork> findByvirtualNetworkIdIn(List<String> virtualNetworkId);
Collection<CloudVirtualNetwork> findByAccountNumber(String accountNumber);
}
|
<reponame>irin4eto/open-commerce-search<filename>ocs-plugin-spi/src/main/java/de/cxp/ocs/spi/indexer/DocumentPreProcessor.java
package de.cxp.ocs.spi.indexer;
import java.util.Map;
import de.cxp.ocs.config.FieldConfigAccess;
import de.cxp.ocs.model.index.Document;
/**
* {@link DocumentPreProcessor} implementations can be used to alter product
* data before they get transformed into
* {@link de.cxp.ocs.indexer.model.IndexableItem}s.
* Several implementations can be configured to run one after another, where
* each processor get's the manipulated record value of the former processor.
*
* @author hjk, rb
*/
public interface DocumentPreProcessor {
/**
* DataPreProcessor MUST have a no-args constructor. To configure it
* afterwards, this method will be used.
*
* @param fieldConfig
* @param preProcessorConfig
* custom string-to-string map that can be configured per
* DocumentPreProcessor.
*/
void initialize(FieldConfigAccess fieldConfig, Map<String, String> preProcessorConfig);
/**
* Called for each source document.
*
* @param sourceDocument
* @param visible
* weather or not the record is currently marked for indexing.
* @return <code>true</code> if the record should be indexed,
* <code>false</code> otherwise.
*/
boolean process(final Document sourceDocument, boolean visible);
}
|
With an apparent nod from the U.S., the Ecumenical Patriarch’s ruling from Istanbul severed 1000-year ties between Moscow and the Orthodox church in Ukraine, raising further tensions between Kiev and Moscow, as Dmitry Babich reports.
The Istanbul-based Ecumenical Patriarch Bartholomew I of Constantinople, an authority completely outside Ukraine, on Oct. 11 stripped away the canonical authority of the Ukrainian Orthodox Church—Moscow Patriarchate (MP), sparking a crisis with Russia.
The 1030-year old church is headed by Patriarch Kirill in Russia and the Russian church responded by severing ties to the Istanbul patriarch. Tensions have now been raised even further in the crisis between Ukraine and Russia that erupted after the U.S.-backed 2014 coup in Kiev that overthrew an elected president who tilted towards Moscow.
In Washington, the events were reported in The Washington Post as part of Ukraine’s struggle to “withdraw from Moscow’s control.” In Europe, Italy’s Deputy Prime Minister and Minister of the Interior Matteo Salvini made the sober warning in the Austrian newspaper Der Standard that the religious interference in Ukraine could provoke a war.
Bartholomew’s action is seen as a first step to giving full autonomy, known as “autocephaly” in the Orthodox faith, to the Ukrainian Orthodox Church of Kiev Patriarchate (KP), a heretical split-off that was created only in 1992 just after the dissolution of the Soviet Union and Ukraine’s independence.
The KP church is headed by a self-styled leader named Mikhail Denisenko, who goes by the name Patriach Filaret. He is a defrocked former bishop in the Moscow Patriarchate of Ukraine.
The MP’s lineage goes back to the tenth century Christian conversion of all the people of Kievan Rus, the proto-state that was precursor to the nations of Russia, Ukraine and Belarus. Its authority in Ukraine was established in 1686 by the same Constantinople Ecumenical Patriarchate.
Bartholomew reversed his seat’s own 332-year-old decision. While the Ecumenical Patriarch is known as “the first among equals,” among Orthodoxy’s 14 autocephalic churches, he has no authority to rule over them. Unlike Roman Catholicism, Orthodoxy has no single church authority that can impose decisions over all the others.
The 14 churches are supposed to be independent of governments. But in Ukraine, Petro Poroshenko, the anti-Russian president installed after the coup, and other government forces, are using the ruling to further erode Russian influence.
Members of the Moscow church in Ukraine have already been the targets of violent assaults by thugs trying to disrupt worship services, and such conflict is being fueled by politicians’ rhetoric.
In October, when Constantinople lifted Denisenko’s ex-communication, Poroshenko called the decision “a victory of good over evil, light over darkness.” He also said that recognition of the renegade Ukraine church would mean severing all links to Orthodox Russia and its “Moscow demons,” reported gazeta.ru.
Bartholomew’s decision didn’t come out of thin air, and the geopolitical implications are clear: breaking Russia’s ties to the Ukrainian people. This was demanded by Poroshenko, and supported by Denisenko, whose church has never been recognized by the 14 other churches.
On Oct. 31, Denisenko made his view clear in a statement to RFE/RL. “We will be striving to have a single Orthodox Church in Ukraine and to make sure that the Russian [Orthodox] Church is not hiding under the Ukrainian name while, in essence, it is Russian,” he said.
He called for faithfulness to the canonical church, the Moscow Patriarchate, and says he’s “ready to go anywhere and talk to anyone” to prevent the schism among the Orthodox inside Ukraine and remove barriers separating the faithful in the two countries.
The break in eucharistic communication means that the priests of the two patriarchates won’t be able to hold church services together.
While Western media have played the break as an aggressive act by Moscow, the reality is more complex. The Russian Orthodox Church is the largest congregation among the approximately 300 million Eastern Orthodox Christians, and Kirill went to Istanbul to meet the Ecumenical Patriarch in August to try to avert any actions that would harm the unity.
On October 31, Russian President Vladimir Putin referred to the action against the Ukrainian church in remarks to the World Congress of Russian Compatriots, an organization uniting people of Russian origin from all over the world. “Politicking in such a sensitive sphere as religion has always led to grave consequences, first and foremost for the people who got involved in this politicking,” he said. He also referenced a “war” on Russian historical monuments by some forces in Ukraine.
That statement came four days after Bartholomew recognized the breakaway Ukrainian church.
Dmitry Babich is a multilingual Russian journalist and political commentator. Born in 1970 in Moscow, graduated from Moscow State University (department of journalism) in 1992. Dmitri worked for Russian newspapers, such as Komsomolskaya Pravda and The Moscow News (as the head of the foreign department). Dmitri covered the Chechen war as a television reporter for TV6 channel from 1995 to 1997. Since 2003 he has worked for RIA Novosti, RT, and Russia Profile. Dmitry is a frequent guest on the BBC, Al Jazeera, Sky News and Press TV. |
<reponame>lignay/matrixcube
package pebble
import (
"testing"
cpebble "github.com/cockroachdb/pebble"
"github.com/stretchr/testify/assert"
)
func TestHasEventListener(t *testing.T) {
assert.False(t, hasEventListener(cpebble.EventListener{}))
assert.True(t, hasEventListener(cpebble.EventListener{BackgroundError: func(e error) {}}))
assert.True(t, hasEventListener(cpebble.EventListener{CompactionBegin: func(ci cpebble.CompactionInfo) {}}))
assert.True(t, hasEventListener(cpebble.EventListener{CompactionEnd: func(ci cpebble.CompactionInfo) {}}))
assert.True(t, hasEventListener(cpebble.EventListener{DiskSlow: func(dsi cpebble.DiskSlowInfo) {}}))
assert.True(t, hasEventListener(cpebble.EventListener{FlushBegin: func(dsi cpebble.FlushInfo) {}}))
assert.True(t, hasEventListener(cpebble.EventListener{FlushEnd: func(dsi cpebble.FlushInfo) {}}))
assert.True(t, hasEventListener(cpebble.EventListener{ManifestCreated: func(dsi cpebble.ManifestCreateInfo) {}}))
assert.True(t, hasEventListener(cpebble.EventListener{ManifestDeleted: func(dsi cpebble.ManifestDeleteInfo) {}}))
assert.True(t, hasEventListener(cpebble.EventListener{TableCreated: func(dsi cpebble.TableCreateInfo) {}}))
assert.True(t, hasEventListener(cpebble.EventListener{TableDeleted: func(dsi cpebble.TableDeleteInfo) {}}))
assert.True(t, hasEventListener(cpebble.EventListener{TableStatsLoaded: func(dsi cpebble.TableStatsInfo) {}}))
assert.True(t, hasEventListener(cpebble.EventListener{WALCreated: func(dsi cpebble.WALCreateInfo) {}}))
assert.True(t, hasEventListener(cpebble.EventListener{WALDeleted: func(dsi cpebble.WALDeleteInfo) {}}))
assert.True(t, hasEventListener(cpebble.EventListener{WriteStallBegin: func(dsi cpebble.WriteStallBeginInfo) {}}))
assert.True(t, hasEventListener(cpebble.EventListener{WriteStallEnd: func() {}}))
}
|
A Democratic senator visited the home state of a GOP House chairman Monday and slammed the Republican’s probe of state attorneys general investigating climate change.
During an event at the Texas statehouse on Monday, Sen. Sheldon Whitehouse Sheldon WhitehouseSenate Dems seek to turn tables on GOP in climate change fight This week: Congress, Trump set for showdown on emergency declaration Senate reignites blue slip war over Trump court picks MORE (D-R.I.) raised questions about House Space, Science, and Technology Committee Chairman Lamar Smith’s opposition to state probes into ExxonMobil Corp.
ADVERTISEMENT
Smith has subpoenaed documents from two Democratic attorneys general who are investigating allegations that the Irving, Texas-based company lied about the extent of its knowledge of climate change. Smith and Exxon allies have said those investigations invade the free speech rights of Exxon and its scientists.
But Whitehouse noted that Smith has received campaign contributions from Exxon, and the Democrat called the attorneys general subpoenas “unprecedented” congressional actions.
“Is it fraud, in which case something should be done? Or is it First Amendment protected speech, in which case, everybody stands down? That is the question that the attorneys general are pursuing,” Whitehouse said of the accusations against Exxon.
“For the representative to use his powers of office to try to interfere, that crosses the bounds of federalism, is doubly unprecedented, reeks of conflict of interest and completely misstates the pertinent law."
Democrats have long objected to Smith’s subpoenas of Eric Schneiderman and Maura Healey, the Democratic attorneys general of New York and Massachusetts, respectively, who are leading the Exxon investigations.
But Smith and Republicans say they are playing an important role by attempting to look into the details of those probes. Smith last month said his committee has a “constitutional obligation” to examine the investigations.
“My committee is operating within its jurisdiction to preserve scientific freedom,” Smith said in a statement.
“Sen. Whitehouse's comments are just environmental activists' talking points, and won't stop the committee from fulfilling its constitutional oversight responsibilities … It is my hope that the AGs and outside groups will come to the table in the spirit of preserving scientific research free from intimidation.”
—This post was updated at 7:10 p.m. |
Experimental Investigation of Tensile Damage Mechanisms on 3-D Braided Composites with AE In this paper, the fracture process of 3D four-directional carbon/epoxy braided composites with different braiding angles under the monotonic tensile loading were investigated by the acoustic emission (AE) technique. The AE cumulative energy, event rate, amplitude, and the peak frequency were analyzed. At the same time, combining with the load-displacement curve varying feature, the fracture processes were divided into different stages to deeply understand the damaged mechanisms of the textile composites. Furthermore, the fracture surfaces of the specimens were observed under optical microscopy. Results reveal that the behavior of AE parameters described well the fracture process in the 3D braided composites with different braiding angles, and the damage mechanisms of the composites can be successfully identified by AE characteristics. |
Stimulation of Cl(-) secretion by chlorzoxazone. We previously demonstrated that 1-ethyl-2-benzimidazolone (1-EBIO) directly activates basolateral membrane calcium-activated K(+) channels (K(Ca)), thereby stimulating Cl(-) secretion across several epithelia. In our pursuit to identify potent modulators of Cl(-) secretion that may be useful to overcome the Cl(-) secretory defect in cystic fibrosis (CF), we have identified chlorzoxazone , a clinically used centrally acting muscle relaxant, as a stimulator of Cl(-) secretion in several epithelial cell types, including T84, Calu-3, and human bronchial epithelium. The Cl(-) secretory response induced by chlorzoxazone was blocked by charybdotoxin (CTX), a known blocker of K(Ca). In nystatin-permeabilized monolayers, chlorzoxazone stimulated a basolateral membrane I(K), which was inhibited by CTX and also stimulated an apical I(Cl) that was inhibited by glibenclamide, indicating that the G(Cl) responsible for this I(Cl) may be cystic fibrosis transmembrane conductance regulator (CFTR). In membrane vesicles prepared from T84 cells, chlorzoxazone stimulated Rb(+) uptake in a CTX-sensitive manner. In excised, inside-out patches, chlorzoxazone activated an inwardly-rectifying K(+) channel, which was inhibited by CTX. 6-Hydroxychlorzoxazone, the major metabolite of chlorzoxazone, did not activate K(Ca), whereas zoxazolamine (2-amino-5-chlorzoxazole) showed a similar response profile as chlorzoxazone. In normal human nasal epithelium, chlorzoxazone elicited hyperpolarization of the potential difference that was similar in magnitude to isoproterenol. However, in the nasal epithelium of CF patients with the DeltaF508 mutation of CFTR, there was no detectable Cl(-) secretory response to chlorzoxazone. These studies demonstrate that chlorzoxazone stimulates transepithelial Cl(-) secretion in normal airway epithelium in vitro and in vivo, and suggest that stimulation requires functional CFTR in the epithelia. |
#moon landing
import math
import time
import krpc
conn = krpc.connect(name='Vessel Landing')
vessel = conn.space_center.active_vessel
obt_frame = vessel.orbit.body.non_rotating_reference_frame
orb_speed = conn.add_stream(getattr, vessel.flight(obt_frame), 'speed')
altitude = conn.add_stream(getattr, vessel.flight(), 'surface_altitude')
#srf_speed = conn.add_stream(getattr, vessel.flight(srf_frame), 'speed')
print ("Deorbiting Vessel...")
vessel.control.speed_mode = vessel.control.speed_mode.surface
ap = vessel.auto_pilot
ap.sas = True
ap.sas_mode = ap.sas_mode.retrograde
while altitude() > 15000:
pass
while (orb_speed() > 500):
vessel.control.throttle = 1.0
vessel.control.throttle = 0.0
while altitude() > 7000:
pass
print("7000 done")
while (orb_speed() > 250):
vessel.control.throttle = 1.0
vessel.control.throttle = 0.0
while altitude() > 1500:
pass
print("1500 done")
while (orb_speed() > 100):
vessel.control.throttle = 1.0
vessel.control.throttle = 0.0
print("pre300")
while altitude() > 300:
pass
print("300 done")
while altitude() > 50:
if orb_speed() > 12:
vessel.control.throttle = 0.5
else:
vessel.control.throttle = 0
print("50 done")
while altitude() > 5:
if orb_speed() > 10:
vessel.control.throttle = 0.2
else:
vessel.control.throttle = 0
vessel.control.throttle = 0
|
<gh_stars>0
import { createGlobalStyle } from 'styled-components'
const GlobalStyle = createGlobalStyle`
body {
background-color: #fff;
color: #30336b;
font-family: 'Noto Sans JP', sans-serif;
font-size: 1.4rem;
}
a {
color: #227093;
}
ul, ol {
list-style: none;
}
hr {
margin: 1.8rem 0;
}
`
export default GlobalStyle
|
An Eco-Benign Approach for Unhairing Goat Skin Using Ozone Unhairing or hair removal is an important step in leather processing. The conventional lime-sulfide process used for unhairing operation generates considerable waste and toxic hydrogen sulfide in the effluent when mixed with acidic effluent. Oxidative chemicals offer an alternative to the use of sodium sulfide in a rapid unhairing reaction. Oxidative unhairing was investigated using hydrogen peroxide, chlorine dioxide, and calcium peroxide, with unsatisfactory results. Ozone being a good oxidative agent was tried in this work in unhairing goat skin. Experiments on the use of ozone with oxygen/air as feed gas were carried out to study the unhairing effect on different regions of a goat skin. Unhairing was done in a static reactor. The wet blue produced from the skin underwent physical testing and was compared with the conventional operation. COD of the spent liquors were tested for comparison. The experimental results indicate that ozone as an oxidative agent could be used for depilation without affecting the physical and chemical characteristics of the resulting leather. The use of ozone for unhairing operation in place of sodium sulfide results in hair recovery and reduction of pollution loads. |
Optimization of Corporate Branding Strategy in Higher Education as the Marketing Sustainability: Study at Universitas Pembangunan Nasional (UPN) 'Veteran' Jawa Timur The rise of the phenomenon of state institutions which are required to become independent both financially and management are forced to be competitive with each other, both from domestic and foreign private institutions. It's forcing the institution to improve the competitiveness both in terms of services and achievements to hold its existence in the current of global markets. UPN "Veteran" Jawa Timur is one of the new state institutions, which is expected to be independent in both, financial and management, and they use the brand "bela Negara" as the corporate branding strategy. As a higher education institution have to improve tri dharma services. Corporate branding is a strategy to increase the market value of an organization. The three stages in corporate branding strategy are the goal (vision), culture, and externalization. This research focuses on identifying the vision of how awareness among users. Two independent variables, namely brand association and brand reputation, are taken from the theory of corporate branding strategy. While the brand image variable as a moderator and brand awareness as an independent variable. Samples were taken from 411 UPNVJT students by purposive random sampling. The questionnaire as the instrument research which uses a Likert scale. All item and variable indicators are tested both reflective and formative with the SmartPLS 3 software. From the results of the outer and inner model, it is found that the brand image as a moderator has the most influence on brand awareness. Overall, it shows that it supports the existing hypothesis, and the variable which has the smallest influence on brand awareness is the brand association. Introduce the Problem The brand has a very important role for the organization because it is an invisible asset that can become the identity of an organization and increase loyalty and higher margins in the long run (Kotler, Philip. Armstrong, 911 2012). A brand is a form of business strategy or other organization to communicate the personality and core of the organization both visually and non-visually (forbes communication council, 2018). The brand is at the forefront of communicating products and services. Organizational value can grow or decrease exponentially through brands. This is a challenge that needs to be studied and developed from various parties, both business and non-business organizations. Where during the last decade, many organizations have begun branding themselves as a form of organizational differentiation from one another, whether it is strengthening their profile in the public, through websites, advertisements, media issues, and other forms of communication. In the current era of globalization, branding strategy is not only applied in business organizations, but also extends to various sectors of the organization (Joseph and Abidemi, 2016). In the non-business sector, for example, the emergence of various city branding, even country branding to promote the existence of a city or country in the eyes of the world. Efforts to strengthen branding in an organization are often referred to as corporate branding strategies. Corporate branding is a strategy to increase the market value of an organization. Basically, there are three main stages in corporate branding strategy, namely: goal (vision), culture, and externalization. In previous studies of (Siti Ning Farida, 2019) has been carried out at the vision stage, which emphasizes the internalization of a brand. So that in this study, more focused on the identification and culture stages for later research aimed at external. Corporate brand culture forms the core values of a brand and creates an organizational identity and has values that become the competitive advantage of an organization. Corporate brand culture is developed through several variables that influence between brand association, brand image, and brand reputation. Prior to the culture stage, previous research showed the need for corporate brand awareness in community organizations. Brand awareness in this context is the awareness of members of the organization of the corporate brand stated in the vision and mission of an organization by leaders at the managerial level. Since 6 December 2018 UPN "Veteran" Jawa Timur (UPNVJT) have officially become universities with Public Service Agency (BLU in Bahasa) by the Ministry of Finance of the Republic of Indonesia. It means UPNVJT has been considered capable of managing finances independently and is demanded to improve tri-dharma education services (pers UPN, 2018). This requires an institution to improve competitiveness in terms of both service and performance achievements. UPNVJT was previously a private tertiary institution under the ministry of defense, driven by the increasing need for tertiary institutions so that UPNVJT was encouraged to become a state university by carrying out its identity as a "bela Negara" campus. Seeing the inauguration with the identity of "bela Negara " not long ago formed, it is interesting to do a more in-depth study related to how to optimize the "bela Negara" brand at UPNVJT as a form of corporate branding strategy. Explore the Importance of the Problem Based on the gap phenomenon, thus, this study has the aim to examine the related corporate branding of corporate brand awareness. So this research is entitled "optimization of corporate branding strategy as a form of sustainability marketing: a study at the" Veteran "National Development University (UPN) of East Java. The formulation of the problems that are the focus of this research are as follows: 1. How corporate branding (brand association and brand reputation) affects brand awareness at UPN "Veteran" East Java? 2. How corporate branding (brand association and brand reputation) affects brand awareness by mediating the brand image at UPN "Veteran" East Java? Describe Relevant Scholarship Corporate Branding Corporate branding is one form of brand building strategy from organizations to create their brand perspectives in society. Corporate branding refers to the mindset that comes from within the organization to the outside, which means experience, encounter, and company perceptions in the eyes of customers or the wider community. According to (Hatch and Williamson, 2003) Corporate branding describes the company, sending messages to users about the quality and other attributes of the product or service. Corporate branding can be seen as a systematic, planned, and implemented process aimed at creating and maintaining a positive image and reputation for the entire organization (Punjaisri and Wilson, 2011). The important role of corporate branding can be seen from the organizational behavior and culture that is formed. Based on the research of incorporate branding strategy, attention needs to be paid to 3 main points, namely: strategic vision, organizational culture, and corporate image (figure 1). Corporate brands have different roles in consumer perception. This means that evaluation is needed, whether the perceptions in the organization are the same as the perceptions held by consumers. The corporate brand emphasizes on the image formed, reputation, and association of the organization and all existing stakeholders. Brand Image Brand image has long been known as an important concept in marketing, but it also has an important role in building a brand in an organization (J, Mao, 2010). Defines brand image as a set of brand associations associated with whatever memory to a brand, usually in a meaningful way and can be defined as a combination of consumers' perceptions and beliefs about a brand. Furthermore, Kotler and (Kotler, Philip., et al., 1999) define brand image as "a set of beliefs that consumers have about something related to the brand's uniqueness. (Bivainiene L, 2007) in () defines brand image as "a multifunctional collection of tangible and intangible features, which enable consumers to do product identification." Brand Reputation The term reputation and image are often used together so that they are relatively difficult to distinguish between in establishing corporate branding. However, further studies find the difference between the two, brand reputation is consumer perception based on experience with services or the use of a product (Kimpakorn and Tocquer, 2010), while brand image is consumer perception based on information or opinions from various sources giving rise to perceptions prior to experience ( Yang & sing, 2008). Meanwhile, Gray and Balmer say the difference between brand image and brand reputation is whether the individual is able to describe an organization without having experience with the organization while brand reputation is more profound, based on personal experience. In (Pinson & Ford, 2012) stated that brand reputation is defined as a form of collective representation of several images that are formed from time to time based on organizational identity, programs, and performance (Argenti and Druckenmiller, 2004). Another study found that reputation is a set of perceptions held by external parties or stakeholders because it focuses on reputation, credibility, legitimacy in an organization (Bromley, 1993;Davies & Mil, 1988) Brand Association Jamil & Wong are of the view that brand association is defined as the strength of benefits offered by brands. Krishnan considers that "brand association" can be used as a general term to represent the relationship between two nodes, which suggests brand association in the customer's mind. Brand associations will help consumers find and respond to information. In addition, brand associations will provide consumers with purchase reasons, because most brand associations relate to brand attributes, consumer target markets, and benefits consumers need, so they form the basis of brand loyalty and consumer purchasing decisions (Len T.W, Cindy M, 2007). Brand Awareness Brand awareness is the ultimate definition of brand recognition, meaning that the potential for existence is easy to remember, information, and ideas about products are easily recognized (Bilgili, B., &Ozkul, 2015). (Ekhveh, A & Darvishi, 2015) show that brand awareness is associated with information nodes in memory; The customer's ability to recognize a brand in various conditions reflects their awareness of that brand. (Jamil, B., & Wong, 2010) Electronic copy available at: https://ssrn.com/abstract=3454117 added value and is also considered as one of the key factors that influence consumer-level knowledge about brands. Method The research method used in this study is a quantitative approach. In the quantitative approach by distributing questionnaires. The interview is used to make more consideration depth related to conditions in the field. Scale Operation Measurement of variables using a Likert Scale that allows respondents to answer each question item that is able to describe how their attitudes and behavior ( Data Collection and Sampling Procedure A population is an object or subject in a group of individuals who have the same characteristics. The population in this study were all UPNVJT students totaling 10,796 (forlap dikti, 2018 / `2019). Data collection techniques using purposive random sampling to be able to represent the entire population. There are two techniques used by revolutionary distribution, manually and online. In total, 444 questionnaires were distributed, and then the questionnaire selection process could be used in a number of 411 respondents. The sample size is sufficient to represent a population of ten thousand in number using the Yamane approach with a precision level of ± 5% and a confidence level of 95%. Results The respondents of the survey had some characteristics, as described in Table 1. Overall, 411 participants were obtained, of which 213 respondents were obtained manually, and 198 others were obtained from online distribution. The demographic picture of the research respondents is 152, while the number of men is 259. Most of them are in the fourth semester with the most 160, the same number of respondents are from the faculties of social and political science. 308 of them have taken national defense courses, and 237 of them are active students in organizations. Scale Accuracy analysis Accuracy scale on the variables used in the study was tested using smart PLS software, with a focus on several focus on reflective measurements namely outer loading, AVE, CR, Cronbach alpha and formative measurements seen from the level of the outer weight. Outer loading is an external standard value with a variant size of not less than 50%, so in this study, a minimum value of 0.5 and indicator items that have values below 0.5 are removed. Next is the Average Variance Extracted (AVE) which shows the level of convergent validity where the minimum value limit of 0.5 indicates the value of the variable used indicates more than half when compared to other variables. Composite reliability (CR) to measure internal consistency in the model, where the minimum value is 0.6, if the value is below 0.6, it can be concluded that the variables used are less reliable. Cronbach alpha is used to strengthen the reliability test of a variable, where the minimum value is 0.6, this is the same as the minimum value in CR. Furthermore, formatively viewed from the level of outer weight in each item idator, in general, the value of outer weight is always lower than outer loading, because outer weight is the result of multiple regression (). Outer weight is used to evaluate the contribution of item indicators and their relevance. The results of the scala item test in the study showed that the entire load was obtained values of more than 0.5 (minimum limit), using several item indicators, read: B.AW4, BA 1, BA 2, BA 4, and BA 11. available can be withdrawn Item indicators meet the criteria and can be continued in the next test. Outside weight values look reasonable compilation of values outside of outside loading, and there is no limit to outside weight because this only shows the contribution of each item. AVE all variables determine the value above 0.5 unless BA has not been assessed very close, and if the round has fulfilled 0.5 then, in this case, it can be concluded that all variables are valid. CR and Cronbach alpha shows the value of the level of reliability of the variables in this study all variables have a value of more than 0.4 then it can be concluded that all the variables that are already quite reliable. Hypothesis Testing After the item scale test both reflectively and formally is declared valid and reliable, so that the inner model of the bootstrapping model can be continued to estimate the path coefficient values, which include: R2, f2, and Q2. The value of R2 is an evaluation measure of the effect of the independent variable with the dependent variable, with values> 0.67 (substantial), 0.33 (moderate), 0.19 (weak). The value of f 2 represents the level of influence of the dependent variable on the dependent variable, where the value <0.02 (weak influence), <0.12 (enough influence), <0.35 (strong influence). Q2 shows the values in the construct have predictive relevance if the value of Q2> 0 then it is proven, and vice versa. Based on Figure 2, it can be seen the results of bootstrapping and blindfolding test from smartPLS software, the level of influence of the independent variable BA BAW is 0.172 indicating the level of influence is enough, BA BI is 0.277 showing enough influence, BR B.AW is 0.346 indicating moderate influence, BR BI is 0.557 shows a strong influence and BI B.AW shows a strong influence of 0.621. Then r2 is indicated by the dependent variable BI of 0.314 by BA, meaning BA has a moderate effect on BI, whereas BI by BR is 0.624, which means it has strong or substantial. The level of Q2 by the dependent variable respectively, BI = 0.362 and BAW = 0.81, when Q2> 0 it can be concluded that the values examined have been constructed well and have good predictive relevance too. Picture 2. Blindfolding test results of the inner model Sources: Data Processed Discussion and conclusion This research focuses on strengthening brand awareness through corporate branding strategy, which consists of two independent variables (brand association and brand reputation) and two dependent variables (brand image and brand awareness). Based on the results of hypothesis testing, the results of brand associations, or things related to the brand, will affect brand awareness, this is evidence that the first hypothesis is acceptable and in accordance with previous research which states that brand association helps improve brand awareness by users. While brand reputation is at a fairly strong level of brand awareness which proves that the fourth hypothesis and this is also supported by previous research () which shows that brand awareness is built on brand reputation. Then the second hypothesis test between brand association to brand image shows a sufficient relationship and supports the hypothesis that was predicted at the beginning, this is also based on research conducted by which discusses related brand image that is influenced by things related to the brand (association) both physically and non-physically. Furthermore, the third hypothesis was also successfully proved by the level of the relationship between brand reputation and brand image, showing a strong relationship that is in accordance with the research which is in accordance with these results. In theory, the results of this study prove that brand awareness can be built by several factors, namely brand image, brand association, and brand reputation, practically this research can be used as a reference when an institution builds brand awareness, it must start by making associations and reputations related to the brand, and building a dimage brand that supports brand awareness building up perfectly. Based on the results of this study, it can be concluded that brand awareness is influenced by brand image, brand association, and brand repairs, both directly and indirectly. Brand image as mediation has a significant influence because it has the most dominant influence on brand awareness. Whereas the least dominant influence on brand awareness is brand association. So based on the current research, which was taken empirical studies at UPN VJT, sequentially from the most dominant, brand awareness is influenced by brand image, brand reputation, and brand association. Then the brand image as a dominant mediator is influenced by brand repairs rather than brand associations. |
def noaaDateConv(dataframe):
import pandas as pd
year, month, day, hour, minute, cpd = [], [], [], [], [], []
cpd_name = dataframe.columns[1]
for index, value in dataframe.iterrows():
year.append(value.datetime.year)
month.append(value.datetime.month)
day.append(value.datetime.day)
hour.append(value.datetime.hour)
minute.append(value.datetime.minute)
cpd.append(value[cpd_name])
dataframe.drop(['datetime', cpd_name], axis=1, inplace=True)
dataframe = dataframe.reset_index()
dataframe.drop('index', axis=1, inplace=True)
for item in [year, month, day, hour, minute, cpd]:
item = pd.Series(item)
dataframe = dataframe.merge(item.to_frame(), left_index=True, right_index=True, how='inner')
dataframe.columns = ['year', 'month', 'day', 'hour', 'minute', cpd_name]
return dataframe |
Formal declaration of the Malaysia Airlines MH370 disappearance as an accident frees the carrier to begin certain procedural work, but the causal factors behind the loss remain undetermined.
The investigation has reached no conclusions over the reasons behind the Boeing 777-200ER’s vanishing while en route to Beijing on 8 March last year.
No trace of the aircraft has been located but the Malaysian government referred to the definition of ‘accident’ afforded by Annex 13 to the Chicago Convention – a definition based purely on the status of the aircraft and its occupants, not the circumstances.
Annex 13 defines an accident as an occurrence associated with aircraft operation which results either in substantial airframe damage – with the exception of certain components – or fatalities or serious injury among those on board.
It also applies to situations in which an aircraft is listed as missing, the status adopted when official search efforts have been terminated without the location of wreckage.
Given the time elapsed since satellite communications data tracked the aircraft to a remote part of the southern Indian Ocean, with no landing area, the Malaysian government considers improbable that any of the 239 occupants survived.
The unlikelihood of finding survivors had already been conveyed in April last year, when the Australian government stated that the surface search effort would transition to an underwater phase.
While the search for the wreckage is continuing, the Malaysian government says that, under the circumstances, survivability after 327 days would be “highly unlikely” – a declaration sufficient to meet the Annex 13 definition of ‘accident’.
But this does not rule out any of the scenarios which might have led to the loss. The Annex 13 definition does not limit the term ‘accident’ to any specific causal factor, stating only that the occurrence must have taken place between boarding and disembarkation of passengers or crew.
This distinction notably meant that the fire on an empty parked Ethiopian Airlines Boeing 787 at London Heathrow in July 2013 fell outside of the definition of an accident or serious incident, and UK investigators had to specially categorise the event in order to invoke the normal protocols.
Investigators have yet to determine whether – outside of the Annex 13 definition – the loss of MH370 was accidental, in the conventional sense of the term, or the result of possible deliberate intervention.
Authorities are still pursuing both a safety inquiry and a criminal probe into the aircraft’s disappearance. But the government says that both investigations are being “limited” by the lack of physical evidence, and the inability to locate the crash site and the flight recorders, and none of the possible causes behind MH370’s loss can be substantiated.
Malaysia’s government believes, however, that the formal ‘accident’ declaration – while not resolving the crucial questions over the cause of the loss – will assist with compensation efforts. The airline says it will “proceed with the compensation process” following the decision. |
Keanu Reeves will return to New York Comic Con next month to promote his new film Replicas, where the first footage will be shown from this impending sci-fi thriller. As of now, a release date for Replicas has yet to be announced, but it seems possible that may be revealed during the panel. Here's the official description of the NYCCC presentation, including who will be joining Keanu Reeves at the Javits Center.
"Join Keanu Reeves and the team behind Replicas, for an exclusive first look and conversation about the film. Reeves developed and produced the Replicas with his producing partner, Stephen Hamel, and Transformers franchise producer, Lorenzo di Bonaventura. The film is written by Chad St. John (London Has Fallen) from a story by Hamel, and directed by Jeffrey Nachmanoff (writer of The Day After Tomorrow). Replicas is the story of a scientist (Reeves) who loses his family in a horrific accident, but is determined save his wife and children by bringing them back to life with cutting-edge cloning technology."
The Hollywood Reporter reveals that the panel presentation will take place on the first day of NYCC, Thursday, October 5, with the panel set to take place from 6:30 PM to 7:30 PM in room 1A06 at the Javits Center. We first reported on this sci-fi thriller Replicas back in October 2014, when Keanu Reeves signed on to the project for Lotus Entertainment, producer Lorenzo di Bonaventura and the director at the time, Tanya Wexler. The film is now directed by Jeffrey Nachmanoff (Traitor).
Since the first footage from Replicas will debut at NYCC, it seems unlikely that we'll see anything from this sci-fi thriller between now and then, except possibly a new poster. Keanu Reeves is joined by a supporting cast that includes Thomas Middleditch, Alice Eve, John Ortiz, Emily Alyn Lind, Emjay Anthony, Nyasha Hatendi and Amber Rivera. Jeffrey Nachmanoff is making his second directorial effort with Replicas, following 2008's Traitor, although he has been keeping busy on the small screen, serving as a writer and producer for Hostages, Legends and Chicago Fire.
Keanu Reeves is coming off his hit action sequel John Wick Chapter 2, which he promoted at New York Comic-Con last fall. He will next be seen in To the Bone, and he has a number of projects in various stages of development, such as John Wick Chapter 3, the long-awaited Bill and Ted 3, alongside Alex Winter, SPF-18, Desination Wedding, Rally Car and The Starling. While we wait for more on Replicas, take a look at the first photo below. |
Crystallization of glycerol dehydrogenase from Bacillus stearothermophilus. The NAD(+)-linked glycerol dehydrogenase from Bacillus stearothermophilus is a member of the so-called 'iron- containing' class of polyol dehydrogenases. This enzyme has been crystallized in three different forms in the presence of a range of divalent cations and glycerol or NAD+ using the hanging-drop method of vapour diffusion with ammonium sulfate as the precipitant. X-ray photographs have established that the crystals grown in the presence of zinc and glycerol (form A) most likely belong to space group I422 with cell parameters a = b = 102 and c = 728 A. The crystals grown with zlnc and NAD(+) (form B) belong to the tetragonal system and probably belong to the space group P422 with cell parameters a = b = 150 and c = 220 A. The crystals grown with lead and glycerol (form C) belong to a primitive orthorhombic system with cell parameters a = 127, b = 178 and c = 173 A. Experiments using the synchrotron radiation source at the DRAL Daresbury laboratory have shown all three crystal types diffract to at least 3 A resolution. Elucidation of the three-dimensional structure of this enzyme will provide a structural framework for this class of polyol dehydrogenases, which are not represented in the database at present, and enable comparisons to be made with enzymes belonging to the other classes. |
def formatTime(self, record, datefmt=None):
if not datefmt:
datefmt = LoggingFormatter.DEFAULT_DATE_FORMAT
record_time = LoggingFormatter.TIMEZONE.localize(self.converter(record.created))
return "".join([
record_time.strftime(datefmt),
".{:03.0f}".format(record.msecs),
"Z",
]) |
Machine learning method for state preparation and gate synthesis on photonic quantum computers We show how techniques from machine learning and optimization can be used to find circuits of photonic quantum computers that perform a desired transformation between input and output states. In the simplest case of a single input state, our method discovers circuits for preparing a desired quantum state. In the more general case of several input and output relations, our method obtains circuits that reproduce the action of a target unitary transformation. We use a continuous-variable quantum neural network as the circuit architecture. The network is composed of several layers of optical gates with variable parameters that are optimized by applying automatic differentiation using the TensorFlow backend of the Strawberry Fields photonic quantum computer simulator. We demonstrate the power and versatility of our methods by learning how to use short-depth circuits to synthesize single photons, Gottesman-Kitaev-Preskill states, NOON states, cubic phase gates, random unitaries, cross-Kerr interactions, as well as several other states and gates. We routinely obtain high fidelities above 99\% using short-depth circuits, typically consisting of a few hundred gates. The circuits are obtained automatically by simply specifying the target state or gate and running the optimization algorithm. It is natural to ask whether we can employ methods from machine learning to aid in the design and realization of quantum algorithms. For instance, many quantum algorithms employ subroutines that require the preparation of resource states or demand a compact decomposition of specific transformations into gates from a universal set. For state preparation, several techniques have been proposed for specific applications [35,. Providing methods to automate and optimize the construction of these subroutines would constitute a valuable and far-reaching tool for quantum computation. This is particularly important for gate synthesis because many methods rely on product-rule approximations that lead to decompositions involving a large overhead in the total number of gates. In this work, we outline how techniques from machine * Electronic address: juanmiguel@xanadu.ai learning and optimization can be employed to find quantum circuits that perform a desired transformation between input and output states. In the simplest case of a single input and output, this corresponds to state preparation: finding a circuit to create a target quantum state. In its generalized form of several inputs and outputs, this is equivalent to gate synthesis: the task of obtaining a circuit that reproduces the action of a target unitary transformation. We focus on the continuous-variable (CV) model of quantum computation, which is a leading platform for optical quantum computing, noting that our results can in principle extended to other models of quantum computing. As an ansatz for the circuit architecture we employ the CV quantum neural network introduced in Ref.. We consider networks with a limited number of layers that perform state preparation and gate synthesis using circuits with significantly fewer gates than standard decomposition techniques. To optimize these quantum neural networks, we simulate the corresponding circuits using the Strawberry Fields software platform for photonic quantum computation. Strawberry Fields is equipped with a TensorFlow backend which is capable of automatically computing gradients with respect to circuit parameters. These can be used to optimize the networks using TensorFlow's built-in gradient descent optimizers. We routinely obtain fidelities above 99% using short-depth circuits consisting of roughly one hundred gates. All results are obtained automatically by just specifying the target state or gate and running the optimization algorithm, providing a significant simplification of the overall algorithm development process. 1 In the following, we discuss our approach for learn-ing state preparation and gate synthesis using the CV neural network architecture. This technique is applied to find circuits that can prepare several single and twomode quantum states. We then employ our results to find circuits capable of synthesizing various single and two-mode gates. High fidelities are observed in all cases studied, providing evidence for the wide-ranging applicability of this approach. II. AUTOMATED CIRCUIT DESIGN The problems considered in this work fall under the same general scope: given a quantum information task, find the circuit that best achieves that task. For state preparation, the goal is to prepare a particular target state starting from a fixed reference state. For gate synthesis, the task is to provide the decomposition of a desired unitary transformation into a sequence of elementary gates. Our strategy to attack this problem is to use a variational quantum circuit approach. A variational quantum circuit is a circuit whose gates and connectivity are fixed by an ansatz, but where some or all of the gates contain free parameters. Through varying these free parameters, we can change the unitary enacted by the circuit. The two tasks listed above can be tackled with this strategy provided that (i) the variational circuit is expressive enough, and (ii) we have a well-performing method for finding good circuit parameters. To address both of these needs, we will leverage methods and ideas from classical and quantum machine learning. In order to provide the most representational power, we would like our variational circuit to be as general and flexible as possible. To this end, we will employ the CV neural network architecture from Ref.. The CV quantum neural network consists of multiple layers L composed of the sequence of gates: where are non-Gaussian gates acting independently on each mode. The displacement and squeezing gates are defined as D() = exp(a − * a) and, where a and a are respectively the annihilation and creation operators of the mode. The linear optical interferometers are made up of single-mode rotation gates R() = exp(in) and two-mode beamsplitters BS(, ) = exp, wher n = a a is the number operator. A single layer of a quantum neural network is shown in Fig. 1. Note that this network architecture is capable of simulating any universal CV quantum circuit with at most polynomial overhead, since the gates in every layer constitute a universal set. The displacement, squeezing, rotation, beamsplitter, and non-Gaussian gates in a single layer all contain free parameters which determine the strength of transformation carried out by the gate. Collectively, we denote these parameters by. The goal is to find the choice of parameters which optimizes some cost function C( ). In order to perform this optimization, we employ the family of gradient descent algorithms that are widely used in the field of deep learning. In vanilla gradient descent, we start off with randomly initialized values for the parameters. We compute the gradient ∇ C of the cost function with respect to the parameters, which determines the direction of steepest descent. We then update the parameters based on the rule where is some user-specified step size (also known as a learning rate). This process is iterated until the cost function no longer improves. The parameter values corresponding to the lowest-observed cost function then determine the proposed solution circuit for the given task, which may or may not be a global optimum. For optimization, variants of gradient descent, such as stochastic gradient descent, momentum, or Adam introduce noise, adaptive step-size, and memory effects into this process, yet they all follow the basic principle of following the gradient. Algorithms based on gradient descent have become so important that numerous libraries now provide the ability to automatically compute gradients [53,. We encode the variational circuits using the Strawberry Fields software platform and make extensive use of its TensorFlow backend, which can automatically compute the gradients of gate parameters and perform the desired optimizations. In all cases studied in this paper, we use the Adam optimizer. In the following, we fix the non-Gaussian element of each layer to be the Kerr gate K = exp(in 2 ), wheren is the number operator. We choose the Kerr gate because it is diagonal in the Fock basis, a feature that leads to faster and more reliable numerical simulations. In the simulations, each mode is truncated to a subspace of fixed cutoff dimension, i.e., a state | is represented in simulation by D |, with H the projector onto the D-dimensional truncated space. To prevent any initial, final, or intermediate state of the circuit having significant support outside of the space, we set the cutoff dimension to be suitably large to fully contain the state at all stages of the simulation, see Appendix A for more details. For simulations and experimental implementations, it is important to be aware of the magnitude of parameters in active gates that can change the photon number, namely the displacement, squeezing, and Kerr gates. It may be desirable to fix upper bounds on these parameters due to the simulation or hardware constraints. Tables I and II provide a summary of the various hyperparameters and results for each of the examples that follow in this paper, including in particular the largest parameters required for displacement, squeezing, and Kerr gates. III. STATE PREPARATION The goal is to find a quantum circuit that, for a given canonical input state | 0 and a target output state | t, performs a unitary transformation U satisfying In other words, the circuit U prepares the state | t from the input | 0. Eq. fixes a single column of the unitary U in a basis containing the input state | 0, while the remaining components of U are free parameters. For simplicity, we henceforth fix the input state to be the vacuum, i.e., | 0 = |0. In principle, it is possible to solve the state preparation problem by fixing the remaining free parameters of U and finding an approximate decomposition in terms of a universal gate set. This approach has several drawbacks: it is not clear how to optimally choose the free parameters, finding decompositions can be computationally expensive, and the resulting circuits usually involve a very large number of gates from the universal set. These drawbacks are even more pronounced for CV quantum computers where finding decompositions is significantly more involved than in other models. Instead, our approach is inspired by strategies employed in machine learning. To prepare a given target state, we first fix the architecture by selecting the number of layers (depth) of the quantum neural network. Optimization is performed by minimizing the cost function which captures the goal of finding parameters such that In the following, we showcase the effectiveness and versatility of this approach by selecting several canonical single and two-mode states and employing our techniques to find quantum circuits that prepare them. Our results demonstrate that the search for these circuits can be largely automated and the resulting circuits have short depth while still preparing the states with very high fidelity. Single photon state As a first example, we consider the task of preparing a single photon. We select a single-mode quantum neural network consisting of 8 layers, for a total of 40 gates from a universal set. For a single mode, a linear optical interferometer reduces to a rotation gate R() = e in. In Fig. 2, we visualize the optimization process by displaying the Wigner function of the output state of the network at different stages during the optimization of the circuit. Initially, due to the random initialization of the circuit parameters, the network prepares a random state that is close to the vacuum. After only a few steps, the network learns to include negativity in the Wigner function. As the optimization continues, the network carves an output state that increasingly resembles an ideal single photon. The result of optimization is illustrated in Fig. 3, where we plot the Wigner functions of an ideal single photon and of the state prepared by the circuit. After 5000 steps of the gradient descent algorithm, a circuit is found that can prepare a state with 99.998% fidelity to a perfect single photon. The Adam optimization algorithm is a stochastic gradient descent algorithm. Together with the random initialization of the gate parameters in the network, this leads to a non-deterministic output of the network. Although the optimization converges to low values of the cost function for a sufficiently large number of steps, for a fixed number of steps the values will differ across different independent runs, as shown in Fig. 4. Consequently, it is often desirable to perform many independent optimization sessions and select the best output among them. FIG. 5: Value of the cost function after 1000 steps of optimization for quantum neural networks with a different number of layers. Each value is an average over ten independent runs of the circuit optimization for preparing a single photon. Finally, we remark that the depth of the quantum neural network plays an important role in the performance of state preparation. Complex quantum states require large circuits to prepare them and therefore a correspondingly large number of layers in the network. However, there is a price to pay for adding layers: it increases the number of parameters to optimize as well as the resources required to simulate the resulting circuits, leading to longer optimization times. It is therefore preferable to find an adequate number of layers such that sufficiently high fidelities can be reached while minimizing the computational resources required for optimization. This is shown in Fig. 5, where we find that the single photon state can be well approximated using only a few layers. As demonstrated also in subsequent examples for both state preparation and gate synthesis, it is possible to find circuits of remarkably short depth that can still achieve high fidelities. ON state In the measurement-based model of CV quantum computing, quantum gates are applied via gate teleportation: a technique where measuring a resource state in a neighbouring mode enables the application of a corresponding gate on a target mode. In Ref., it was shown that superpositions of vacuum and Fock states of the form where |0 is the vacuum, |N is an N -photon Fock state, and a is a complex number, can be employed via gate teleportation to apply the gate exp(ix N ) to first order in. These states are known as ON states and we select the N = 9 ON state as the target for state preparation, setting a = 1 such that the state is an equal superposition of the vacuum and a nine-photon Fock state. We fix a network of 20 layers (100 gates) and optimize for 5000 steps, using a cutoff dimension of 14. The result is a circuit that can prepare a state with 99.93% fidelity to the ideal ON state as shown in Fig. 6. GKP state Gottesman-Kitaev-Preskill (GKP) states are important resource states that can be used for error correction in CV quantum computing. Here, we focus on Hex GKP states, as defined in Ref., which are better suited than the original GKP states for correcting errors due to loss. In their idealized form, Hex GKP states are given by where d is the dimension of a code space, = 0, 1,..., d− 1, and |0 is the vacuum. In the case of finite energy, the states are modulated by a Gaussian envelope exp(−∆ 2n ) |. In Strawberry Fields, it is convenient to specify states in terms of their components in the Fock basis. In the case of the GKP states, these can be computed by numerically evaluating the inner products |n for all Fock states |n in the Hilbert space defined by the cutoff dimension in the simulation. We choose a Hex GKP state with = 1, and ∆ = 0.3 as the target for state preparation. This state is significantly more complex than our previous examples, so we select a network with 25 layers (125 gates), a cutoff dimension of 51 for the simulation, and optimize for 10,000 steps. The result is illustrated in Fig. 7, where a circuit was found that can prepare a state with 99.60% fidelity to the target GKP state. 4. Random state All the states studied thus far have significant symmetry. To demonstrate that our method is versatile enough to prepare unstructured states, we now focus on a random state of the form (a n + ib n ) |n, where the values a n and b n where drawn from a standard normal distribution and N = d−1 n=0 |(a n + ib n )| 2 is a normalization constant. We fix a value of d = 15 and select a network of 25 layers (125 gates), with a cutoff dimension of 20 in the simulation. The optimization is carried out for 5000 steps resulting in a prepared state with fidelity 99.82% with respect to the target random state. This is shown in Fig. 8. NOON state As a final example, we extend the state preparation method to two-mode states. Computationally, optimization is significantly more challenging because the Hilbert space dimension in the simulation is quadratically larger than in the single-mode case. As the target state we select a NOON state, defined as where |0N is a state of vacuum in the first mode and N photons in the second mode, with an analogous definition for the state |N 0. NOON states play an important role in quantum metrology as they are known to be optimal resource states that saturate the Heisenberg limit of precision for phase estimation. We set the NOON state with N = 5 as the target state, fixing a network of 20 layers (100 gates) with a cutoff dimension of 10. The network prepares a state with 99.89% fidelity to the ideal target state. This is shown in Fig. 9, where we plot the two-dimensional wavefunction NOON (x, y) of the target and prepared states. Note that we plot the wavefunction and not the Wigner function since the latter is a function of four variables in the twomode case. All state preparation results are summarized in Table I. A straightforward generalization of state preparation is gate synthesis, where we consider the action of the circuit not just on a fixed input, but on a complete orthonormal basis of a given Hilbert space. In the following section, we describe how our methods can be extended to the gate synthesis problem. IV. GATE SYNTHESIS In the context of photonic quantum computing, a gate is a quantum transformation operating either on the full infinite-dimensional Hilbert space or on a restricted subspace of a set of modes. Gates are most often of unitary form, which is the setting we consider in this work. One approach to synthesize a target unitary gate V t is to decompose it into a fixed set of elementary gates. The set of gates in the elementary set can vary, and there exists multiple decomposition methods for each gate set. However, there are several drawbacks to traditional methods for performing gate decomposition, including computational overhead, a large number of gates from the elementary set, and errors arising due to Trotterization and commutator approximations. As with state preparation, we approximate V t using a CV quantum neural network whose parameters are optimized to replicate the action of the target gate. This process allows for a realization of the target unitary V t that is both deterministic and of fixed depth, providing the user with control over the number of elementary gates used. The strategy is as follows. Any given unitary can be equivalently described by a set of inputoutput relations between basis states: given a set of orthogonal input states {| We fix the input states to be the first d states in the Fock basis of each mode, i.e., | (i) 0 = |i where |i is the Fock state of i photons. For unitaries acting on the infinite-dimensional multimode space, this represents a restriction on the countably infinite number of relations. This description of the unitary captures its action only on a subspace of restricted photon number. Energy constraints in any physical implementation of a CV quantum computer mean that an effective restriction on photon number is already introduced, and the user can fix d to match this limitation. To optimize the unitary transformation U ( ) performed by the quantum neural network, we opt for the cost function By comparing to the cost function in Eq., we see that gate synthesis can be considered as a generalization of state preparation to more than one input-output relation. The following section provides example applications of gate synthesis to several single and two-mode gates. These results demonstrate how relatively short-depth approximations of a unitary can be constructed using a process that is largely automated. We measure the performance of gate synthesis by numerically calculating the average fidelity between the target unitary V t and the circuit unitary U ( ) when applied over all states with support in the input d-dimensional Fock subspace; see Appendix B for more details. Cubic phase gate The cubic phase gate is a single mode non-Gaussian unitary that, in combination with Gaussian gates, forms a universal set for CV quantum computing. It is defined as withx the position operator and > 0 a fixed gate parameter. As discussed previously, we synthesize a gate that replicates the action of the cubic phase gate on a subspace of the infinite-dimensional Hilbert space. We set this subspace to be the 10-dimensional subspace of states with at most nine photons and fix a gate parameter of = 0.01. We select a network consisting of 25 layers, i.e., 125 gates, and perform the optimization for 4000 steps. The cubic phase gate can increase photon number and therefore in general it maps states in the subspace of at most d − 1 photons to states that may have more than d − 1 photons. This transformation can be represented in terms of a matrix with d columns where column i represents the result of applying the gate to the i-th Fock state and the columns have dimension d > d. The result of optimization is illustrated in Fig. 10. Here, we visualize the real and imaginary parts of the transformation matrices for both the ideal cubic phase gate and the unitary U ( ) applied by the circuit. The synthesized gate has an average fidelity of 99.86% with respect to the ideal cubic phase gate. To visualize these transformations, we also highlight the result of applying both the ideal and synthesized gate to the equal superposition state in the d-dimensional subspace given by with |i the i-th Fock state. In this case, we apply the ideal and synthesized gates to the state | 10 and plot the Wigner functions of the resultant states in Fig. 10. Similarly to the state preparation setting, the result of gate synthesis is non-deterministic due to random initialization of gate parameters and the use of stochastic gradient descent. In Fig. 11, we plot the progress in minimizing the cost function for 10 independent runs of gate synthesis. We study both the case of a 6-dimensional and a 10-dimensional subspace. The result of different optimization runs varies greatly, with many of them becoming stuck in local minima that are far from optimal. This behavior can be understood in terms of the subspace dimension: increasing the number of relations that define the transformation makes the optimization landscape more complex and adds computational overhead. In particular, it can be seen in Fig. 11 that for d = 6 input-output relations, a smaller proportion of runs become stuck in local minima that are far from the global optimum. Quantum Fourier transform We now consider a unitary transformation acting on a finite-dimensional system embedded into the first d Fock states of a single mode. This transformation has the effect of mapping input Fock states into equal superpositions of all Fock states, thus performing a transformation between two mutually-unbiased bases. We denote this gate as the quantum Fourier transform (QFT) in relation to the mathematically equivalent transformation employed in discrete systems. The gate is defined as This is a highly complex gate and hence we allow for a deeper architecture and more optimization steps. We fix d = 8 and carry out gate synthesis with 40 layers (200 gates) for 8000 steps, resulting in an average gate fidelity of 98.89% between the ideal gate and the transformation performed by the network. We plot visualizations of both unitaries in Fig. 12 as well as the result of applying them to the equal superposition state | 8. Note that in this case V QFT | 8 = |0. Random unitary As in the case of state preparation, we now study the suitability of our gate synthesis method for unstructured transformations. This complements our investigation of random state preparation by adding multiple relations. For this task, we generate a random unitary V according to the Haar measure that acts only on the five-dimensional space of at most four photons. Gate synthesis was performed with 25 layers (125 gates) for 1000 steps, resulting in an average fidelity of 99.5%. Along with the previous QFT gate, this shows the viability of our gate synthesis method for complex transformations. Figure 13 visualizes the target and learned unitaries, along with the Wigner functions resulting from applying these unitaries to the d = 5 superposition state | 5. Cross-Kerr interaction We now extend our investigation of gate synthesis to two-mode unitaries. We focus on the cross-Kerr interaction, which mediates coupling between photons in different modes by applying a phase that depends on the photon number in each mode. It can be written as withn k the number operator on mode k and the interaction strength. The cross-Kerr is a widely used nonlinear bosonic interaction, appearing in the context of superconducting circuits and quantum photonics. It has been shown to allow the implementation of a nearlydeterministic qubit CNOT gate with vastly reduced resources compared to other approaches, and leads to a maximally efficient implementation of the non-linear sign gate on photonic qubits. The cross-Kerr interaction is also vital in state preparation, for instance in the generation of arbitrary-strength Schrdinger cat states, and represents the nearest-neighbor or dipole interaction in the Bose-Hubbard model. We synthesize the cross-Kerr interaction using 25 layers (125 gates) and 10000 optimization steps, with = 0. 1. By restricting to the first d = 5 Fock states in each mode, our architecture can approximate the cross-Kerr interaction with an average fidelity to the ideal unitary of 99. 994%. The result of cross-Kerr gate synthesis is visualized in Fig. 14. The cross-Kerr optimization resulted in a circuit with negligible levels of displacement and squeezing, confirming the intuition that the use of Kerr gates and beamsplitters is sufficient in this case. We test the action of both ideal and learnt unitaries by applying them to the equal superposition two-mode state, which is written as To visualize the resultant states, we plot the twodimensional wavefunctions instead of the Wigner functions, similarly to two-mode state preparation. Extending to the two-mode setting increases the computational overhead of gate synthesis. Indeed, as in state preparation, the truncated Hilbert space of the composite system is quadratically larger. However, an additional overhead in gate synthesis is that the number of relations that define the transformation also increases for two modes, e.g., to 25 for d = 5. Nevertheless, our results demonstrate synthesis of high fidelity approximations of a cross-Kerr gate with parameter = 0.1. Historically, the interaction strength for the cross-Kerr gate that is realizable with available technology has been too small for use in quantum computing. Recent results have considered decompositions of the cross-Kerr into cubic phase gates, controlled-phase gates, and beamsplitters, requiring approximately 1000 elementary operations for a decomposition precision of ∼ 0.1. Our approach uncovers a short-depth decomposition, requiring only 25 Kerr gates and 125 elementary operations in total. A summary of the gate synthesis results is reported in Table II. V. CONCLUSION We have presented a general method to leverage techniques from machine learning and optimization to find quantum circuits that are capable of reproducing desired transformations between input and output states. Our results make it possible to largely automate the task of discovering circuits that perform specific subroutines of quantum algorithms. Crucially, we are capable of synthesizing high-fidelity states and gates using short-depth circuits -a feature that makes our techniques particularly well suited for near-term quantum devices. The strategies employed here -namely stochastic gradient descent based on automatic differentiation of simulated quantum circuits -can be straightforwardly applied to other forms of quantum computation. However, despite the usefulness of automatic differentiation for quantum computing and quantum simulation, to our knowledge, Strawberry Fields is currently the only quantum software library which natively supports automatic differentiation. Further work is required to bring this feature to other simulation libraries. Finally, it is important to extend these methods to more general quantum algorithms involving complex transformations between several modes. The techniques outlined in this work require the ability to classically simulate circuits, a task that becomes intractable as the number of modes increases. Achieving this extension will likely require the use of specialized quantum techniques to optimize the circuits directly. The average fidelity of two quantum unitary operations U and V is defined by where the integral is performed over the Haar measure on the state space. To calculate the average fidelity, we employ another common fidelity measure known as the process fidelity. The process fidelity is calculated by first applying the N -mode unitary V defined on the d-dimensional Fock subspace to one half of a maximally entangled state |, This is repeated for the learnt unitary U ( ), and the process fidelity determined by taking the corresponding state overlap: The process fidelity is advantageous, as it is bounded by the average fidelity of only two complementary sets of input states, avoiding the need to sample over the entire state space. Furthermore, the process fidelity is related directly to the average fidelity via the relationship It should be noted that a slight subtlety arises in the case of computing the process fidelity for the cubic phase gate. While U CP ( ) acts on a d-dimensional subspace, it has the potential to map states within this subspace into the larger D-dimensional subspace given by the Fock basis cutoff dimension. As a result, to numerically approximate the average gate fidelity in this case, we compute the quantit |
/*
Serves as a register for HLS
*/
uint16_t reg(uint16_t in)
{
#pragma HLS PIPELINE II=1
#pragma HLS INTERFACE ap_ctrl_none register port=return
#pragma HLS INLINE off
return in;
} |
Why assemble your own ethernet cables? Many online stores sell them for only a couple of dollars each. But certain situations call for using your own custom-wired cables. Maybe you need enough of them to make DIY cables cost-effective; maybe you have unique length requirements; maybe you need to replace broken plugs, or maybe you just want to use up excess cable that you have on hand and would otherwise waste.
I'll identify the parts and tools that you'll need, and then I'll explain how to assemble each cable. With the right equipment, you can crank out customized cables in seconds.
Let's start with the cables. For gigabit network cabling, select Category 5e (Cat 5e) or better. Cat 6 cables support up to 10-gigabit networks and are fully backward-compatible, but most home users don't have any 10-gigabit to support.
You'll also need to choose between shielded twisted-pair (STP) and unshielded twisted-pair (UTP) cabling. Either type should work just fine, though STP might be better if you're running cables over long distances and with lots of potential for electrical interference. Finally, decide between solid-core and stranded wires. I opted for solid-core, since I had a lot of that type left over from my home ethernet wiring project.
You'll be attaching ethernet plugs to each end of each cable, along with boots slightly behind them to protect the plastic tabs. Buy plugs that match your cable choice--solid-core or stranded--and enough boots to complement each plug. I bought an assortment of colors so that I could keep track of my network wiring more easily.
You'll need a wire cutter, wire stripper, or pair of scissors, and an RJ45 crimper. You may be able to borrow these tools from a friend or IT department at your work, or you can buy them online. I purchased everything I needed from Monoprice.com.
To verify that the wiring is correct, you'll also want a tester; they retail for $25 or more. Alternatively, you can make your own, as I did. I wired an ethernet keystone jack to a 9-volt battery, a 470-ohm resistor (in series), and four red LEDs (in parallel) so that each pair of wires is associated with its own LED, looping through those parts. I then wired a separate jack in a loopback configuration, so that pairs of wire complete the circuit on the opposite end, bridging 1 and 2, 3 and 4, 5 and 6, and 7 and 8. If the cable that I plug between the two jacks is good, the cable will bridge each circuit, lighting one LED for each completed (and properly functioning) pair.
Slide a boot onto the end of the cable, leaving the large boot opening toward the bare end of the cable. Strip about 1 inch of the cable jacket away. Notch down at the end of the jacket, and tear another inch away, using your fingernails or the string inside the cable if available. Trim this jacket off.
This process ensures that you'll have an exposed and unnicked section of cable to work with; when making the first pass at stripping off the jacket, you may have scored or slightly cut the wires inside.
Untwist and straighten the pairs of wires. I like to hold the bundle in one hand and then tug my thumb and finger across the rest. Another approach is to hold both ends of the exposed wire and gently draw it across a curved table-edge. In any event, treat it well, because needless wrangling could damage the wire.
Put the eight wires in order as you go. The particular order you use doesn't actually matter as long as you stick to it at each end. Still, I follow the T568B standard, which calls for (left to right) white/orange, orange, white/green, blue, white/blue, green, white/brown, brown.
Trim the wires back again, leaving about ¾ inch exposed. Position the ethernet plug with the flat side up and with the opening for the wires facing you. Slide the wires as far into the ethernet plug as possible. You might need to push with moderate force. You'll see them reach the far end, following their assigned tracks.
Put the plug into your crimping tool, and crimp it all into place. The copper pieces will slice down, into the wires, and the crimp will push the plug together in two places. If you were successful, you'll see that part of the cable jacket is present within the first crimp. If not, you may have exposed too much of the ethernet wires. Or the exposed wires may have been too short to reach the far end of the plug.
Repeat the process as needed. Then plug everything together to build the ultimate home network. |
Mutual Visibility by Fat Robots with Slim Omnidirectional Camera In the existing literature of the Mutual Visibility problem for autonomous robot swarms, the adopted visibility models have some idealistic assumptions that are not consistent with practical sensing device implementations. This paper investigates the problem in the more realistic visibility model called opaque fat robots with slim omnidirectional camera. The robots are modeled as unit disks, each having an omnidirectional camera represented as a disk of smaller size. We assume that the robots have compasses that allow agreement in the direction and orientation of both axes of their local coordinate systems. The robots are equipped with visible lights which serve as a medium of communication and also as a form of memory. We present a distributed algorithm for the Mutual Visibility problem which is provably correct in the semi-synchronous setting. Our algorithm also provides a solution for Leader Election which we use as a subroutine in our main algorithm. Although Leader Election is trivial with two axis agreement in the full visibility model, it is challenging in our case and is of independent interest. Motivation Robot swarms are distributed multi-robot systems consisting of simple and inexpensive robots that can collaboratively execute complex tasks. Such systems offer several advantages over traditional single robot systems, such as scalability, robustness and versatility. Employing robot swarms is particularly tempting in risky and hazardous scenarios, such as disaster management, military operations, etc. Coordination of autonomous robot swarms has been the object of study in a number of fields, including robotics, artificial intelligence, control theory and distributed computing. Within distributed computing, in particular, there has been a series of studies on the algorithmic aspects of distributed coordination of robot swarms (see for a comprehensive survey). In the traditional framework of theoretical studies, robot swarms are modeled as systems of autonomous (there is no centralized control), anonymous (no unique identifiers that can be used in computation), identical (indistinguishable by physical appearance) and homogeneous (all of them execute the same algorithm) computational entities that can freely move on the plane. The robots do not have access to any global coordinate system. They each have their own local coordinate system. Each robot is equipped with sensors that allow it to perceive its surroundings. The robots operate in Look-Compute-Move (LCM) cycles, i.e., when a robot becomes active, it takes a snapshot of its surroundings (Look), computes a destination point based on the snapshot (Compute) and moves towards the computed destination (Move). There are three types of schedulers considered in the literature that describe the timing of operations of the robots. In the fully synchronous model (FSYN C), time is logically divided into global rounds and all the robots are activated in each round. The robots take their snapshots simultaneously and then execute their moves concurrently. The semi-synchronous model (SSYN C) is the same as FSYN C except for the fact that not all robots are necessarily activated in each round. The most general model is the asynchronous model (ASYN C), where there are no assumptions except that all robots are activated infinitely often. The standard movement models are rigid and non-rigid. In the rigid model, a robot can move towards its computed destination accurately in one step. On the other hand, the nonrigid model assumes that a robot may stop before it reaches its destination. However, there is a fixed but unknown > 0 so that each robot traverses at least the distance unless its destination is closer than. In the full visibility model, it is assumed that each robot can see all the other robots in the swarm. However, limitations in sensing capabilities may not allow the robots to obtain a complete view of the configuration. For example, if the robots are equipped with cameras as sensing devices, then the visibility of a robot can be obstructed by the presence of other robots. A simple model that captures this scenario is the opaque point robot model. In this model, the robots are assumed to be dimensionless points in the plane and two robots are visible to each other if and only if no other robot lies on the line segment joining them. A more realistic model is the opaque fat robot model, where the robots are seen as disks. In this model, two robots are visible to each other if and only if there exists an unobstructed line between two points on the surface of the robots. Although this model addresses the impracticality of the physical aspect of the previous point robot model, the visibility assumptions are still impractical. In order to implement this model in practice, the entire surface of a robot has to be covered with cameras, which is expensive and impractical. A more economical way of obtaining an omnidirectional view is to have a circular arrangement of fewer number of cameras around the center of the robot. This can be modeled as having a single camera represented as a disk whose diameter is smaller than the diameter of the robot. We say that a robot is visible to another robot if and only if there is an unobstructed line from a point on the surface of the former to the camera of the latter. This model was introduced by Honorat et al. in. The region obstructed by a single robot in this model has the shape of a truncated infinite cone instead of a line or a strip in the case of opaque point robots and traditional opaque fat robots models respectively (see Fig. 1). Some implications of this model which show a stark difference from the previous models are mentioned in the following. A robot cannot always ascertain from its view whether or not it is on the convex hull of the configuration (see Fig. 2a). A robot cannot always ascertain from its view whether or not it is on a collinear configuration, i.e., all the robots are on the same line (see Fig. 2b and Fig. 2c). The visibility relation is not symmetric, i.e., r 1 being visible to r 2 does not imply that r 2 is also visible to r 1 (see Fig. 2d). The fundamental problem in the obstructed visibility scenario is the MUTUAL VISIBILITY problem, where the robots are required to reach a configuration in which all robots can see each other. Although the problem has been extensively studied in the opaque point robot model and also in the traditional fat robot model, it is yet to be studied for opaque fat robots with slim omnidirectional camera. In fact, to the best of our knowledge, the only work which considered robots with slim omnidirectional camera is that of Honorat et al., where the gathering problem for four robots was studied. Our Contribution In this paper, we initiate the study of the MUTUAL VISIBILITY problem for opaque fat robots with slim omnidirectional camera. In particular, each robot is modeled as a disk of unit radius and its camera is also a disk having the same center but a smaller radius. We consider the luminous robots model (LUMI) in which each robot is equipped with a visible light that can assume a constant number of predefined colors. The lights serve as a medium of communication and also as a form of memory. We assume that Figure 1: The region invisible to r 1 due to the obstruction by r 2. a) Opaque point robots. b) The traditional model of opaque fat robots. c) Fat robots with slim omnidirectional camera. Figure 2: a) The robot r 1 'thinks' that it is on the convex hull as it lies on the convex hull of the robots visible to it, but it is actually an interior robot. b)-c) The robot r cannot distinguish between a collinear and a non-collinear configuration. d) The robot r 1 is visible to r 2, but r 2 is not visible to r 1. the robots have two axis agreement, i.e., all robots agree on the direction and orientation of both X and Y axes of their local coordinate systems. The total number of robots in the swarm is not known beforehand. However, an upper bound on the width of the initial configuration is known in advance. In this setting, we have presented a distributed algorithm for the MUTUAL VISIBILITY problem using 7 colors. We have proved the correctness of our algorithm in the semi-synchronous (SSYN C) setting. Our algorithm also provides a solution for the LEADER ELECTION problem, which we use as a subroutine in our main algorithm. Although LEADER ELECTION is trivial with two axis agreement in the full visibility model, it is challenging in our case and is of independent interest. We have provided extensive simulation studies assessing our algorithm with respect to different performance metrics. To set up the simulation environment, we had to solve the problem of determining whether a robot is visible to another in a configuration of robots with slim omnidirectional camera. The simulation framework can be useful for conducting experiments for future works in this model. Related Works The study of the MUTUAL VISIBILITY problem was initiated by Di Luna et al. for oblivious robots in SSYN C for the opaque point robot model. They solved the problem by forming a convex n-gon, where n is the total number of robots in the swarm. However, they assumed that n is known beforehand. Later, Sharma et al. analyzed and improved the round complexity of the algorithm in FSYN C. With the assumption that the total number of robots is not known in advance, the problem was first studied by Di Luna et al. in the luminous robots (LUMI) model. In the rigid movement model, they solved the problem (a) with 2 colors in SSYN C, and (b) with 3 colors in ASYN C. In the nonrigid movement model, they solved the problem (a) with 3 colors in SSYN C and (b) with 3 colors in ASYN C under one axis agreement. Sharma et al. later improved the algorithms in terms of the number of colors required. Then, a series of papers appeared, aiming towards reducing the time complexity of the algorithm. Bhagat et al. first solved the problem in ASYN C without any agreement on the coordinate axes. The problem was studied for robots with finite persistent memory and no communication capability in. The problem was also considered for faulty robots and robots operating on a grid-based terrain. All the papers mentioned till now have considered the opaque point robot model. In the traditional opaque fat robot model, the problem was studied in. In, Sharma et al. proposed an algorithm that solved the problem in FSYN C using 9 colors. Then, in, Sharma et al. proposed an algorithm that solves the problem in SSYN C. However, they assumed that the number of robots n is known beforehand and no two robots visible to each other in the initial configuration are more than n units apart. Agathangelou et al. studied the gathering problem in the traditional opaque fat robot model in ASYN C. The first phase of their gathering algorithm corresponds to forming a mutually visible configuration. They assumed that n is known beforehand and the robots have an agreement on the clockwise-counterclockwise orientation. Model Robots. The robots are assumed to be anonymous, autonomous, identical and homogeneous. Each robot is modeled as a disk of radius equal to 1 unit. The robots do not have access to any global coordinate system. Each robot perceives its surroundings based on its local coordinate system. We assume that their local coordinate systems agree on the direction and orientation of both axes. Visibility. Each robot is equipped with a slim omnidirectional camera. The embedded camera is modeled as a disk whose center coincides with the center of the robot. The diameter of the camera is strictly smaller than the diameter of the robot. For any robot r, B r and C r will respectively denote the disks representing the body and the camera of r. For a set of robots R = {r i,..., r n }, r j will be visible to r i iff ∃ points p i and p j on the boundaries of C ri and B rj respectively such that the line segment joining p i and p j (not including the end-points) lies inside Lights. Each robot is equipped with a visible light that can assume a constant number of pre-defined colors. The lights serve as a communication medium and also as a form of memory. In this paper, our algorithm uses 7 colors, namely off, defeated, leader, subordinate, no space, expand and final. Initially, all robots have their lights set to off. Look-Compute-Move cycles. Each robot, when active, operates in LOOK-COMPUTE-MOVE cycles. In the LOOK phase, a robot obtains a snapshot of the positions and colors of all robots which are visible to it. In the COMPUTE phase, based on the observed configuration, each robot computes a destination point and a color according to a deterministic distributed algorithm. The destination point may be its current position as well. Finally, in the MOVE phase, it sets its light to the decided color and moves towards the destination point (if the destination point is different from its current position). When a robot transitions from one LCM cycle to the next, all of its local memory is erased, except for the color of the light. Scheduler. We assume that the robots are controlled by a semi-synchronous (SSYN C) scheduler. In this model, time is logically divided into global rounds. In each round, one or more robots are activated. Each robot is activated infinitely often. The active robots take their snapshots simultaneously and then execute their moves concurrently. As a consequence, no robot is observed while moving. Movement. We assume that the robots have non-rigid movements. This means that a robot may stop before it reaches its destination. However, there is a fixed > 0 so that each robot traverses at least the distance unless its destination is closer than. For simplicity, we assume that ≥ 2. This is a reasonable assumption because, in practice, a robot should be able to move a distance of at least the extent of its diameter in one go. Also, with some minor modifications, our algorithm can be easily adapted to work without this assumption. Terminology We shall denote the set of robots by R = {r 1, r 2,..., r n }, n ≥ 3. The position of a robot will be specified by the position of its center. So when we say that a robot is at a point p on the plane, we shall mean that its center is at p. Also, when we say that the distance between two robots is d, we shall mean that the distance between their centers is d. With respect to the local coordinate systems of the robots, positive and negative directions of the X-axis will be referred to as east and west respectively, and the positive and negative directions of the Y -axis will be referred to as north and south respectively. Since the robots have two axis agreement, they agree on east, west, north and south. The orientation of the X-axis will be called horizontal, and the orientation of the Y -axis will be called vertical. Technical Difficulties and an Overview of Our Strategy In this section, we highlight some key difficulties of the problem in the current model and give an overview of our algorithm. A more formal description of the algorithm is provided in Section 5. A common approach to solve the MUTUAL VISIBILITY problem is to bring all the robots on the convex hull of the configuration. The robots on the convex hull set their lights to some particular color. This helps the interior robots to identify the convex hull. The interior robots then move to the convex hull. The main difficulty towards employing this strategy in our setting is that it is not always possible for a robot to correctly determine whether it is on the convex hull or not (see Fig. 2a). A robot can only be sure of being on the convex hull if it has ≥ 180 unobstructed view. However, a robot on the convex hull may not necessarily have ≥ 180 unobstructed view. In this case, we may ask such a robot (which 'thinks' that it may be on the convex hull but is not sure about it) to move outward so that it may get an obstructed view. However, the robots obstructing its view may also do the same and create obstruction in the resulting configuration as well. Also, since the convex hull may change due to the movements, a robot that was sure of being on the convex hull in the previous configuration and had changed its color accordingly may become an interior robot in the new configuration. Since the strategy of bringing the interior robots on a convex hull appears to be difficult to implement in this model, we try a different approach. Instead of trying to bring the interior robots on to the convex hull, we will sequentially build the convex hull anew. For this, we shall first elect a leader. It may appear that leader election is trivial with two axis agreement, since we can elect the leader as the southmost robot, and in the case of a tie, the eastmost robot among the southmost robots. However, we again face the problem of mistaken identity: a robot that is not southmost may not find any robot on its south (due to visibility obstructions) and thus wrongly infer that it is the southmost. We shall call such a robot a false southmost robot (see Fig. 3). So we see that the current visibility model prevents a straightforward solution to leader election by exploiting the two axis agreement assumption. We now give a brief description of how we solve the problem. When a robot finds (according to its local view) that it is southmost, it will move southwards in order to get an unobstructed view and determine whether it is actually southmost or not. If a robot finds that it is jointly southmost, it will only move if it does not see any robot to its east on the same horizontal line. Any other robot will change its color to defeated. We say that a robot is sure of being southmost if it has an unobstructed view of the south of the plane. This happens when all other robots are ≥ (1 − c) units to its north. We can show that eventually, there will be a robot that is sure of being the southmost. Now, if we ask this robot to become the leader by changing its color to leader, then the problem is that it may be overtaken by other robots which are also moving southwards (upon wrongly thinking of being southmost). Thus, we may have multiple robots with color leader. However, it can be shown that if a robot is able to reach at least D √ 3 units (D is an upper bound on the horizontal width of the initial configuration) to the south of the rest of the swarm, then there will be no subsequent movements by false southmost robots. To carry out the next stage of our mutual visibility algorithm, we also need an empty space of vertical width of at least 10 units. So we ask a robot to become the leader only when it finds that it is ≥ max{10, D Once the leader is elected, we enter the second stage of our algorithm. Here, the other robots will build a mutually visible structure with the leader. In particular, the mutually visible structure will be a chain, as shown in Fig. 4a, where the leader is at the southmost point, called the tip of the chain. We want the chain to be regular in the sense that all the sides and the angles are equal. The length of each side is called the stretch of the chain, and the value of each exterior angle is called the turning angle of the chain. Notice that, as shown in Fig. 5, the turning angle of the chain needs to be large enough in order to have mutual visibility. However, if the turning angle is too large, we may not be able to accommodate all the robots in the chain. We can prove that the minimum turning angle required for mutual visibility decreases if we increase the stretch. Therefore, depending on the total number of robots in the team, the stretch and the turning angle of the chain have to be adjusted so that all the robots can be accommodated within the chain while maintaining mutual visibility. The problem is that the size of the team is not known beforehand. So, the robots will start building the chain with some predefined value of stretch and turning angle, and then if they find out that the chain cannot accommodate all the robots, it will be rebuilt with a larger stretch and a smaller turning angle. Let us now describe the process of building the chain. As mentioned earlier, the robots will start building a chain with some predefined value of stretch and turning angle. Take the projection of the chain on the horizontal line through the leader, as shown in Fig. 4b. We call this projection the base chain. Recall that when the leader is set, all other robots are to the north of the leader. These robots will then sequentially come and place themselves on the base chain. The first robot will place itself on the east of the leader, the second robot will place itself on the west of the leader, the next one will go to the east, and so on. Notice that the distance between two consecutive points on the base chain gradually decreases. When this distance becomes less than 2 units, a new robot cannot be accommodated. When this happens, the next robot will set its light to no space. Then a chain with a larger stretch and a smaller turning angle will be chosen and the robots will reposition themselves on the corresponding base chain. Finally, we will obtain a base chain where all robots can be accommodated. Then, the robots will move vertically to form the corresponding chain. Basic Properties of the Mutually Visible Chain In this section, we prove some basic properties of the mutually visible chain. Lemma 1. Let r 1, r 2 and r 3 be three robots located at three consecutive points of a chain of stretch d and turning angle. The robots r 1 and r 3 will be visible to each other if and only if sin > 1−c d. Proof. Let A, B and C denote the centers of r 1, r 2 and r 3 respectively. We have d( Assume that the turning angle be such that the three circles C r1, B r2 and B r3 share a tangent as shown in Fig. 6a. We shall show that sin = 1−c d. It is easy to see that our claim follows from this. Let us draw Fig. 6a in a slightly different way so that the common tangent is horizontal. In particular, fix a coordinate system with the origin at B and BC as the negative direction of the X axis (see Fig. 6b). Proof. Let r and r be any two robots on the chain. We shall show that r can see r. From symmetry, it will imply that r is also able to see r. Suppose there are i robots between r and r on the chain. We prove the result by using induction on i. For i = 0, there is nothing to prove. For i = 1, the result follows from Lemma 1. So assume that i > 1. Assume that the result is true for i − 1. Suppose that the robots from r to r are arranged on the chain as r, r 1,..., r i, r. It follows from the induction hypothesis that r i is visible to r. Consider the region between l 1 and l i where l 1 is a tangent on C r, B r1 and l i is a tangent on C r, B ri (see Fig. 7a). If there is any portion of r outside this region, then it must be visible to r. Notice that it is sufficient to show that r is not obstructed by r i. In other words, it is sufficient to only consider r, r i and r. So the equation of the common tangent is If we have three robots at A, B, C such that d(A, B) = d(B, C) = d and ∠ABC < − sin −1 ( 1−c d ), then by Lemma 1, the robot at A can see the robot at C. Notice that the same is true if we have d(A, B) > d(B, C) = d. This is because the obstructed region of the second case is contained inside the obstructed region of the first case (see Fig. 7b). Notice that this holds for the robots r, r i and r. Hence, r is able to see r. In our algorithm, we shall set the stretch d and turning angle of the chain so that sin = 1 d > 1−c d. This will imply that the final configuration is a mutually visible configuration. Algorithm In this section, we shall describe our main algorithm. A set of n ≥ 3 robots are arbitrarily placed on the plane. Initially, the lights of all robots are set to off. The size of the swarm, n, is not known to the robots. However, an upper bound D on the horizontal width of the initial configuration is known in advance. This means that the horizontal distance between no two robots in the initial configuration is more than D. The execution of our algorithm can be divided into two stages: first, a leader is elected, and then the mutually visible chain is built. The execution from the beginning up till a leader is elected will be called Stage 1. The rest will be called Stage 2. A robot, however, may not be aware of the current stage of the process due to its incomplete view of the configuration. Our algorithm uses 7 colors, namely off, defeated, leader, subordinate, no space, expand and final. The last 5 colors can be found only in Stage 2. So we call these colors as Stage 2 colors. Leader Election We shall first describe the process of electing the leader. We want to have a unique robot having its light set to the color leader. We also want to maintain a distance between this robot and the rest of the swarm. This space will be used in the next stage for building the base chain. Our plan is to have a single southmost robot in the configuration and elect it as the leader. For this, we need to have a robot that is sure of being the southmost. Recall that initially, all robots have color off. If such a robot can see a robot on its south, then it will change its color to defeated. It will also do the same if it finds a robot on the same horizontal line on its east. Robots with color defeated will not further take part in the leader election procedure. Now consider the case where a robot with color off does not see any robot to its south and also does not find any robot on the same horizontal line on its east. If it is not sure of being southmost, then it will move 2 units to the south. It can be shown that these movements will ensure that we have a robot that is sure of being the southmost. Now, we shall not ask this robot to become the leader immediately by changing its color to leader. We want to have the leader at least 10 units to the south of the rest of the swarm. As mentioned earlier, we need this space for the execution of Stage 2. So the robot may need to move further southwards so that it is ≥ 10 units to the south of the rest. However, even after ≥ 10 units of separation is achieved, there might still exist false southmost robots in the swarm that will move southward. We do not want such movements to occur after the leader is elected. It can be shown that if we can achieve ≥ D √ 3 units of separation, then there will not be any such unwanted movements in the future. So we shall ask the robot to move southwards until it is ≥ max {10, D √ 3 } units to the south of the rest. When this separation is attained, the robot will change its color to leader. Formation of the Mutually Visible Chain Let r L denote the elected leader. The leader r L will not make any moves in the remainder of the algorithm. Now we can fix a coordinate system with the origin at the center of r L, the positive direction of the X-axis along the east and the positive direction of the Y -axis along the north. Any robot that can see the leader r L will agree with this coordinate system. For any number d, L d will denote the horizontal line Y = d. If an off or defeated colored robot sees any robot with Stage 2 color, then it will change its color to subordinate. So the robots with color subordinate are aware that a leader has been elected, and we have entered the next stage of the algorithm. Now the first task is to form the base chain. We want this process to be sequential, i.e., we want the robots to come one by one and place themselves on the base chain. However, sequentializing the process is a bit tricky. For example, if we ask the southmost subordinate colored robot to go first, then we can still have parallel movements due to the false southmost robots. So let us now describe how we sequentialize the movements. First, we ask the robots to come to L 10. In particular, if a robot r with color subordinate is to the north of L 10 and the vertical path to L 10 has no obstructions, then it will move towards L 10. Fig. 8 shows situations where the vertical path of a robot to L 10 is obstructed. Now we want to move one robot from L 10 to L 8. For this, if there are multiple robots on L 10, then we ask the one that is closest to the Y -axis to move 2 units southwards to reach L 8. In case there are two robots closest to the Y -axis, then the one on the east will move. Also, the robot will move only if it finds no robot on L 8. However, in spite of this strategy, we may have multiple robots on L 8. An example of this is shown in Fig. 9. So there can be multiple robots on L 8. If we try to move south one among these robots in a similar fashion, then we can again face the same problem and have multiple robots on L 6. To resolve this, we shall ask the robots to leave via the Y -axis, i.e., a robot may need to move along L 8 towards the Y -axis and then leave L 8 only when it is touching the Y -axis. This strategy will ensure that at any time, we have at most one robot on L 6. This is because a robot on L 8 touching the Y -axis will be able to detect if there is a robot on L 6 as that robot also must be touching the Y -axis. However, notice that there is a possibility of a collision between a robot r moving horizontally along L 8 and another robot r moving southwards from L 10 to L 8. This can happen in a situation where r cannot see r and thinks that L 8 is empty. In order to avert such a collision, r will do the following. The robot r will identify all the robots on L 10 with which it can collide if that robot moves southwards. Notice that r will be able to find all such robots, as there are no robots on L 8 in the portion between the Y -axis and itself that can obstruct its view. If r finds no such robots on L 10, then there is no problem, and it will move towards the Y -axis as required (see Fig. 10a). If r finds only one such robot, say r, then clearly r can also see r (see Fig. 10b). Hence, r will not move in this case, and thus, there is no possibility of a collision. So in this case, r will simply ignore r and move towards the Y -axis. Now consider the case where r has found multiple robots on L 10. In this case, only the one that is closest to the Y -axis, say r, is to be considered as only this robot may decide to move southwards (see Fig. 10c and 10d). Let d be the horizontal distance between r and r. Notice that if d is small enough, i.e., r and r are close enough, then r will be able to see r and hence r will not move. More precisely, it can be shown that if d ≤ 5, then r will be able to see r. Intuitively, the worst case of obstruction occurs when a robot is touching r and the radius of the camera is zero, i.e., a point camera (see Fig. 10f). Formally, the obstructed region in any other case will be contained in the obstructed region for this case (see Fig. 10e). Hence, it suffices to argue for this case. Using simple calculations, one can verify that r will be visible to r in this worst case situation if d ≤ 5 (see Fig. 10f). So if d ≤ 5, r will ignore r and move towards the Y -axis. Otherwise, if d > 5, then in order to avert a collision, r will not move more than d − 2 units. Y -axis Y -axis Y -axis (c) Figure 9: A situation where we have multiple robots on L 8. (a) The robots r 2 and r 3 decide to move to L 10. Also, r 1 being closest to the Y -axis on L 10, decides to move to L 8. (b) r 2 does not see any robot on L 8, and hence decides to move to L 8. r 1 is not activated. (c) We have multiple robots on L 8. Our strategy ensures that the robots come to L 6 sequentially. When a robot r comes to L 6, it first checks if there is any robot in the region between L 6 and L 0. If there is such a robot, then r will do nothing. Otherwise, it will calculate the position on the base chain on L 0 where it has to place itself. Recall that the robots have to alternatively go to the east and west branches of the base chain. So if r finds that both branches have k robots, then it has to go to the east branch, while if it finds that the east branch has k robots and the west branch has k − 1 robots, then it has to go to the west branch. The robot can compute its position by calculating the stretch of the corresponding mutually visible chain from the distance between r L and its nearest robot on the base chain using Lemma 3. If r is the first robot on the branch, we set its position to be 4 units from r L. If its computed position is < 2 units from the last robot on its branch of the base chain, then it means that there is no more space on the base chain, and an expansion is required. First, consider the case where there is room for r on the base chain. In this case, it will first move to L 2, then move along L 2 to vertically align with its computed position on the base chain. Finally, it moves towards the south to place itself on the base chain on L 0 (see Fig. 11a and 11b). Now consider the case where r finds that there is no space, and so the base chain has to be expanded. There is no possibility of a collision between r and r. This is because r can see r and hence will not move south. (c) There is a possibility of a collision between r and r. This is because r may not be able to see r as their horizontal separation is > 5 units. (d) There is no possibility of a collision between r and r. This is because r can see r as their horizontal separation is ≤ 5 units. (e) The worst case of obstruction occurs when a robot is touching r and the radius of the camera is zero. This is because the obstructed region in any other case will be contained in the obstructed region for this case. (f) In the worst case of obstruction, r is visible to r if their horizontal separation is ≤ 5. In this case, r will change its color to no space. When the leader r L (with color leader) finds r with color no space, it will change its color to expand. The plan now is that all the robots of the base chain, except the leader, will move to L 4 and place themselves on the X-coordinates of the expanded chain. In this case, L 2 will be used for horizontal movements. The leader r L will be able to detect when all the robots have placed themselves on L 4 at their respective positions. While the leader detects, it will change its color back to leader. Finally, r will also change its color to subordinate and the robots on L 4 will move vertically to L 0. This completes the expansion of the base chain. We describe this part of the algorithm in more detail in the following. Figure 11: (a) r will go to the east branch of the base chain. (b) r will go to the west branch of the base chain. (c) r changes its color to no space and then r L changes its color expand. (d) The movement of r 1 from L 0 to L 4. (e) The movement of r i, i > 1 from L 0 to L 4. (f) After all robots move to L 4, r L changes its color to leader and then r changes its color to subordinate. When a robot on L 0 with color subordinate sees the leader with color expand, it understands that the base chain is being expanded. Let us denote the robots on the base chain as r 1, r 2,... and r 1, r 2,... as shown in Fig. 11c. So r i (resp. r 1 ) will be able to see the leader (with color expand) when r 1,..., r i−1 (resp. r 1,..., r i−1 ) have left L 0. When such a robot on L 0 is able to see r L with color expand, it will check if there is any robot on L 2 in its half. If there is none, then it will move to L 2. Now consider a robot r i or r i on L 2. It can understand that it is the ith robot on the chain as it can see i − 1 robots on L 4 on its half. It now has to move horizontally and align itself with its position in the expanded base chain. We explain how r i or r i will calculate its position on the expanded base chain. For this, the robot just needs to find the stretch of the expanded chain. If i ≤ 2, then it can see r 1 or r 1 on L 4 and thus, they can calculate the stretch of the expanded chain using Lemma 3. When i = 1, the robot has to set the stretch of the new chain. The stretch has to be larger than the stretch of the current chain. We also have to ensure that both r 1 or r 1 choose the same stretch. This can be easily achieved by asking r 1 (resp. r 1 ) to align with r 2 (resp. r 2 ) on L 2 (i.e., the distance of the first robot from the leader on the new base chain will be equal to the distance of the second robot from the leader on the old base chain). The leader r L will be able to detect when all the robots have placed themselves on L 4 (see Fig.11f). Then it will change its color back to leader. When r with color no space sees that r L has color leader and robots are queued on L 4, then it will understand that all robots from L 0 (except r L ) have moved to L 4 and then it will change its color back to subordinate. Now for a robot r i on L 4, it will decide to move back to L 0 when it can see r L with color leader and a robot on L 6 with color subordinate. Now let us consider the special case where a robot r finds that all the other robots are on the base chain. We call r the last robot. In this case, r will not try to go to the base chain. Here, r will compute its final position on the mutually visible chain and go there directly. We shall ask the last robot r to always go to the west branch of the chain (see Fig. 12a). When r reaches its final position, it will change its color to final. Let r 1, r 2,... and r 1, r 2,... be the robots on the base chain as shown in Fig. 12a. Now the robots r k, r k−1,..., r 1 will have to go to their final positions sequentially, from west to east. After r, r k,..., r i+1 have gone to their final positions and changed their colors to final, r i will find that all robots on its west have color final (see Fig. 12b). Then r i will decide to move. Notice, however, that r i will not be able to see r L unless i = 1 and hence cannot compute its final position. In this case, r i will first move 2 units north. Then it will be able to see both r 1 and r L, and thus can infer the stretch of the chain using Lemma 3. So, then it can compute its final position and move towards it. When all the robots on the west branch have placed themselves at their final positions and changed their colors to final, the leader r L will also change its color to final (see Fig. 12e). Now the east branch robots r 1, r 2,..., r k will have to go to their final positions sequentially, from west to east. After r 1,..., r i−1 have gone to their final positions and changed their colors to final, r i will find that all robots on its west have color final (see Fig. 12f). Then r i will decide to move. The robot r i will first move vertically 2 units to the north of r i−1 (see Fig. 12g). From there, r i will be able to see r i−1 which is horizontally aligned with r i−1. The robot r i will also be able to identify r i which is immediately to the east of r i−1. The final position of r i will be horizontally aligned with r i. So r i will then align itself with r i and change its color to final. With this strategy, all the robots will be able to place themselves on the mutually visible chain (see Fig. 12h). Proof. In a configuration with no leader, there are two types of robots: robots with color off and robots with color defeated. Let us call the off colored robots live robots and defeated colored robots defeated robots. For any live robot r in a configuration with no leader, we associate a set B(r) in the following way. We call a robot r bad with respect to r if either r is on the same horizontal line as r, or r is to the north of r, but their vertical separation is < 1 − c. According to this definition, if there is a false southmost robot in the configuration, then there must be a bad robot with respect to it, which is obstructing its southward view. For any live robot r, the set B(r) consists of 1) all bad robots with respect to r, 2) all live robots that are to the north of r, and 3) all robots that are to the south of r. Intuitively, the set B(r) contains all the robots that are either currently bad or may become bad in the future. Although the robots in 2) are not currently bad with respect to r, they may move southward and become so in the future. Similarly, a robot from 3) may become bad with respect to r in the future if r moves southward. Now let B denote the set of all pairs (r, r ) where r is a live robot and r ∈ B(r). We first show that the size of the set B never increases. Observe that the number of live robots in the configuration never increases. Also, for any live robot r, the robots outside B(r) are precisely the defeated robots that are ≥ (1 − c) units to the north of r. Clearly, these robots will never enter B(r). Hence, it follows that |B| cannot increase. Now we show that the size of the set B gradually decreases. Consider any round t. Assume that there is no leader in the configuration. Consider the robot r that is northmost among all live robots. If there are multiple such robots, then take the westhmost one. Let t ≥ t be the earliest round when r is active. Case 1. Suppose that r can see a robot r on its south. Hence (r, r ) ∈ B. In this case, r will change its color to defeated. Thus, (r, r ) is removed from B and hence |B| decreases. Case 2. Suppose that the robot r thinks that it is southmost and its southward view is obstructed by a robot r to its north. Clearly, the vertical distance between r and r is < (1 − c) units. Hence (r, r ) ∈ B. It follows from the definition of r that the color of r is defeated. In this case, r will move 2 units south. Thus, (r, r ) is removed from B and hence |B| decreases. Case 3. Suppose that the robot r thinks that it is southmost, but its southward view is obstructed by a robot r on the same horizontal line. Hence (r, r ) ∈ B. It follows from the definition of r that r is to the east of r. So r will change its color to defeated. Thus, (r, r ) is removed from B and hence |B| decreases. Case 4. Suppose that the robot r is sure of being southmost. But r is also the northmost among all the live robots. This means that r is the only live robot in the configuration. Also, all other robots have color defeated and they are ≥ (1 − c) units to the north of r. So we have |B| = 0. We have shown that, while there is no leader in the configuration, |B| gradually decreases. In particular, it implies that there exists a round when either 1) there is a leader or 2) |B| = 0. In the first case, we are done. In the latter case, there is only one live robot r, which is surely southmost, and all the other robots are defeated. Since the defeated robots do not move, r will be able to make ≥ max {10, D √ 3 } units vertical separation from the rest and then become the leader by changing its color to leader. Hence, there is a round T 1 when we have a leader. Lemma 4. There are no off colored false southmost robots after the leader is elected at T 1. Proof. Let S be the smallest vertical strip containing the initial configuration. The horizontal width of S is ≤ D. At any time during the execution of the algorithm, an off colored robot must be inside S. This is because an off colored robot only moves vertically. Consider the set O of all off colored robots in the configuration at round t. Take any r ∈ O. Let t be the earliest round ≥ T 1 when r becomes active. We claim that r will see some robot to its south and hence will change its color. For the sake of contradiction, assume that r is a false southmost robot at round t. Now consider the region in S to the south of r that is invisible to it. Since r does not see any robot on its south, the vertical extent of this region will be maximum when r is obstructed by a robot r on the same horizontal line at a distance 2 and the radius of the camera is 0 (i.e., a point camera). Such a situation is shown in Fig. 13. The vertical extent of the obstructed region is |DE|. Since the triangles ∆ABC and ∆ADE are similar,. Therefore, any robot ≥ D √ 3 to the south of r must be visible to it. So r L is visible to r. This contradicts our assumption that r is false southmost. It follows from Lemma 4 that if there remains any off colored robot after leader election, then the next round it is activated, it will change its color to defeated or subordinate. Any defeated colored robot that can see the leader or any subordinate colored robot will change its color to subordinate. These robots will move southwards to build the base chain. The robots will come to L 6 sequentially. After a robot comes to L 6, it will then go to L 0 and place itself on the base chain if there is space. Otherwise, the base chain will be first expanded before it can go to L 0. From the discussions in Section 5.2, it follows that the robots will carry out these steps correctly. Therefore, a base chain consisting of n − 1 robots will be built in this way. Then the last robot will go directly to its place in the corresponding mutually visible chain and change its color to final. Then the n − 1 robots on the base chain will sequentially move vertically to place themselves in their respective positions on the corresponding chain. Again, it follows from the discussions in Section 5.2 that the robots will be able to execute these steps correctly. Therefore, we have the following result. Theorem 2. There is a round T 2 > T 1 when a base chain consisting of n − 1 robots is built. Then there is a round T 3 > T 2 when the corresponding chain of n robots is built. By Lemma 2 it follows that any two robots are visible to each other in the configuration at round T 3. Proof. It follows from the proof of Theorem 1 that the leader is elected within O(n) epochs. The nonleader robots will now sequentially place themselves on the base chain. If no expansion is needed, then it takes O epochs for a robot to place itself on the base chain. If an expansion is needed, then it has to wait on L 6 for the expansion to complete. An expansion is completed within O(n) epochs. So construction of the base chain takes O(n(1 + e(n))) epochs. Formation of the mutually visible chain from the base chain is done within O(n) epochs. So in total, the algorithm requires O(n(1 + e(n))) epochs to complete. Simulation Framework We designed a Python-based simulation framework to carry out the experiments. The key component of the simulation framework is an algorithm that determines the view of a robot in our adopted visibility model. In particular, for a set R of opaque fat robots with slim omnidirectional camera, we need to determine if a robot r ∈ R can see another robot r ∈ R. We provide a brief description of the algorithm in the following. Without loss of generality, assume that r and r are on the same vertical line. Draw the direct tangents to C r and B r. Let A, A, B, B be the points where the tangents touch the disks as shown in Fig. 14a. Notice that only the arc between A and B can be visible to r. Let L = {r ∈ R \ {r, r } | B r intersects the line segment AA } and R = {r ∈ R \ {r, r } | B r intersects the line segment BB }. We call L the set of left obstructions of r and R the set of right obstructions of r. Notice that only the robots of L ∪ R will cause obstructions. So we can ignore all the other robots. For each r ∈ L ∪ R, draw direct tangents to C r and B r. The region between the two tangents as shown in Fig. 14b is called the type I bad region defined by r. If any portion of the arc A B lies in this region, then trim off that portion. If any robot r ∈ R \ {r, r } intersects both AA and BB, i.e., we have L ∩ R = ∅, then r is not visible to r. This is because in that case, B r lies entirely inside the bad region defined by r. So now assume that L ∩ R = ∅. For each pair (r, r ) ∈ L R, draw the transverse tangents to B r and B r (see Fig. 14c). The regions between the two tangents as shown in Fig. 14c are called the type II bad regions defined by r and r. If any portion of the arc A B lies in these regions, then trim off that portion. The algorithm decides that r is visible to r if and only if the arc A B is not completely trimmed out. Theorem 5. The algorithm described above is correct. Proof. If L ∩ R = ∅, the algorithm decides that r is not visible to r. This is obviously correct. So now assume that L ∩ R = ∅. Take any point p on the arc A B. To prove the theorem, we have to show that p is visible to r if and only if it survives the trimmings. Now draw tangents from p to the robots of L and let L be the rightmost one (see Fig. 15a Figure 15: (a) The red ray is L and the blue ray is R. The shaded region is U p. (b) When p is in the bad region, C r is completely to the left of the right tangent from p to B r. (c) When p is outside the bad region, some portion of C r is to the right of the right tangent from p to B r. (d) When p is in the bad region, the right tangent from p to B r is to the right of the left tangent from p to B r. (e) When p is outside the bad region, the right tangent from p to B r is to the left of the left tangent from p to B r. Recall that we have to prove that p survives the trimmings if and only if C r ∩ U p = ∅. Let us first prove that if p does not survive the trimmings, then C r ∩ U p = ∅. So take a point p such that it is inside a bad region of type I or type II. Suppose that p is inside a bad region of type I defined by, without loss of generality, a left obstacle r ∈ L. If be the right tangent from p to B r, then by Observation 1, C r is completely to the left of. This implies that C r is completely to the left of L and hence C r ∩ U p = ∅. Now suppose that p is inside a bad region of type II defined by r ∈ L and r ∈ R. Let be the right tangent from p to B r and be the left tangent from p to B r. Then, by Observation 2, is to the right of, which implies that L is to the right of R. This implies that U p = ∅, and hence C r ∩ U p = ∅. Finally, we show that if p survives the trimmings, then C r ∩ U p = ∅. So take a p such that it is outside all bad regions. For any r ∈ L and r ∈ R, is to the left of, where is the right tangent from p to B r and is the left tangent from p to B r (by Observation 2). In particular, L is to the left of R. This means that U p = ∅. For any r ∈ L, some portion of C r is to the right of, where is the right tangent from p to B r (by Observation 1). In particular, some portion of C r is to the right of L. Similarly, some portion of C r is to the left of R. This implies that C r ∩ U p = ∅. Figure 16: The red ray is L and the blue ray is R. (a) p is visible to r because C r ∩ U p = ∅ (b)-(c) p is not visible to r because C r ∩ U p = ∅. In case of (c), U p is empty, while in case of (b), U p is non-empty, but it does not overlap C r. Experimental Results We first focus on the leader election stage of the algorithm. We analyzed the round complexity of the leader election stage in Section 6 where we have proved an upper bound of O(n) epochs. The main source of difficulty in the leader election problem was the existence of false southmost robots. Movements of the false southmost robots can prevent the actual southmost robot from creating the required vertical separation from the rest of the team. We showed that n − 1 robots would change their colors to defeated within O(n) rounds. After this, there are no movements from these robots and the southmost robot can establish the required vertical separation in O epochs. This gave the O(n) upper bound for the leader election stage. However, our simulations reveal that the problematic movements of the false southmost robots occur scarcely. As a result, the O(n) epoch bound may be quite loose. Details of the experimental results are expounded in the following. We randomly generate initial configurations of robots inside a rectangular region. In particular, the position of each robot is generated uniformly at random inside the rectangular region. If the generated point is within 2 units of a previously generated point, then we discard it and try again. To simulate an SSYN C scheduler, the activation of each robot at any round is set as a Bernoulli process Bern(p). When p = 1, it coincides with an FSYN C scheduler. Under this framework, we first simulate our leader election algorithm in FSYN C and note the following: 1. m = the number of moves by false southmost robots, 2. r = the number of epochs needed for n − 1 robots to change their colors to defeated. We first run the algorithm for different rectangular deployment regions for n = 30 robots. The algorithm is run 100 times in each case. The results are presented in Fig. 17. The results reveal the effect of the shapes of the rectangles (length of horizontal and vertical sides) and robot density (number of robots per unit 2 area). We can see that the problematic moves by false southmost robots are quite rare, in particular m ≤ 4 in each run. As a result, the number of rounds needed for n − 1 robots to change their colors to defeated is significantly less than what our theoretical analysis suggests. In particular, we see that r ≤ 4 in each run. We also observe that m and r are higher in the case of deployment regions with larger horizontal sides. This is because false southmost robots are usually found in the southmost layer of the configuration (see Fig. 18a). As a result, we are more likely to have numerous false southmost robots in horizontally stretched deployment regions. However, it is possible to have false southmost robots at any part of a configuration as shown in Fig. 18b where even a northmost robot is false southmost. Although one can contrive many such configurations, they are unlikely to show up in random deployments. We also see that m and r tend to drop as robot density decreases. This is quite natural, as there are more visibility obstruction in dense configurations. We can infer from these observations that the horizontal extent and the density of the initial configuration are the main factors determining m and r. To further test the above statement, we repeat the experiments for different sizes of the swarm, but choosing the deployment regions in such a way that the density and horizontal width are the same in each case. In particular, the density and horizontal width in each case are respectively 0.2 robots/unit 2 and 25 units. The results are presented in Fig. 19. As expected, we did not see any discernible effects due to the varying size of the swarm. The experiments we have discussed till now were all carried out in the FSYN C setting. Notice that in FSYN C, the robot that becomes the leader is the actual southmost robot in the initial configuration. However, in SSYN C, a false southmost robot may also become the leader. The main observation from the experiments conducted in FSYN C was that the problematic moves by robots other than the eventual leader are only a few in number. In SSYN C, they are even rarer. We ran the algorithm for different activation probabilities, observing that these moves become rarer as the activation probability decreases (see Fig. 20). Recall that the algorithm asks the leader to establish ≥ max {10, D √ 3 } units of vertical separation from the rest of the swarm. The ≥ D √ 3 unit vertical separation ensures that no moves by off colored false southmost robots occur after the leader is elected. This property helps to simplify the correctness proof, but requires the assumption that the robots have the knowledge of D. However, the experiments show that such moves are quite rare. Also, even if such a move occurs after the leader is elected, it is unlikely to hamper the algorithm. Therefore, it is fine in practice to ask for only ≥ 10 units of vertical separation and drop the assumption about the knowledge of D. We now focus on the entire mutual visibility algorithm. We evaluate the performance of our algorithm in terms of time complexity and total distance traversed by the robots. Recall that we assumed that the size of the team is not known beforehand. If the number of robots was known, then the optimum stretch required for accommodating all robots on the base chain can be calculated in advance. Without this knowledge, we adopt a trial and error approach, i.e., start with some value of stretch and increase it by some amount when we find it to be inadequate. In Fig. 21a, we compare the stretch set by our algorithm with the optimum value sufficient to form the base chain. The jumps in the graph correspond to the expansions, i.e., when we find that our previously set stretch is not large enough and increase it (by setting the position of the first robot to be the position of the second robot of the previous base chain). The stretch determines the horizontal and vertical widths of the final configuration. They are shown in Fig. 21b. One can see that these graphs also have bumps corresponding to the ones in Fig. 21a. The expansion also affects the time complexity and total distance traversed. Observed values of time and total distance traversed are presented in Fig. 22a and Fig. 22b respectively. These graphs also have similar bumps as expected. For these experiments, we chose a square deployment region with sides of length 25 units, FSYN C scheduler and rigid movement model. Figure 21: (a) Comparison between the optimal stretch required (so that the base chain can accommodate n − 1 robots) and the stretch set by our algorithm (when the size of the swarm is not known beforehand). (b) The horizontal and vertical width of the final configuration for varying swarm size. Note that the total distance traversed should also depend on the horizontal width H and vertical width V of the initial configuration. To observe their effects, we ran the algorithm for horizontally stretched (10:1) and vertically stretched (1:10) deployment regions with 30 robots. The results are presented in Fig. 23. Our previous experiments suggest that in the case of horizontally stretched regions, there will be more moves by false southmost robots. This will slightly increase the total distance traversed in the case of horizontally stretched regions. However, the results in Fig. 23 show the opposite. The reason is the following. H affects the total distance traversed because the robots have to move horizontally to reach the Y -axis (passing through the leader). On the other hand, there is an influence of V because the robots have to move southwards to reach the leader. Notice that in the case of a horizontally stretched 10a a deployment region, the best case (with respect to the horizontal moves) is when the elected leader is from the middle portion of the region. In this case, the robots have to move roughly at most 5a units to reach the Y -axis. The worst case (with respect to the horizontal moves) is when the leader is from the eastmost or westmost portion of the region, as in this case, a large section (roughly half) of the robots have to move more than 5a units. For the vertically stretched a 10a deployment region, in all cases, roughly half of the robots move more than 5a units to come out of the deployment region. For this reason, the total distance traversed on average for the horizontally stretched deployment regions is lower, but the standard deviation is higher; on the other hand, the total distance traversed on average for the vertically stretched deployment regions is higher, but the standard deviation is lower (see Fig. 23). Concluding Remarks In this paper, we presented an algorithm for MUTUAL VISIBILITY by opaque fat robots with slim omnidirectional camera. We proved the correctness of our algorithm in the SSYN C setting. The SSYN C assumption is required to prove the correctness of the leader election stage of the algorithm. The rest of the algorithm can be easily adapted to the ASYN C setting with some minor modifications. The main difficulty of the leader election stage arises due to the moves by false southmost robots. However, they are quite rare, as we have seen in our simulations. Hence, our algorithm should work well also in the ASYN C setting as a heuristic. However, it might be of theoretical interest to have a provably correct algorithm for leader election in ASYN C. We believe that it might be possible to adapt our approach to the ASYN C setting to obtain a provably correct algorithm. We assumed that the robots have an agreement on the direction and orientation of both X and Y axes of their local coordinate systems. An interesting direction for future research is to solve the problem without any agreement on the coordinate system. Our approach to solve the problem was to first elect a leader and then arrange the robots on a mutually visible chain. Without any agreement on the coordinate system, there are some initial symmetric configurations in which leader election is deterministically unsolvable. So, in this case, one can try to solve leader election using randomization and then try to build the mutually visible chain. However, it might be of theoretical interest to have a fully deterministic solution. Since leader election is not always deterministically solvable, a new approach is needed so that the problem can be directly solved without requiring to elect a leader. |
Neanderthal anatomy
Neanderthal anatomy differed from modern humans in that they had a more robust build and distinctive morphological features, especially on the cranium, which gradually accumulated more derived aspects, particularly in certain isolated geographic regions.
Anatomical evidence suggests they were much stronger than modern humans while they were slightly shorter than the average human, based on 45 long bones from at most 14 males and 7 females, height estimates using different methods yielded averages in the range of 164–168 cm (65–66 in) for males and 152–156 cm (60–61 in) for females. Samples of 26 specimens in 2010 found an average weight of 77.6 kg (171 lb) for males and 66.4 kg (146 lb) for females.
A 2007 genetic study suggested some Neanderthals may have had red hair.
Cold-adapted theory
Some people thought that the large Neanderthal noses were an adaptation to the cold, but primate and arctic animal studies have shown sinus size reduction in areas of extreme cold rather than enlargement in accordance with Allen's rule. Todd C. Rae summarizes explanations about Neanderthal anatomy as trying to find explanations for the "paradox" that their traits are not cold-adapted. Therefore, Rae concludes that the design of the large and extensive Neanderthal nose was evolved for the hotter climate of the Middle East and went unchanged when the Neanderthals entered Europe. However Neanderthals in Spain date back to 700,000 years, prior to them living in the Middle East. Rae supposes that Neandertals, due to increased physical activity and a large amount of muscle mass, would have needed increased oxygen uptake.
Levantine Neanderthals had phenotypes significantly more similar to modern humans than European Neanderthals (classic Neanderthals). This may be because of gene flow from early modern humans in the Levantine corridor or the fact that the European Neanderthal phenotype is a specialized climatic adaptation.
Pathology
Within the west Asian and European record, there are five broad groups of pathology or injury noted in Neanderthal skeletons.
Fractures
Neanderthals seemed to suffer a high frequency of fractures, especially common on the ribs (Shanidar IV, La Chapelle-aux-Saints 1 'Old Man'), the femur (La Ferrassie 1), fibulae (La Ferrassie 2 and Tabun 1), spine (Kebara 2) and skull (Shanidar I, Krapina, Sala 1). These fractures are often healed and show little or no sign of infection, suggesting that injured individuals were cared for during times of incapacitation. It has been remarked that Neanderthals showed a frequency of such injuries comparable to that of modern rodeo professionals, showing frequent contact with large, combative mammals. The pattern of fractures, along with the absence of throwing weapons, suggests that they may have hunted by leaping onto their prey and stabbing or even wrestling it to the ground.
Trauma
Particularly related to fractures are cases of trauma seen on many skeletons of Neanderthals. These usually take the form of stab wounds, as seen on Shanidar III, whose lung was probably punctured by a stab wound to the chest between the eighth and ninth ribs. This may have been an intentional attack or merely a hunting accident; either way the man survived for some weeks after his injury before being killed by a rock fall in the Shanidar cave. Other signs of trauma include blows to the head (Shanidar I and IV, Krapina), all of which seemed to have healed, although traces of the scalp wounds are visible on the surface of the skulls.
Degenerative disease
Arthritis was common in the older Neanderthal population, specifically targeting areas of articulation such as the ankle (Shanidar III), spine and hips (La Chapelle-aux-Saints 'Old Man'), arms (La Quina 5, Krapina, Feldhofer) knees, fingers and toes. This is closely related to degenerative joint disease, which can range from normal, use-related degeneration to painful, debilitating restriction of movement and deformity and is seen in varying degree in the Shanidar skeletons (I–IV).
Developmental stress
Two non-specific indicators of stress during development are found in teeth, which record stresses, such as periods of food scarcity or illness, that disrupt normal dental growth. One indicator is enamel hypoplasia, which appears as pits, grooves, or lines in the hard enamel covering of teeth. The other indicator, fluctuating asymmetry, manifests as random departures from symmetry in paired biological structures (such as right and left teeth). Teeth do not grow in size after they form nor do they produce new enamel, so enamel hypoplasia and fluctuating asymmetry provide a permanent record of developmental stresses occurring in infancy and childhood. A study of 669 Neanderthal crowns showed that 75% of individuals suffered some degree of hypoplasia. Two studies, compared Neanderthals with the Tigara, coastal whale-hunting people from Point Hope Alaska, finding comparable levels of linear enamel hypoplasia (a specific form of hypoplasia) and higher levels of fluctuating asymmetry in Neanderthals. Estimated stress episode duration from Neanderthal linear enamel hyoplasias suggest that Neandertals experienced stresses lasting from two weeks to up to three months.
Infection
Evidence of infections on Neanderthal skeletons is usually visible in the form of lesions on the bone, which are created by systemic infection on areas closest to the bone. Shanidar I has evidence of the degenerative lesions as does La Ferrassie 1, whose lesions on both femora, tibiae and fibulae are indicative of a systemic infection or carcinoma (malignant tumour/cancer).
Childhood
Neanderthal children may have grown faster than modern human children. Modern humans have the slowest body growth of any mammal during childhood (the period between infancy and puberty) with lack of growth during this period being made up later in an adolescent growth spurt. The possibility that Neanderthal childhood growth was different was first raised in 1928 by the excavators of the Mousterian rock-shelter of a Neanderthal juvenile. Arthur Keith in 1931 wrote, "Apparently Neanderthal children assumed the appearances of maturity at an earlier age than modern children." The rate of body maturation can be inferred by comparing the maturity of a juvenile's fossil remains and the estimated age of death.
The age at which juveniles can be indirectly inferred from their tooth morphology, development and emergence. This has been argued to both support and question the existence of a maturation difference between Neanderthals and modern humans. Since 2007, tooth age can be directly calculated using the noninvasive imaging of growth patterns in tooth enamel by means of x-ray synchrotron microtomography.
This research supports the occurrence of much more rapid physical development in Neanderthals than in modern human children. The x-ray synchrotron microtomography study of early H. sapiens sapiens argues that this difference existed between the two species as far back as 160,000 years before present.
More recent research, published in September 2017 and based on a more complete skeleton of a Neanderthal juvenile (7.7 years old) found in a 49,000 year old site in Northern Spain, indicates that Neanderthal children actually grew at a similar rate to modern humans. Researchers were able to examine dental, cranial, and postcranial material, allowing the assessment of dental and skeletal maturation with age. In fact the main difference between Neandertals and modern humans was reported in the vertebral column. Several features also indicated ongoing brain growth. It was observed that the pattern of vertebral maturation and extended brain growth might reflect the broad Neanderthal body form and physiology, rather than a fundamental difference in the overall pace of growth in Neanderthals compared to modern humans. |
The present invention relates to x-rays and, more specifically, to X-ray focussing using a refractive X-ray arrangement. The refractive arrangement for X-rays comprises a member of low-Z material, said part of low-Z material having a first end adapted to receive x-rays emitted from an x-ray source and a second end from which emerge said x-rays received at said first end, and first and second surfaces. The invention also concerns a lens and a method for manufacturing the arrangement.
With the advent of 3rd generation synchrotron x-ray sources, hard x-ray optics is a field of growing interest with applications in research, material testing, chemical analysis and medical imaging and therapy. Prior art focusing elements in this energy region use the methods of reflection and diffraction, e.g. best crystals, curved mirrors, Fresnel zone plates and capillary optics. These elements are generally expensive and technologically challenging to manufacture, limiting their use in commercial-grade applications.
Another shortcoming associated with prior art high-energy x-ray focusing techniques, such prior art attempts are limited to generating a single-peak energy distribution. Hence, such experimental methods are not well suited to applications requiring more than one x-ray energy peak, such as dual-energy x-ray imaging.
It is well known that the refractive index of any material can be expressed by
n=1xe2x88x92xcex4xe2x88x92ixcex2xe2x80x83xe2x80x83(1)
Refractive lenses can easily be fabricated for use in the visible light region, since materials having a refractive index n far from unity and a small absorption in this region are readily available. In contrast, optical elements utilizing refraction are intrinsically difficult to fabricate for use in the x-ray region, since in this energy region, all materials have an index of refraction n near unity and exhibit a large absorption. Consider a concave piece of material having a circular revolution with the radius of curvature R. Such a piece of material will focus a plane-wave entering parallel to the axis at a focal distance of f. The focal length is given by f = R δ ( 2 )
A lens fabricated according to eq. 2 would have a very large focal length, since d is typically 10xe2x88x925 or 10xe2x88x926 in the hard x-ray region. Examples of such lenses were given by Suehiro et al (Nature 352 (1991), pp. 385-386). In a correspondence, this approach was ruled out for any practical application by Michette (Nature 353 (1991), p. 510). The extent to which the focal length can be shortened by reducing R has limitations in terms of fabrication technology and practical use.
A significant improvement was achieved when Snigirev et at (Nature 384 (1996), pp. 49-51) cascaded N drilled holes in a piece of aluminum. This corresponds to 2N concave surfaces, thereby reducing the focal length by the same factor. The total focal length of the compound lens is given by F = f 2 N = R 2 δ xe2x80x83 N ( 3 )
This lens still suffered from spherical aberration and high absorption and focusing was only achieved in one dimension. These shortcomings have been addressed by several authors. Similar solutions are also known through U.S. Pat. No. 5,594,773 and U.S. Pat. No. 5,684,852.
Low-Z materials have been used for decreased absorption and two-dimensional focusing has been achieved by, e.g. Elleaume Nucl. Instr. and Meth. A 412 (1998), pp. 483-506) by means of crossing two linear arrays.
Another lens is described in a U.S.A Patent Application entitled xe2x80x9cA COMPOUND REFRACTIVE X-RAY LENSxe2x80x9d, now U.S. Pat. No. 6,091,798, which discloses a novel manufacturing technique to make parabolic profiles by splitting the lens in two halves at the symmetry axis, thereby reducing spherical aberration and absorption.
However, aberration free compound reflective x-ray lenses still rely on elaborate and expensive manufacturing techniques. Hence, such refractive lenses are not well suited to commercial-grade applications. Furthermore, such prior art refractive x-ray lenses are limited to generating a single-peak energy distribution. As yet another disadvantage, prior art refractive x-ray lenses have, for a given energy, a fixed focal length, which cannot be varied.
Thus, a need exists for a refractive x-ray lens, which is well suited for commercial applications and which does not suffer from the disadvantageous inherited by the known lense. Still another need exists for a refractive x-ray lens, which is able to generate a dual energy distribution from an x-ray source. Yet another need exists for a refractive x-ray lens for which the focal length for a given energy can easily be varied. Still, another need exists for a high-energy x-ray leas able to generate a dual energy distribution from a broadband x-ray source.
A further need exists for a method readily to form a refractive x-ray lens at a low cost, e.g. so that high-energy x-ray optics should find its way from specialized research facilities into general applications in industry and commercial RandD.
The present invention provides an x-ray lens which is well suited for commercial applications. The present invention further provides a method readily to form a compound refractive x-ray lens. The present invention also provides a refractive x-ray lens able to generate a dual-energy distribution from a broad energy x-ray source. Furthermore, the present invention provides an x-ray lens for which the focal length for a given energy can easily be varied. The present invention achieves the above accomplishments with a novel x-ray focusing apparatus, novel x-ray lens formation methods and novel methods for focusing of x-rays.
Moreover, the present invention has as an objective to increase the flux on a scanned slit. For these reasons, the initially mentioned refractive arrangement for X-rays further comprises a plurality of substantially sawtooth formed grooves disposed between said first and second ends on at least one of said first or second surfaces. Said plurality of grooves oriented such that said x-rays which are received at said first end, pass through said member of low-Z material and said plurality of grooves, and emerge from said second end, are refracted to a focal point.
Preferably, said member of low-Z material consists of a plastic material, specially one of from the group comprising polymethylmethacrylate, vinyl and PVC. It may also consist of beryllium.
Preferably, said grooves have the form of sawteeth with substantially straight cuts.
In an advantageous embodiment said pluralities of grooves have varying sizes, decreasing or increasing continuously from said first end towards said second end.
The refractive X-ray lens according to the invention comprises a volume of low-Z material, said volume having a first end adapted to receive x-rays emitted from an x-ray source and a second end from which emerge said x-rays received at said first end and first and second surfaces. The volume further comprises a plurality of substantially sawtooth formed grooves disposed between said first and second ends on at least one of said at least two surface, said plurality of grooves oriented such that said x-rays which are received at said first end, pass through said volume of low-Z material and said plurality of grooves, and emerge from said second end, are refracted to a focal point.
In one advantageous embodiment the lens comprises two volumes arranged such that the surfaces with the plurality of grooves are facing each other. Preferably, said two volumes each have a tilt angle to an optical axis of said X-ray. Said volumes have non-coincident focal points.
Preferably, a focal length of each of the two volumes of the lens is varied by separately varying each tilt angle.
Said volume of low-Z material consists of a plastic material, specially one from the group comprising polymethylmethacrylate, vinyl and PVC or said volume of low-Z material consists of beryllium.
Moreover, the invention concerns an X-ray system and a method for two-dimensional focusing of X-rays and including at least two leases according to above. The focusing is obtained by arranging said at least two lenses, such that each x-ray traverses both of lenses in sequence and that one of said at least two lenses are rotated around an optical axis with respect to the other lens.
In one preferred application said refractive lens is coupled to at least one second commercial-grade compound refractive x-ray lens such that an array of compound refractive x-ray lenses is formed.
The method of fabricating the saw-tooth profile refractive x-ray lens is characterized by: transferring shapes of grooves onto a carrier by means of an engraving arrangement producing a master, and using said master to pressing grooves on a suitable material. |
Does Obama have the guts for a full-frontal confrontation with the Israel lobby?
The Israel lobby is mobilizing for what might turn into the most significant confrontation between the United States and Israel since, well, the Suez War of 1956, when President Eisenhower told Israel — and its covert allies, the UK and France — to halt the unprovoked assault on Egypt. Since then, US-Israel conflicts have been relatively small and tied to side issues, such as the fight over President Reagan’s sale of AWACS surveillance aircraft to Saudi Arabia in the early 1980s or President Bush’s showdown with Israel in the early 1990s, when the United States threatened to withhold loan guarantees to Israel after a right-wing Israeli government stone-walled the peace process.
This time, if President Obama plays his cards right, he could bring down the extremist government of Bibi Netanyahu. But that depends on whether Obama displays the guts and gumption necessary for a full-frontal challenge to the American Israel Public Affairs Committee and its allies.
In a piece written for Mother Jones last year, I outlined the vulnerability of AIPAC et al. to a direct challenge from Obama, especially with the emergence of J Street, the “pro-Israeli, pro-peace” Jewish lobby.
A year ago, it seemed possible that Obama was headed in that direction. He’d nominated the even-handed George Mitchell as his Israel-Palestine special representative, to the discomfort of AIPAC. He’d installed a number of aides at the White House, including General Jones, Mara Rudman, and others who had sympathies with the Palestinians and with the Israeli pro-peace camp. Obama launched a major effort to rebuild US ties with the Muslim world, including his June speech in Cairo, that all but required a stronger US effort to force concessions from Israel. And he’d ordered a showdown with Israel over its illegal settlements in occupied Palestinian lands, demanding outright that Israel stop building them.
Nearly all of that collapsed. Mitchell got nowhere. Netanyahu bluntly rejected the settlements demand, kept building them, and faced no consequences. And, worst of all, Obama utterly failed to put forward an American peace plan to restart the talks. What was needed then, and now, is for Obama to outline what a final settlement of the conflict will look like: a return to the 1967 borders (with some land swaps), the division of Jerusalem, the removal of Israeli encampments from the West Bank, a sovereign Palestinian state, a deal over the Palestinians’ right to return to their land (including a Saudi- and Gulf-financed compensation package), and probably some sort of US security guarantees for Israel.
Obama didn’t deliver. He never stated the end goal. Now, he has another chance. His new opportunity was handed to him last week when Netanyahu’s government slapped visiting Vice President Biden in face by announcing, during a high-stakes, delicate trip, a plan to build 1,600 new Jewish homes in occupied East Jerusalem. In the aftermath of that event, the entire Obama administration has been mobilized against Israel. The key question is not whether Obama and Co. will slam Israel rhetorically, as they’ve done, buy whether there will be concrete consequences for Israel and whether the Obama team will finally relaunch the all-but-dead peace process by declaring the president’s own vision of the terms that Israel, the Palestinians, and the Arab states must agree to.
“We also hope that if progress lags, the administration will be ready to put forward its own proposals on the central issues of borders, refugees, security and the future of Jerusalem.
Netanyahu, while faking an apology, insists — as does his entire right-wing regime — that it won’t change policy or back down.
Underlying all this is not just the reaction to an insulting announcement during the visit of Vice President Biden. Instead, at a more fundamental level, the Obama administration is beginning to realize that Israeli intransigence — and the Netanyahu government, in particular — is a major obstacle to US policy in the region, from Iraq to Iran to the struggle against Al Qaeda. It still remains to be seen if the White House the courage to do anything about it. In 2009, it didn’t. But this is 2010.
Tomorrow: the strategic underpinnings of Obama’s unease with the Israelis. |
<reponame>parkma99/cs_study_plan
import argparse
import json
import os
from difflib import unified_diff
import local_server
import log
from formatter import prettify
def reformat_files(src, dest=None, check=False):
if dest is None:
dest = src
with open(src) as src:
original = src.read()
formatted = prettify([original]) + "\n"
if check:
if original != formatted:
print("\n".join(unified_diff(original.splitlines(), formatted.splitlines(), fromfile="Original", tofile="Formatted")))
exit(1)
with open(dest, "w") as dest:
dest.write(formatted)
exit()
parser = argparse.ArgumentParser(description="CS61A Scheme Editor - Spring 2021")
parser.add_argument("-f", "--files",
type=argparse.FileType('r+'),
help="Scheme files to test",
metavar="FILE",
nargs='*')
parser.add_argument("-nb", "--nobrowser",
help="Do not open a new browser window.",
action="store_true")
parser.add_argument("-n", "--no-dotted",
help="Disable dotted lists",
action="store_true")
parser.add_argument("-p", "--port",
type=int,
default=31415,
help="Choose the port to access the editor")
parser.add_argument("-r", "--reformat",
type=str,
nargs="*",
help="Reformats file and writes to second argument, if exists, or in-place, otherwise.",
metavar='FILE')
parser.add_argument("-c", "--check",
help="Only check if formatting is correct, do not update.",
action="store_true")
args = parser.parse_args()
if args.reformat is not None:
reformat_files(*args.reformat, check=args.check)
log.logger.dotted = not args.no_dotted
configs = [f for f in os.listdir(os.curdir) if f.endswith(".ok")]
if args.files is not None:
file_names = [os.path.basename(file.name) for file in args.files]
for file in args.files:
file.close()
else:
file_names = []
if len(configs) > 1:
parser.error("Multiple okpy configs detected, files to be tested must be specified explicitly.")
elif len(configs) > 0:
with open(configs[0]) as f:
file_names = [name for name in json.loads(f.read())["src"] if name.endswith(".scm")]
local_server.start(file_names, args.port, not args.nobrowser)
|
Q:
Do bedbugs spread disease?
The CDC (the US Centers for Disease Control and Prevention) asserts that:
Bed bugs should not be considered as a medical or public health hazard. Bed bugs are not known to spread disease.
Can the risk of disease transmission be categorically ruled out, considering that, after all, bed bugs feed on people's and animals' blood?
A:
Can the risk of disease transmission be categorically ruled out, considering that, after all, bedbugs feed on people's and animals' blood?
No. More research is needed before such a statement could be made.
As it stands now, despite investigations of transmissibility of numerous infectious agents, including transmissible blood-borne pathogens such as HIV and hepatitis B and C viruses, to our knowledge, no conclusive evidence has demonstrated disease transmission by bedbugs [1][2]
However, there are some reasons for concern regarding the possibility of bedbugs being a vector for drug-resistant bacteria, or commensal bacteria that are themselves vectors.
Three residents of an impoverished community in Vancouver were hospitalized, and found to be infested with bedbugs. The bedbugs were tested for the presence of drug-resistant bacteria, and bedbugs from each of the three patients were found to be carriers:
For 2 patients, VRE was isolated from 1 bedbug each. These bacterial isolates were also resistant to ampicillin, teicoplanin, and aminoglycosides but susceptible to linezolid, quinupristin/dalfopristin, and tetracycline. For 1 other patient, MRSA was isolated from 3 bedbugs.
The conclusions drawn from the incident are:
Bedbugs carrying MRSA and/or VRE may have the potential to act as vectors for transmission. Further studies are needed to characterize the association between S. aureus and bedbugs. Bedbug carriage of MRSA, and the portal of entry provided through feeding, suggests a plausible potential mechanism for passive transmission of bacteria during a blood meal. Because of the insect’s ability to compromise the skin integrity of its host, and the propensity for S. aureus to invade damaged skin, bedbugs may serve to amplify MRSA infections in impoverished urban communities.
Additionally, a study of an outbreak of bedbugs on French warships in the Mediterranean found that 13 of the 18 insects collected carried bacteria of the genus Wolbachia, which is suspected as a pathogenic vector for hepatitis B and American trypanosomiasis (Chagas disease). Link to the PDF abstract. |
# --------------------------------------------------------------------------------------------
# Copyright (c) Microsoft Corporation. All rights reserved.
# Licensed under the MIT License. See License.txt in the project root for license information.
# --------------------------------------------------------------------------------------------
from azure.cli.core.decorators import Completer
from azure.cli.command_modules.resource._client_factory import (
_resource_policy_client_factory, _resource_client_factory)
@Completer
def get_policy_completion_list(cmd, prefix, namespace, **kwargs): # pylint: disable=unused-argument
policy_client = _resource_policy_client_factory(cmd.cli_ctx)
result = policy_client.policy_definitions.list()
return [i.name for i in result]
@Completer
def get_policy_set_completion_list(cmd, prefix, namespace, **kwargs): # pylint: disable=unused-argument
policy_client = _resource_policy_client_factory(cmd.cli_ctx)
result = policy_client.policy_set_definitions.list()
return [i.name for i in result]
@Completer
def get_policy_assignment_completion_list(cmd, prefix, namespace, **kwargs): # pylint: disable=unused-argument
policy_client = _resource_policy_client_factory(cmd.cli_ctx)
result = policy_client.policy_assignments.list()
return [i.name for i in result]
@Completer
def get_policy_exemption_completion_list(cmd, prefix, namespace, **kwargs): # pylint: disable=unused-argument
policy_client = _resource_policy_client_factory(cmd.cli_ctx)
result = policy_client.policy_exemptions.list()
return [i.name for i in result]
@Completer
def get_providers_completion_list(cmd, prefix, namespace, **kwargs): # pylint: disable=unused-argument
rcf = _resource_client_factory(cmd.cli_ctx)
result = rcf.providers.list()
return [r.namespace for r in result]
@Completer
def get_resource_types_completion_list(cmd, prefix, namespace, **kwargs): # pylint: disable=unused-argument
rcf = _resource_client_factory(cmd.cli_ctx)
result = rcf.providers.list()
types = []
for p in list(result):
for r in p.resource_types:
types.append(p.namespace + '/' + r.resource_type)
return types
|
import random
loginUrls = {
'normal': {
'init': {
'url': r'https://kyfw.12306.cn/otn/login/init',
'method': 'GET',
'headers': {
'Accept': r'text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8',
'Referer': r'https://kyfw.12306.cn/otn/leftTicket/init',
},
'response': 'html',
},
'uamtk': {
'url': r'https://kyfw.12306.cn/passport/web/auth/uamtk',
'method': 'POST',
'headers': {
r'Content-Type': r'application/x-www-form-urlencoded; charset=UTF-8',
'Referer': r'https://kyfw.12306.cn/otn/passport?redirect=/otn/login/userLogin',
}
},
'captcha': {
'url': r'https://kyfw.12306.cn/passport/captcha/captcha-image?login_site=E&module=login&rand=sjrand&{}'
.format(random.random()),
'method': 'GET',
'response': 'binary',
},
'captchaCheck': {
'url': r'https://kyfw.12306.cn/passport/captcha/captcha-check',
'method': 'POST',
'headers': {
'Content-Type': r'application/x-www-form-urlencoded; charset=UTF-8',
'Referer': r'https://kyfw.12306.cn/otn/login/init',
}
},
'login': {
'url': r'https://kyfw.12306.cn/passport/web/login',
'method': 'POST',
'headers': {
'Content-Type': 'application/x-www-form-urlencoded; charset=utf-8',
'X-Requested-With': 'xmlHttpRequest',
'Referer': 'https://kyfw.12306.cn/otn/login/init',
}
},
'userLogin': {
'url': r'https://kyfw.12306.cn/otn/login/userLogin',
'method': 'POST',
'headers': {
'Content-Type': 'application/x-www-form-urlencoded',
'Referer': 'https://kyfw.12306.cn/otn/login/init',
},
'response': 'html',
},
'userLoginRedirect': {
'url': r'https://kyfw.12306.cn/otn/passport?redirect=/otn/login/userLogin',
'method': 'GET',
'response': 'html',
},
'uamauthclient': {
'url': r'https://kyfw.12306.cn/otn/uamauthclient',
'method': 'POST',
'headers': {
'Referer': r'https://kyfw.12306.cn/otn/passport?redirect=/otn/login/userLogin',
}
},
'checkUser': {
'url': r'https://kyfw.12306.cn/otn/login/checkUser',
'method': 'POST',
'headers': {
'Referer': r'https://kyfw.12306.cn/otn/leftTicket/init',
}
},
'loginOut': {
'url': r'https://kyfw.12306.cn/otn/login/loginOut',
'method': 'GET',
'headers': {
'Referer': r'https://kyfw.12306.cn/otn/index/initMy12306',
},
'response': 'html',
},
},
# --------------------------------------------------------------------------------------------------------
'other': {
'init': {
'url': r'https://kyfw.12306.cn/otn/login/init',
'method': 'GET',
'headers': {
'Accept': r'text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8',
r'Content-Type': r'application/x-www-form-urlencoded',
'Referer': r'https://kyfw.12306.cn/otn/leftTicket/init',
},
'response': 'html',
},
'uamtk': {
'url': r'https://kyfw.12306.cn/passport/web/auth/uamtk',
'method': 'POST',
'headers': {
r'Content-Type': r'application/x-www-form-urlencoded; charset=UTF-8',
'Referer': r'https://kyfw.12306.cn/otn/passport?redirect=/otn/login/userLogin',
}
},
'captcha': {
'url': r'https://kyfw.12306.cn/otn/passcodeNew/getPassCodeNew?module=login&rand=sjrand&rand=sjrand&{}'
.format(random.random()),
'method': 'GET',
'response': 'binary',
},
'captchaCheck': {
'url': r'https://kyfw.12306.cn/otn/passcodeNew/checkRandCodeAnsyn',
'method': 'POST',
'headers': {
'Origin': r'https://kyfw.12306.cn',
'Referer': r'https://kyfw.12306.cn/otn/leftTicket/init',
'Content-Type': r'application/x-www-form-urlencoded; charset=UTF-8',
}
},
'login': {
'url': r'https://kyfw.12306.cn/otn/login/loginAysnSuggest',
'method': 'POST',
'headers': {
'Content-Type': 'application/x-www-form-urlencoded; charset=utf-8',
'Origin': r'https://kyfw.12306.cn',
'Referer': r'https://kyfw.12306.cn/otn/leftTicket/init',
}
},
'loginOut': {
'url': r'https://kyfw.12306.cn/otn/login/loginOut',
'method': 'GET',
'headers': {
r'Content-Type': r'application/x-www-form-urlencoded',
'Host': r'kyfw.12306.cn',
'Referer': r'https://kyfw.12306.cn/otn/leftTicket/init',
},
'response': 'html',
},
},
}
autoVerifyUrls = {
'12305':{
'url':'https://kyfw.12306.cn/passport/captcha/captcha-image64?login_site=E&module=login&rand=sjrand&'.format(
random.random()),
'method':'GET'
},
'api':{
'url':'http://60.205.200.159/api',
'method':'POST',
'headers': {
r'Content-Type': r'application/json',
}
},
'img_url':{
'url':'http://check.huochepiao.360.cn/img_vcode',
'method':'POST'
},
'check_url':{
'url':'https://kyfw.12306.cn/passport/captcha/captcha-check',
'method':'GET'
}
}
queryUrls = {
'query': {
'url': r'https://kyfw.12306.cn/otn/leftTicket/query',
'method': 'GET',
'headers': {
'Referer': r'https://kyfw.12306.cn/otn/leftTicket/init',
}
},
}
submitUrls = {
'dc': {
'submitOrderRequest': {
'url': r'https://kyfw.12306.cn/otn/leftTicket/submitOrderRequest',
'method': 'POST',
'headers': {
'Referer': 'https://kyfw.12306.cn/otn/leftTicket/init',
'Content-Type': r'application/x-www-form-urlencoded; charset=UTF-8',
'Host': r'kyfw.12306.cn',
},
},
'getPassengerDTOs': {
'url': r'https://kyfw.12306.cn/otn/confirmPassenger/getPassengerDTOs',
'method': 'POST',
},
'getExtraInfo': {
'url': r'https://kyfw.12306.cn/otn/confirmPassenger/initDc',
'method': 'GET',
'response': 'html',
},
'checkOrderInfo': {
'url': r'https://kyfw.12306.cn/otn/confirmPassenger/checkOrderInfo',
'method': 'POST',
'headers': {
'Referer': r'https://kyfw.12306.cn/otn/confirmPassenger/initDc',
},
},
'getQueueCount': {
'url': r'https://kyfw.12306.cn/otn/confirmPassenger/getQueueCount',
'method': 'POST',
'headers': {
'Referer': r'https://kyfw.12306.cn/otn/confirmPassenger/initDc',
},
},
'confirmForQueue': {
'url': r'https://kyfw.12306.cn/otn/confirmPassenger/confirmSingleForQueue',
'method': 'POST',
'headers': {
'Referer': r'https://kyfw.12306.cn/otn/confirmPassenger/initDc',
'Content-Type': 'application/x-www-form-urlencoded; charset=UTF-8',
},
},
'queryOrderWaitTime': {
'url': r'https://kyfw.12306.cn/otn/confirmPassenger/queryOrderWaitTime',
'method': 'GET',
'headers': {
'Referer': r'https://kyfw.12306.cn/otn/confirmPassenger/initDc',
},
},
'resultOrderForQueue': {
'url': r'https://kyfw.12306.cn/otn/confirmPassenger/resultOrderForDcQueue',
'method': 'POST',
'headers': {
'Referer': r'https://kyfw.12306.cn/otn/confirmPassenger/initDc',
},
},
'queryMyOrderNoComplete': {
'url': r'https://kyfw.12306.cn/otn/queryOrder/queryMyOrderNoComplete',
'method': 'POST',
'headers': {
'Referer': r'https://kyfw.12306.cn/otn/queryOrder/initNoComplete',
},
}
},
'wc': {
'submitOrderRequest': {
'url': r'https://kyfw.12306.cn/otn/leftTicket/submitOrderRequest',
'method': 'POST',
'headers': {
'Referer': 'https://kyfw.12306.cn/otn/leftTicket/init',
'Content-Type': r'application/x-www-form-urlencoded; charset=UTF-8',
'Host': r'kyfw.12306.cn',
},
},
'getPassengerDTOs': {
'url': r'https://kyfw.12306.cn/otn/confirmPassenger/getPassengerDTOs',
'method': 'POST',
},
'getExtraInfo': {
'url': r'https://kyfw.12306.cn/otn/confirmPassenger/initWc',
'method': 'GET',
'response': 'html',
},
'checkOrderInfo': {
'url': r'https://kyfw.12306.cn/otn/confirmPassenger/checkOrderInfo',
'method': 'POST',
'headers': {
'Referer': r'https://kyfw.12306.cn/otn/confirmPassenger/initWc',
},
},
'getQueueCount': {
'url': r'https://kyfw.12306.cn/otn/confirmPassenger/getQueueCount',
'method': 'POST',
'headers': {
'Referer': r'https://kyfw.12306.cn/otn/confirmPassenger/initWc',
},
},
'confirmForQueue': {
'url': r'https://kyfw.12306.cn/otn/confirmPassenger/confirmGoForQueue',
'method': 'POST',
'headers': {
'Referer': r'https://kyfw.12306.cn/otn/confirmPassenger/initWc',
'Content-Type': 'application/x-www-form-urlencoded; charset=UTF-8',
},
},
'queryOrderWaitTime': {
'url': r'https://kyfw.12306.cn/otn/confirmPassenger/queryOrderWaitTime',
'method': 'GET',
'headers': {
'Referer': r'https://kyfw.12306.cn/otn/confirmPassenger/initWc',
},
},
'resultOrderForQueue': {
'url': r'https://kyfw.12306.cn/otn/confirmPassenger/resultOrderForWcQueue',
'method': 'POST',
'headers': {
'Referer': r'https://kyfw.12306.cn/otn/confirmPassenger/initWc',
},
},
'queryMyOrderNoComplete': {
'url': r'https://kyfw.12306.cn/otn/queryOrder/queryMyOrderNoComplete',
'method': 'POST',
'headers': {
'Referer': r'https://kyfw.12306.cn/otn/queryOrder/initNoComplete',
},
}
}
}
|
Use of percutaneous transpedicular external fixation pins to measure intervertebral motion. STUDY DESIGN Direct measurement of intervertebral motion was compared to motion determined by measuring the position of the exposed ends of the external fixation pins. OBJECTIVES To verify the accuracy of this technique, so that this protocol can be used to study intervertebral motion in the clinical setting. SUMMARY OF BACKGROUND DATA The transpedicular external fixation test has been shown to be a test that can predict the outcome of spinal fusion. In patients who are candidates for this test, intervertebral motion can be calculated from motion at the external ends of these pins. METHODS Six fresh cadaveric spinal segments from L2 to L5 were instrumented with titanium Schanz screws. Reflective markers were placed on the tips of the pins, and intervertebral motion was measured using a noncontacting camera system. Computed tomography data were used to determine the position of the vertebra relative to the reflective markers. Intervertebral distances were calculated and compared with direct measurements obtained using a three-dimensional digitizing arm. RESULTS There was an excellent correlation (r2 = 0.931) between the directly measured intervertebral motions and those that were indirectly calculated from measurements of motion at the end of the Schanz screws. CONCLUSIONS Intervertebral motion can be measured by monitoring motion of the ends of transpedicular external fixation pins. Motion of anatomic landmarks on the vertebrae can be calculated from the pin end's motion if computed tomography data are used to determine the geometric relation between the vertebrae and the external fixation pins. This validation study supports the use of this method in clinical investigations of intervertebral motion in patients with low back pain and external fixation. |
One of the greatest lines I have heard in a long time.
Yes, folks, the acorn doesnt fall far from the tree.
The more I think about it, the better I like it. So send along those unbelievable statements to me. Better still if you can provide documentation of the statement.
Before I announce my choice for the best of the banned words, here are a couple of links. The first is of a book review in Sundays New York Times that I suspect may become a hot topic. In his book The Intimate World of Abraham Lincoln, C.A. Tripp suggests that arguably our greatest president may have been gay. Dont see any controversy here, do you?
Each adopted soldier receives a baggie once a month with goodies like toothpaste, paper, candy, potato chips, etc. These items help raise morale and make it a little easier to live in the middle of a desert. Currently, Operation Interdependence has launched Operation Valentine. They are looking for Valentines to send to the troops so they know we havent forgotten them. Homemade, store-bought, doesnt matter. The soldier doesnt care. I know there are tons of worthy organizations out there, but OI really has its act together. They send out hundreds of thousands of c-rats (civilian rations) a year, all donated by folks like you and me. To find out more, go to their Web site at www.oidelivers.org.
So there you go, in case you want to help. Normally, I dont promote like this. But as I said last week, we cant forget the men and women overseas. It makes the stupid stuff going on back home seem even more stupid.
And I cant forget to announce what I have judged the word or phrase that most deserves to be banned. First of all, I have posted your responses on our Web site. Click here to read them. I hope you have some time to devote to the task. This was a bear to edit Sunday. I have to tell you, a few times I uttered the higher powers name after church.
Believe me, a number of words and phrases deserved this honor: At the end of the day.
Rightsizing. Think outside the box. And, of course, impact as a verb.
But after vigorous thought, I have awarded top honors to the phrase human capital. It is that rare phrase in that it is vague, annoying, meaningless, soulless and dehumanizing. By the way, someone in human resources suggested it. At the risk of bringing wrath upon myself for using a suggested banned phrase, you go girl!
Again, thank you for all your best-in-breed solutions to the English aftermarket. |
Earlier on CNN New Day, Cuomo spoke with Connecticut Senator Richard Blumenthal, and they discussed how Supreme Court nominee Neil Gorsuch was not happy with Trump’s recent slams against a federal judge. Gorsuch’s remarks were confirmed by his spokesman but that didn’t stop Trump from heading to Twitter to accuse Blumenthal of misrepresenting Gorsuch’s statements and his war record.
Chris Cuomo, in his interview with Sen. Blumenthal, never asked him about his long-term lie about his brave “service” in Vietnam. FAKE NEWS!
During a discussion with David Gregory, Cuomo took notice of this, and he immediately proved that he did bring up Blumenthal’s previous misrepresentation. Cuomo went on to say that Trump is “once again off on the facts” and is engaging his tendency to double down whenever he’s proven wrong.
As the conversation continued, Cuomo said that due to Trump’s accusation against him personally, Cuomo had no other choice but to call out the president for distorting the record.
“When he intentionally and deceptively misrepresents what happens on the show and calls me out in doing so, he kind of forces the hand of the show,” Cuomo said.
@realDonaldTrump . @ChrisCuomo did address that point at the start of his interview. https://t.co/JWJEAshv1y Those are the facts. |
The exploration of transform leadership and organizational performance Two mediators' model The development of technology never stops. High-tech industries such as IC, DRAM, or networking have become one of the most important industries in Taiwan. High-tech industry is a knowledge-intensive industry, so the methods to transfer information and experience to knowledge become more important. Using knowledge to develop innovation and performance also relate to the survival of organizations. However, everyone knows the importance of knowledge and innovation, but plenty of organizations couldn't exploit knowledge to create innovation. Leadership is one of key factor because leadership could affect the future of a company. This study conducted an empirical research targeted the high-tech industry in Taiwan and explores the relationship of leadership, knowledge sharing, organizational innovation, and organization performance. This study used questionnaires to collect data then used SEM to verify hypotheses, and the number of valid questionnaires is 186. Finally this study found out that transform leadership would positively affect the level of knowledge sharing, organizational innovation, and organization performance. Also knowledge sharing would positively affect the level of organizational innovation and organization performance. Knowledge sharing as a mediator, Transform leadership would affect organizational innovation; however, it wouldn't affect organization performance. |
package recursion;
import java.util.ArrayList;
import java.util.Collections;
import java.util.List;
public class CombinationsEqualToSum {
// Generate All Combinations With Sum Equal to Target
//
// Given an integer array, generate all the unique combinations of the array numbers that sum up to a given target value
//
// Example One
// Input: [1, 2, 3],
// Output: [ [1, 2], [3] ]
// Example Two
// Input: [1, 1, 1, 1],
// Output: [ [1, 1]
public static void main(String[] args) {
List<Integer> arr = new ArrayList<>();
arr.add(1);
arr.add(2);
arr.add(3);
arr.add(4);
arr.add(6);
generate_all_combinations(arr, 8);
//forEach(li -> li.forEach(System.out::print));
}
// Complete the function below.
public static List<List<Integer>> generate_all_combinations(List<Integer> arr, int target) {
List<List<Integer>> results = new ArrayList<>();
Collections.sort(arr);
helper(results, arr, target, 0, new ArrayList<>(), 0);
int sums = arr.stream().mapToInt(i -> i).sum();
return results;
}
public static void helper(List<List<Integer>> results, List<Integer> arr, int target, int index, List<Integer> sum, int sums){
if (sums == target){
sum.forEach(System.out::print);
System.out.println();
results.add(new ArrayList<>(sum));
return;
}
for(int i = index; i < arr.size(); i++){
sum.add(arr.get(i));
helper(results, arr, target, i + 1, sum, sums + arr.get(i));
sum.remove(sum.size() -1);
}
}
}
|
<filename>central/src/main/java/com/github/rinde/rinsim/central/arrays/SingleVehicleArraysSolver.java
/*
* Copyright (C) 2011-2016 <NAME>, iMinds-DistriNet, KU Leuven
*
* Licensed under the Apache License, Version 2.0 (the "License");
* you may not use this file except in compliance with the License.
* You may obtain a copy of the License at
*
* http://www.apache.org/licenses/LICENSE-2.0
*
* Unless required by applicable law or agreed to in writing, software
* distributed under the License is distributed on an "AS IS" BASIS,
* WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
* See the License for the specific language governing permissions and
* limitations under the License.
*/
package com.github.rinde.rinsim.central.arrays;
import javax.annotation.Nullable;
/**
* Interface for solvers for the single vehicle pickup-and-delivery problem with
* time windows (SPDPTW). This interface uses <code>int</code> arrays for
* specification of the inputs and outputs.
* <p>
* <b>Note that usage of this interface is not recommended.</b> The
* {@link com.github.rinde.rinsim.central.Solver} interface provides exactly the
* same functionality but in a type safe manner.
* @author <NAME>
*/
public interface SingleVehicleArraysSolver {
/**
* Gives a solution for the single vehicle PDPTW as specified by the
* parameters. The returned solution does not necessarily need to be optimal
* but it needs to be feasible. The {@link ArraysSolverValidator} can check
* whether a {@link SingleVehicleArraysSolver} produces a valid solution and
* it can check whether the parameters for the
* {@link SingleVehicleArraysSolver} are valid.
* <p>
* All times are in units relative to the current time (0). All constraints
* are soft, i.e. lateness at service locations and at depot are allowed. The
* start location has index 0, the end location (depot) has index n-1.
*
* @param travelTime <code>n x n</code> distance matrix expressed in time:
* <code>travelTime[i][j]</code> specifies travelTime from location
* <code>i</code> to location <code>j</code>.
* @param releaseDates specifies the left side of the time window for every
* location (hard constraint, earlier is not allowed).
* @param dueDates specifies the right side of the time window for every
* location (soft constraint, lateness is allowed).
* @param servicePairs <code>n x 2</code> matrix of service location pairs,
* <code>servicePairs[i][0]</code> and
* <code>servicePairs[i][1]</code> specify the pickup and delivery
* location respectively. Each location may occur at maximum once in
* the matrix (either as an pickup or as a delivery).
* @param serviceTimes specifies the service time for all locations (both
* pickups and deliveries).
* @param currentSolution If defined it contains the current route of the
* vehicle. This can be used as a starting point for a new solution.
* If any new parcels have become known since this current solution
* was computed these parcels will <i>not</i> be part of the
* solutions. This means that these solutions may not be feasible
* solutions and thus require adaptation.
* @return The solution object which indicates a (usually the best found)
* solution for the single vehicle PDPTW.
*/
SolutionObject solve(int[][] travelTime, int[] releaseDates, int[] dueDates,
int[][] servicePairs, int[] serviceTimes,
@Nullable SolutionObject currentSolution);
}
|
<reponame>nathanmullenax83/rhizome<gh_stars>1-10
#ifndef RHIZOME_PARSE_PLUS_CLOSURE_HPP
#define RHIZOME_PARSE_PLUS_CLOSURE_HPP
#include "gramex.hpp"
namespace rhizome {
namespace parse {
class PlusClosure: public Gramex {
private:
Gramex *inner;
public:
PlusClosure( Gramex *inner );
virtual ~PlusClosure();
virtual bool can_match( ILexer *lexer, GrammarFn lookup ) const override;
virtual void match( ILexer *lexer, GrammarFn lookup, stringstream &captured) override;
virtual Gramex * clone_gramex(bool withmatches) const;
virtual void serialize_to(size_t level,ostream &out) const override;
virtual string rhizome_type() const override;
virtual bool has_interface( string const &name ) override;
virtual Thing * invoke( Thing *context, string const &method, Thing *arg ) override;
virtual bool accepts(GrammarFn lookup) const override;
};
}
}
#endif
|
Red Bull Pool Party: 1 p.m. at Seminole Hard Rock Hotel & Casino. NFL stars Reggie Bush and Devin Hester and celebrity friends gather for an invitation-only pool party, with Dash runway fashion show over the Seminole Hard Rock Hotel pool and a special appearance by T-Pain.
Jamie Foxx party: 10 p.m. at Passion Nightclub. Academy Award-winning actor and comedian/musician Jamie Foxx's party has become a Super Bowl week staple and this year's event will mix a little Hollywood pizzazz with Hard Rock style. There will be a red carpet prior to the event in front of Passion Nightclub. Info: Passionnightclub.com, 954-321-3443.
Taste of the Game VIP Cocktail Reception: 6-9 p.m., Biscayne Lady yacht, docked at Epic Hotel, 270 Biscayne Blvd., Miami. Honors John Wooten of the Fritz Pollard Alliance; establishes scholarship award. Guests include NFL stars Michael Boley and DeShaun Foster, ex-NFLer Willie Gault and actress Vivica Fox. Tickets: $150. Info: Tasteofthegamemiami.com.
Pepsi Super Bowl Fan Jam: Rihanna, Timbaland and Justin Bieber are scheduled to perform. Gates open 5 p.m., show begins 7 p.m. at Eighth Street & Ocean Drive, Miami Beach. Actor Kevin Dillon, star of HBO series "Entourage," and TV anchor Nancy O'Dell will host. NFL players also will participate. Free tickets will be available for a nominal surcharge at Ticketmaster. Live broadcast 9 p.m. on VH1. Info: NFL.com/fanjam.
Eats Beats and Cleats Gridiron Festival: All weekend on Lincoln Road: Some 75 current and former NFL All Stars and other sports legends, celebrity chefs, sports exhibit and film festival. Friday: Gridiron Greats Night of Champions. Sunday: Chalk Talk/Coaches Corner with Mike Ditka; Ultimate Tailgate Party. Daily tickets $85. VIP All Access Passport Holders' kickoff party 9 p.m.-midnight Thursday at Ritz-Carlton, 1 Lincoln Road, Miami Beach. Prices start at $350 (also include VIP Festival Tent, film screenings, premium merchandise and memorabilia). Call 877-733-3430 or visit Ebcmiami.com.
The Tide Mile of Clean Style: 11 a.m.-9 p.m. Thursday through Saturday on Ocean Drive between Seventh and 10th streets, Miami Beach. Interactive experience: "Tide Everyday Runway," where you can make a style statement, show off your own personal style and get your photo taken; "Apparel Creation Station" where you can help custom design your own T-shirt; visit the Tide Loads of Hope truck and purchase a Loads of Hope vintage tee to help support disaster relief efforts in Haiti; get clothing care tips from experts, while inputting your own stain-fighting solution into Tide's new iPhone app, the Tide Stain Brain; take home Tide products. Stylist Jorge RamM-sn will meet and greet noon-4 p.m. Thursday and Saturday to discuss style trends and must-have fashion. For information, call 212-891-0486.
Jordin Sparks Experience: The Red, White & Black After Party: Eden Roc Renaissance, 4525 Collins Ave., Miami Beach. Private pool and after-party room open at 7 p.m. with DJ Cedric Ceballos, formerly of the Heat. Jordin and friends will take the mic throughout the evening. Tickets are $100. Info: Jordinsparksexperience.com.
Pepsi Musica Super Bowl Fan Jam: Nelly Furtado, Paulina Rubio and Pitbull perform. Gates open 5 p.m., show begins 7 p.m. at Eighth Street and Ocean Drive, Miami Beach. Telemundo stars Leti Coo and Jessi Losada, with actor Karim Mendiburu, will host. NFL players also will participate. Free tickets will be available for a nominal surcharge at Ticketmaster. Taping will be aired at 4:30 p.m. Saturday on Telemundo. Info: NFL.com/fanjam.
Hard Rock International's "Rock 'N Soul" Party: 9 p.m. at Hard Rock. Agent Drew Rosenhaus will be joined by NFL players, including Tommie Harris, Chad Ochocinco, Willis McGahee, Santana Moss, Terrell Owens, Kellen Winslow Jr., Jeremy Shockey, Zach Thomas, Frank Gore, DeSean Jackson and Lance Briggs. A red carpet event will precede the celeb-studded party. VIP packages available. Tickets: $100, $250 for VIP at the Hard Rock Live box office, open Monday-Saturday noon to 7 p.m. and Sunday at noon. Tickets also are available at Ticketmaster outlets, Ticketmaster.com or 800-745-3000. Presented by Hard Rock International and WQAM Sports Radio.
Super Bash 2010: 9 p.m.-4 a.m. at Opium at the Seminole Hard Rock Hotel & Casino. Hosted by Michael "The Playmaker" Irvin. Join the Playmaker and invited guests Dan Marino, Ryan Bader, Deion Sanders, Alex Rodriguez, Will Ferrell, Dominique Wilkins, Rick Ankiel, Ray Lewis, Johnny Damon and more. To reserve tickets, go to SuperBash2010.com. To reserve a limited number of private VIP tables, call 954-327-9094. More info: Opiumhardrock.com.
ESPN The Magazine's Next party: Athlete and celebrity guests dance the night away under a custom-made, 25,000-square-foot, clear-top tent at the Fontainebleau, 4441 Collins Ave., Miami Beach. Special performances by Keri Hilson & Ne-Yo, music by Q-Tip, VIP red carpet reporter rapper Nelly. Also: Jennifer Love Hewitt, Laurence Fishburne, Mark Sanchez (Jets), Matt Kemp (Dodgers), Brandon Jacobs (Giants), Braylon Edwards (Jets), Brooke Hogan, Dave Annable, Jake Delhomme (Panthers), Jeremy Shockey (Saints), Jerry Rice, Jillian Michaels ("Biggest Loser"), Joumana Kidd (VH1's "Let's Talk About Pep"), Kerry Rhodes (Jets), Kevin Boss (Giants), Lennox Lewis, Shawne Merriman (Chargers), Tim Tebow (UF). Info: 917-913-5744.
NFL Alumni Player of the Year Awards Dinner: 6-10 p.m. at Westin Diplomat Resort & Spa, 3555 S. Ocean Drive, Hollywood. The event honors the top offensive, defensive and special teams players, as well as the coach of the year. Information: 800-878-5437, ext. 212. |
The New York Police Department used undercover cops to gain intimate access to the organizing core of the city's Black Lives Matter activists in 2014 and 2015, revealing to police protesters' plans and trusted communications, new documents show.
The documents, mostly emails between undercover NYPD cops and NYPD officials, were ordered to be released following a February court ruling. The new materials show the extent of surveillance employed by the largest police force in the US against protesters seeking to point out the disproportionate impact of state violence on people of color, especially African-Americans, in New York City.
By embedding cops into Black Lives Matter (BLM) protesters' decision-making operations, the NYPD was able to gain possession of group text exchanges and organizing details that revealed the basic plans of BLM protesters in 2014 and 2015 following the NYPD killing of Eric Garner, an unarmed black man, in July 2014.
One email from an NYPD official shows that that the department was monitoring an NYPD cop who was embedded within a small group of BLM protesters on their way to Grand Central Station. This type of approach allowed the NYPD to understand the group's movements and plans ahead of time.
The new documents, in which all dates were redacted prior to public release, also include pictures and a short video of Grand Central demonstrations. In one photo, an undercover cop identified a person in a brown jacket as the "main protester."
BLM protesters and supporters said the level of access gained by the NYPD amounted to a covertly compromised inner circle of demonstration planners amid a protest movement that was overtly viewed with suspicion, if not outright opposed, by the NYPD and much of the power structure in New York City and across the nation.
Keegan Stephan, an activist and law student involved in Grand Central demonstrations and who has assisted in the effort to obtain the documents, said the new revelations indicate a chilling degree of deception amongst trusted organizers.
Stephan told RT America that the documents further expose undercover infiltration of social movements, a known, "disruptive tactic" within protest policing.
"One problem with this policing occurring in secret, and never being disclosed, even years after the fact, is that it is undemocratic – it is never debated by and approved by the public, so it continues even though most of the public might think it should not," Stephan said in an email.
The documents show that NYPD undercover officers described the protesters as "peaceful,""very quiet," and "orderly," yet continued to surveil them. Stephan said this dichotomy must be at the center of public debate.
"The NYPD, in their own records, called these protests completely peaceful, yet continued to infiltrate them," he said. "I'm hopeful that most of the public does not think the NYPD should be infiltrating completely peaceful, First Amendment activity, and demand that it stops."
An attorney who was part of the lawsuit that triggered the release of the documents said the materials do not indicate a crime had been or was going to be committed, and that NYPD spying was politically motivated.
"There was no law enforcement need for undercover surveillance or infiltration of these protests. This was politically motivated action by the NYPD against a group it considers its political enemy,"said David Thompson, a partner with the firm Stecklow & Thompson, in a news release.
M.J. Williams, a counsel with Stecklow & Thompson, said the court-ordered disclosure was incomplete, suggesting the department is withholding more damning evidence, especially concerning video taken of protests by the NYPD.
"So if NYPD was truthful with the court, then this additional footage exists, but is still being withheld," she said.
The attorneys said they will "continue to pursue the matter until the NYPD obeys the court's order in it entirety."
Based on NYPD's own guidelines, the department cannot begin to investigate constitutionally protected activities unless "facts or circumstances reasonably indicate that an unlawful act has been, is being, or will be committed" and only if surveillance operations are approved by a committee. That committee, the Handschu Authority, was staffed only by NYPD officials at the time, the Guardian reported.
There are loopholes to the intelligence-gathering rules, however, that allow the NYPD to investigate leads and execute "preliminary inquiries," calling into question whether the department's internal surveillance laws actually limit police activity or are simply a matter of the NYPD's own enforcement prerogatives.
Kim Ortiz, an organizer for the activist group NYC Shut It Down, said the NYPD's spying on BLM protesters is par for the course in New York City.
"The constant surveillance is definitely troubling," she said in the news release. "But we know our history, the history of the Black Panthers, and NYPD’s efforts to take them down as well as other political movements that threaten the status quo. But we are not going to stop protesting, not until we force shifts in power that will guarantee my kids will grow up safe."
The freedom of information lawsuit seeking to provide insight into the NYPD's surveillance operations of BLM protests was filed after the NYPD refused to comply with records requests. In response to the lawsuit, the NYPD revealed in September 2016 documents that indicated undercover police officers monitored BLM protests, including Grand Central Station demonstrations. In February, a New York Supreme Court judge ruled that the NYPD had to comply with the records request related to the lawsuit, paving the way for the new disclosures.
Last month, the Stecklow & Thompson attorneys uncovered evidence showing that the NYPD recorded BLM demonstrations and, years earlier, Occupy Wall Street protests hundreds of times without proper authorization. |
// unmarshalConfBytes accepts bytes and unmarshals them using the correct
// format. Either the unmarshaled data or an error is returned.
//
// Supported formats:
// json
// toml
// yaml
func unmarshalConfBytes(f Format, buff []byte) (interface{}, error) {
var ret interface{}
switch f {
case JSON:
err := cjson.Unmarshal(buff, &ret)
if err != nil {
return nil, err
}
return ret, nil
case TOML:
_, err := toml.Decode(string(buff), &ret)
if err != nil {
return nil, err
}
return ret, nil
case YAML:
err := yaml.Unmarshal(buff, &ret)
if err != nil {
return nil, err
}
return ret, nil
default:
return nil, UnsupportedFormatError{f.String()}
}
} |
Thank you for purchasing this Pocket Books eBook.
* * *
Join our mailing list and get updates on new releases, deals, bonus content and other great books from Pocket Books and Simon & Schuster.
CLICK HERE TO SIGN UP
or visit us online to sign up at
eBookNews.SimonandSchuster.com
## Content
Acknowledgments
Prologue
Part I
Chapter One
Chapter Two
Part II
Chapter Three
Chapter Four
Chapter Five
Chapter Six
Chapter Seven
Chapter Eight
Chapter Nine
Chapter Ten
Chapter Eleven
Chapter Twelve
Chapter Thirteen
Chapter Fourteen
Chapter Fifteen
Chapter Sixteen
Chapter Seventeen
Chapter Eighteen
Chapter Nineteen
Chapter Twenty
Chapter Twenty-one
Chapter Twenty-two
Chapter Twenty-three
Chapter Twenty-four
Chapter Twenty-five
Chapter Twenty-six
Chapter Twenty-seven
Chapter Twenty-eight
Chapter Twenty-nine
Chapter Thirty
Chapter Thirty-one
About the Author
##
**ACKNOWLEDGMENTS**
We'd like to thank John Ordover, editor of the A Time To . . . series, for the opportunity to participate in one of these high-profile projects featuring the work of several authors. As readers and fans of Star Trek books long before either of us got the harebrained idea that we could write, we became accustomed to names like David, Friedman, Reeves-Stevens, and Carey as staples for efforts on this scale. That anyone might consider us capable of holding our own at the level established long ago by these fine writers is a reward unto itself.
Thanks also to the other writers involved in this effort: John Vornholt, Robert Greenberger, David Mack, and Keith R.A. DeCandido. Everyone pitched in well beyond the efforts of simply writing their own story, offering insights and advice on one another's manuscripts to make this entire affair a truly collaborative effort.
Last but certainly not least, thanks very much to the many readers who've expressed their enjoyment and appreciation for the stories Kevin and I write. One of the most common questions we ask whenever working on a project is "What would a fan want to see?" That question and the mind-set it evokes influences everything we do, and we hope it shows in the stories that end up in your hands.
##
**Prologue**
**Translated from the personal journal of Hjatyn:**
WRITING IS NOT SOMETHING I have practiced much of in the past, at least in any capacity that did not involve my work, but the crisis that is befalling us compels me to record my feelings and thoughts. I am sure that others, possessing superior education and clarity of thought, are at this very moment recording these events so that future generations might read and reflect on this time in our history. Still, I feel an obligation, almost a compulsion, to do the same.
I know I should report to the school to conduct my scheduled classes, but I am finding it increasingly difficult to remain focused on my responsibilities. With each passing day, those things I once considered important and even enjoyable in life seem to be losing their significance. More than once, I have fought back the growing sensation that I myself am becoming progressively inconsequential.
I am afraid.
My wife, Beeliq, keeps telling me there is nothing to fear, yet with each new day she spends more and more time at the office of the colony administrator. She acts as one of his assistants, which puts her in a position to know if anything was wrong.
What I am no longer sure of is whether she would tell me. Since our earliest days of courtship, she has never kept secrets from me, at least to the best of my knowledge. That she seems to be holding back now only deepens my anxiety. Is it possible she has been ordered to keep information even from her husband?
Still, despite her best efforts, the worry in her eyes is unmistakable.
It is a look that becomes more obvious on those rare occasions that we can share a meal together. Neither of us seems to have an appetite, however, and more often than not the food goes uneaten as we watch the latest news feeds from Dokaal. They seem to be on all the time now, even in our classrooms at the school. With the communications channels overloaded by everyone trying to reach family and friends, the feeds are our only other contact with our homeworld.
At first, the images of destruction were rare, only one or two a season. Certain parts of the world had always suffered from quakes, after all. Such disturbances were given their just due by the media, appearing as part of the daily news broadcasts transmitted to the mining colonies from Dokaal. People worried about loved ones who might be living in affected areas, and memorial services were held on the rare occasions it was learned that relatives had fallen victim to tragedy. There might also be discussion regarding the type and amount of aid the various regional governments might provide, but ultimately, such news was usually forgotten quickly.
Things are different now.
Quakes seem to be erupting every few days at different locations around the world, and the effects seem to be getting worse each time. Barely a week ago, we received the news that the capital city of Wyjaed suffered widespread damage when a quake struck there in the middle of the night. Rescue efforts continue with unrelenting intensity just as they have since the beginning, but hundreds of thousands are feared dead.
Last night's broadcast brought news of the most recent incident. We sat aghast and watched journalists fight back tears as they reported the loss of the entire island nation of Saorquiln, destroyed by tidal forces generated as the result of a massive undersea quake. My friend Rueq and a few others living in our colony had relatives there, and we sat up through the night waiting for any word of survivors. According to the accounts we have seen, it appears that all of the island's inhabitants were lost.
The reports and images, coming from nearly every city now, are perhaps more disturbing because we are helpless to do anything. Out here, among the asteroids, we are days away even with our fastest ships. Besides, what would we do once we got there? Even those with the proper skills and knowledge do not yet seem to know what is happening.
On another of the colonies, the wife of my friend Caesi has been in constant contact with the ministry on Dokaal, but even her position as colony administrator has gained her nothing. No one seems able to explain what the scientists are calling "recurring irregular seismic disruptions beneath the planet's surface." They do not yet know what caused the quakes to begin, why they continue, or whether they will get worse before they finally stop.
One theory that seems to be gaining support in the scientific community is that this is a natural geological phase for the planet. Many scientists are searching for evidence that such an event might have happened long ago, perhaps even before life evolved on our world, but I do not understand how this knowledge will help stop the quakes.
What if they never stop?
More alarming to many is the notion put forth by several prominent spiritual leaders: that this is "the Reckoning." Many religious groups have long felt that our people have been drifting away from the principles Dokaa laid down at the start of our civilization. They believe she is angry at us and that the quakes are a punishment for abandoning our faith in her. Though this specific penalty is not recorded in our people's most sacred texts, the wording is sufficiently cautionary that it is enough to send waves of concern through our more devout people.
As for myself, while I have always attended services with Beeliq, I have never accepted these beliefs with her level of conviction. I know that she is seeking comfort and perhaps forgiveness in Dokaa's embrace, much as she did after her brother died in the mines. Though I did not do so then, part of me wants to join her in prayer now.
The colony administrators are doing their part to keep up a brave front. They repeatedly tell us to go about our lives as best we can, working in the mines or at the various stations supporting the miners and their families. Despite their efforts, the activity is doing little to ease everyone's concerns. My friends and others talk before and after our classes, and I overhear conversations in the Concourse Module when we go to shop or eat. Everyone, everywhere, all across the different colonies, seems to be asking the same question.
What is happening?
##
**2151**
## Chapter One
THOUGH IT WAS NOT UNUSUAL for him to be called to the bridge at such an irregular hour, Captain Vanik was still surprised at the summons. After all, given their current assignment, what could possibly be so pressing?
Located well within the admittedly small sector of the galaxy that had been mapped and traversed by Vulcan ships, this area of space was one Vanik had traveled numerous times during his fifteen years as commander of the Ti'Mur. Other than its status as the location of a single minor conflict during the protracted war with the Andorians, the region offered little of interest. None of the planets in the area's lone star system were habitable, and they contained nothing of scientific or strategic value. The only quality the area possessed, in Vanik's opinion, was that it had few distractions to delay a vessel's journey to some other, more appealing destination.
Has this somehow changed?
He had only just settled into his evening's meditation when the message came from the officer on duty. Well aware of her captain's routine, Sub-commander T'Lih would not have intruded on his private time unless she believed it was a matter for his attention. Whatever it was that had prompted her call, it must be quite fascinating indeed.
Of course, Vanik reminded himself, further speculation serves no purpose. My questions will be answered in short order.
The turbolift slowed to a halt and the doors parted to reveal the Ti'Mur's bridge. Triangular-shaped, the command center was widest at the rear stations, with rows of control consoles to either side and angling inward until they met the immense viewscreen dominating the forward bulk-head. Unlike other areas of the ship, where lighting was adjusted in order to simulate the daily cycle on Vulcan, Vanik preferred the command center's illumination to remain at normal levels regardless of the time of day.
Each of the bridge's key stations was manned despite the lateness of the hour, just as they would be during prime shift, yet the captain also noted a crew member operating the secondary science console. A visual inspection of the weapons station showed that the defensive systems were not active, meaning that no threats to the ship had been detected. Even from across the room, he could hear the two separate conversations taking place between members of the bridge crew and detected nothing untoward being discussed.
Stepping from the turbolift, Vanik nodded in greeting to T'Lih as the subcommander noticed his arrival.
"Good evening, Captain," she offered as she rose from the command chair at the rear of the bridge. Like every other member of the ship's complement, T'Lih wore the standard gray uniform of the Vulcan Space Service. Impeccably tailored to her physique, the uniform possessed no decorative accessories save for the small rank insignia on the left side of her collar. Like Vanik's own, her features were lean and angular, but while his hair was gray and full-bodied, T'Lih wore her black locks cropped close to her skull in a manner that served to highlight the severe upswing of her pointed ears.
"And to you, Sub-commander," Vanik replied. "So, what is it that has attracted your interest?" Rather than take the proffered seat T'Lih had vacated, he chose instead to pace the room's perimeter, walking a slow circuit with hands clasped behind his back as he waited for the subcommander to make her report.
Moving to join her captain, T'Lih replied, "Fifty-two point six minutes ago, our long-range sensors detected an object traveling at warp one point three. A review of our data banks shows that it is of a type and configuration unknown to us."
"Life signs?" Vanik prompted.
"No, Captain. The object appears to be an unmanned drone. It is transmitting a recorded message that repeats at intervals of four point seven minutes. Translation efforts are already under way, and I have also ordered an attempt to determine the drone's origin point based on its current course heading."
Vanik nodded, pleased with the report and the subcommander's initiative, which also logically explained the presence of additional science personnel on the bridge. "Is it close enough for visual inspection?"
By way of reply, T'Lih summoned the attention of the junior officer working at the main science station. "Lieutenant Serel?"
The object that appeared on the bridge's central viewer in response to the science officer's commands was unlike anything Vanik had seen before. It consisted of a bulky cylindrical module mounted above a trio of squat engine bells. The cylinder's outer shell was composed of metal plating, and Vanik could see the join lines as well as the heads of dozens of fasteners that presumably attached the individual plates to a skeletal frame. Two antenna dishes were affixed to the cylinder's flanks, one of which appeared to have suffered damage. In fact, pockmarks and other blemishes were clearly discernible across the surface of the small craft.
"The damage is consistent with the effects of ion storms we have seen on our vessel's hulls," Serel reported from his station. "According to our scans, exposure to such a storm most likely occurred approximately eleven point six years ago."
"What have you learned about its level of technology?" Vanik asked.
"Though we will have to retrieve the drone in order to complete a thorough investigation," the science officer replied, "its propulsion system looks to be quite rudimentary. I would theorize that the warp drive was of an experimental nature, perhaps the first such test made by whoever constructed the object."
Interesting, Vanik thought. Given that the craft was obviously primitive, in all likelihood a first-generation deep-space vessel, that it had survived such an encounter relatively intact and still able to transmit data was a testament to its designers' craftsmanship.
Could this drone be the initial step toward first contact with a new species? Though he had worn the uniform of the Space Service for seventy-six years, he had participated in only one other introduction to an alien race. Vanik had to confess that the opportunity to do so again presented an intriguing notion.
He heard a telltale tone from Serel's console and turned to see the junior officer rising from his chair. "I have a report on the status of our translation efforts, Captain," Serel said as he crossed the bridge to stand before Vanik and T'Lih. "The object has sustained considerable damage during its journey. Much of the message is garbled beyond our ability to decipher. However, I was able to isolate several passages. The people who constructed the drone call themselves the Dokaalan, and the device itself was not launched from their homeworld as part of an exploration initiative. Rather, it seems that the message is a distress call."
Vanik's right eyebrow rose in response. An entire planet calling for help? What could have prompted such a desperate act? "Did the message include a reason for their plea?"
"Yes, Captain," Serel replied. "Their planet was undergoing global seismic events that threatened to destroy it, and science specialists among their people predicted total obliteration within one of their years. Though they had discovered the ability to travel at light speeds, they possessed no space vessels capable of transporting people to another habitable planet. They therefore sent out a trio of unmanned craft in the hopes of contacting someone who could come to their aid."
Already beginning to surmise the likely outcome of this scenario, Vanik was nevertheless obligated to consider what course of action, if any, he could undertake in response to the distress call. "Are we able to determine where the object originated?"
Turning to the secondary science station, T'Lih said, "Sub-commander Taren?"
"According to our sensor scans of its onboard systems," Taren replied, "it appears to have traveled on a constant course at a consistent speed for thirty-eight point three years. This places its likely origin point in an area of space that according to our databases is presently unexplored."
It took little effort for Vanik to comprehend the futility of the Dokaalan's actions. Even if the drone had been able to travel at a faster speed, had its creators not under-stood the improbability of making contact with anyone possessing the resources to render assistance on such a scale? Perhaps they had, and yet the dire situation they faced nevertheless compelled them to make the attempt.
"Given what has already been learned," Vanik said, "and presuming the Dokaalan scientists were correct in their original predictions, it would seem the time to provide assistance has long passed." It was an unfortunate determination to reach, he knew, but the facts currently available to them seemed to support no other conclusion.
"Captain," T'Lih said, "we could deploy a reconnaissance probe back along the drone's original course. It will take several months to reach that area of space at the probe's maximum speed, but it will be able to ascertain what ultimately happened to the Dokaalan homeworld."
It was a logical suggestion, and one Vanik at first supported. However, as this matter involved a species never before encountered, it was an issue that would have to be decided upon by the Vulcan Science Directorate. Only that august body possessed the authority to permit any interaction with a new race, a precaution intended to prevent the accidental introduction of technology, science, or even ideas that might prove too advanced for a culture not yet ready to possess such knowledge.
Besides, the Ti'Mur had other priorities. High Command had instructed Vanik to deviate from its current patrol in order to observe the latest activities of Enterprise, the deep-space exploration vessel recently launched by the humans from Earth. Though the humans themselves held little interest for him, Vanik nevertheless had kept abreast of their progress, especially regarding their efforts to perfect warp travel and push farther away from the confines of their own star system.
It had long been the opinion of High Command that the humans bore watching. Though they had proven to be somewhat innovative in their own way, they had also demonstrated that their inexperience in dealing with a larger celestial community, to say nothing of their own arrogance and overconfidence, likely would be their undoing.
Since Enterprise had left Earth, its crew and particularly its captain had managed to make quite a nuisance of themselves. That much was amply demonstrated when the vessel departed Earth on its inaugural voyage, deep into the heart of the Klingon Empire of all places. Only fortunate happenstance had prevented their initial contact with the Klingons from dissolving into an unmitigated disaster, and Vanik believed that the ultimate ramifications of the haphazard encounter were yet to be realized.
Then there was the recent debacle that had unfolded at the monastery on P'Jem. The Enterprise captain, Archer, had revealed the presence of the top-secret observation facility hidden beneath the monastery to Andorian operatives. Now that station and the vital data it provided about ship movements and other activities within Andorian space was gone, and the damage Archer had inflicted on Vulcan's intelligence-gathering operations would take a long time to repair.
Given all of that, Vanik could understand High Command's wishes that the Earth ship be monitored. He simply did not agree with the dispatching of a Surak-class vessel to do it. He hoped that Enterprise would be able to avoid trouble for the few days until the Ti'Mur was relieved by another vessel.
"Sub-commander T'Lih," he said, "prepare all of the information you have for transmission to High Command. In the interim, divert from our present course long enough to retrieve the drone, then adjust our course and speed to make our appointment on schedule."
"Yes, Captain," T'Lih replied, and set about relaying the necessary orders. As Vanik paced back to his command chair, he watched and listened as his bridge crew turned to their various tasks, satisfied that they would carry out their duties with their usual impeccable efficiency.
Settling into his seat, the captain realized he was actually looking forward to what a full examination of the alien object might reveal. If nothing else, the effort would pass the time until the rendezvous with the Earth ship.
It would be up to High Command and the Science Directorate as to whether a vessel was sent to discover the origin of the alien drone and perhaps to learn what had happened to those who had dispatched it, but Vanik for one hoped the attempt was made. Given the calamity they had apparently suffered, it would be unfortunate if the mystery of the Dokaalan were to remain unsolved.
## Chapter Two
AT ONE TIME, Admiral Forrest could differentiate among the various types of headaches that had always plagued him. There were those caused by stress or muscle tension or too little sleep, for example. Then there was the newer variety of discomfort he experienced on increasingly frequent occasions, invoked whenever he read one of Jonathan Archer's more colorful status reports from the Enterprise.
These days, however, Forrest divided his headaches into only two categories: those caused by Ambassador Soval, and the rest of them; and Soval's score was growing at an exponential rate. Though he didn't have a headache at the moment, Forrest nevertheless mentally added another mark to the list as he walked into his office and saw the Vulcan waiting for him.
The beginning of another wonderful day.
"Good morning, Ambassador," Forrest offered in what he knew to be a vain attempt at pleasantries. "How may I help you today?"
Dressed in his normal ensemble of flowing, earthtoned robes, Soval stood before the admiral's desk with his hands clasped in front of him. Forrest could not be sure, but he thought he saw the Vulcan's jaw clench. Something was definitely annoying the ambassador this morning.
"I understand that Captain Archer has managed to get himself into trouble again," Soval said, "and this time he required the assistance of one of our vessels to extricate himself from his predicament."
Movement outside his window caught Forrest's attention, and he looked up to see a Starfleet shuttlepod flying past. It was ascending into the sky, doubtless on its way to one of the space stations or drydock facilities orbiting Earth. The spaceframe of a new long-range space vessel was being assembled up there right now, he knew, and hundreds of engineers and other specialists were currently hard at work constructing the hundreds of components that would combine to create the next NX-class ship. He was looking forward to tomorrow, when his schedule would permit him the opportunity to go up there and see the status of the formidable project for himself. It certainly was a more appealing prospect than anything listed on his agenda for today.
Is it too late for those guys to come back and pick me up?
There was no way he would retreat from his current guest, of course. A man not easily intimidated, Forrest had long ago learned to handle personalities even haughtier than Soval's. "And Starfleet is extremely grateful, Ambassador. Please pass on my thanks to Captain Vanik and his crew. I also intend to submit a letter of commendation to the Vulcan High Command for their actions." Shrugging, he smiled and added, "I guess it was just good luck that the Ti'Mur was nearby." It was an effort to keep from smiling as he heard Soval exhale, an action on par with a heavy sigh of frustration from a human.
Of course, Forrest knew it was anything but coincidence that the Vulcan vessel had been in the vicinity when two Enterprise officers were trapped on the surface of the comet they had discovered. According to Archer's report, they had been under scrutiny by Vulcan ships for weeks. Though no explanations had been offered, Forrest was certain the directive had come because of Archer's actions on P'Jem.
His exposure of their secret surveillance facility hidden beneath the monastery there had not sat well with the High Command. They had been against the Enterprise's launch and its subsequent long-range exploration mission to begin with, feeling that humanity was not yet ready to venture into the cosmos on its own. That Archer and his crew already had logged a handful of notable mishaps since leaving Earth had only exacerbated the Vulcans' unease. Undoubtedly, they would want to take steps to insure that Archer could not do anything else to interfere in their affairs.
"I have been in the company of humans long enough to recognize sarcasm when I hear it, Admiral," Soval said. "It is one quality of your people I have not yet come to appreciate."
Despite his best effort to remain composed, Forrest could not resist the opening. With a smile he asked, "Ah, so we have other qualities that you do admire?"
There was a moment of silence as Soval appeared to consider the words, and Forrest was sure he saw the ambassador's jaw tighten yet again. I think Archer's right, and Soval has been spending too much time among us lowly humans.
Finally, the Vulcan said, "I do admire your tenacity and desire to expand your horizons, Admiral, as these are commendable goals. My concern, however, and it is one shared by many of my people, is that you refuse to temper such determination with patience. Surely you can admit that your ignorance of the galaxy you inhabit already has been a source of great disruption?"
The compliment, wrapped as it was within the criticism, was still high praise indeed. Forrest knew that the ambassador had spent a great deal of time on Earth in the decades following first contact. He also had been one of the many voices of Vulcan dissent when Zefram Cochrane and Henry Archer had begun work on the Warp 5 project, all while Forrest himself was little more than a wide-eyed teenager contemplating a four-year stint in the navy in order to earn money for college. As Cochrane, along with the elder Archer and hundreds of others, labored to expand the limited warp capabilities of his original Phoenix spacecraft and those efforts began to bear fruit, Soval had been there, always warning that the "humans were too brash and were moving too fast for their own good."
And now this, a grudging accolade for humans from one of their most vocal detractors?
Could Soval actually be mellowing in his middle age?
Wishful thinking, Admiral.
Deploying his best diplomatic charm, Forrest said, "Ambassador, it's true that Jonathan Archer is not the experienced commander one might like to have in charge of the Enterprise. No human possesses such experience, and the only way we're ever going to acquire it is by going out there. Will we make mistakes? I don't doubt it, but in the end I trust Archer's judgment."
"I hope your confidence is not misplaced, Admiral," Soval replied, "and that Captain Archer obtains the experience he seeks before he commits a transgression that does real, lasting damage."
That's the Soval I know and love, Forrest mused.
Attempting to change the subject, the admiral held up the padd his aide had given him. "Since you're here, there is another matter I was hoping we could discuss. Starfleet received word yesterday that the Vulcan Science Directorate has updated its databases, and one item in particular caught my interest."
Though tight-lipped when it came to sharing technology, the Vulcans had been very forthcoming with other information, such as interstellar cartography and navigation. Despite their misgivings about Enterprise's mission, that information exchange had become much more frequent and detailed following the ship's launch.
"This probe that the Ti'Mur discovered," Forrest continued. "Is there a final decision on what to do about it?"
Soval's eyebrow rose in response. Clearly, he had not anticipated this new question. "The Directorate is still examining data collected from the device. Why do you ask?"
Forrest paused, taking a moment to ponder the Golden Gate Bridge, visible across San Francisco Bay. Fog enshrouded most of it, but the view was still clear enough that he could see a lone sailboat navigating the bay as it headed out to sea. A wistful smile curled the corners of the admiral's mouth, and not for the first time he wished it could be him at the wheel of such a tiny vessel.
"It's a fascinating discovery," he said. "I was thinking of sending Enterprise to investigate."
His position at Starfleet naturally precluded Forrest from undertaking any of the long-range missions planned for Enterprise and future NX ships, the next of which would be ready for launch nearly two years from now. The delays and setbacks encountered during the development of the advanced warp program had seen to it that he and his contemporaries would live vicariously through the experiences of younger men like Jonathan Archer, A. G. Robinson, and those who followed such promising leaders into that vast, unknown frontier.
With that in mind, the idea of sending Archer and his crew to learn the fate of the Dokaalan appealed to the admiral. It also seemed to present an opportunity to give the Enterprise a mission unlikely to further irk the Vulcans.
Judging by Soval's reaction, however, that was not an opinion the ambassador shared.
"According to our calculations," Soval replied, "it would take your vessel months to reach the probe's point of origin, even traveling at its maximum speed. Besides, there would be nothing to investigate when they arrived."
Forrest replied, "I know that whatever happened to the Dokaalan was a long time ago. Still, they had the means to launch that probe. What else might they have left behind? Don't you wonder about that, or what finally became of them?" The Vulcan's position seemed a bit simplistic, the admiral decided. There was no telling what kind of artifacts of their civilization the Dokaalan might have left behind. The possibilities were endless.
"Scientists on Vulcan examined all of the information transported within the craft's limited computer storage facility," Soval said. "Using that information to extrapolate a series of computer models, they determined that seismic forces eventually tore the planet apart. Given that conclusion and the Dokaalan's limited technology, it is logical to assume that their civilization was destroyed by whatever cataclysm befell their planet. There would be little use sending your ship, Admiral. That part of the galaxy is still uncharted, and it will be some time before we ourselves undertake any exploration of the region."
Forrest shrugged. "Seems like the perfect reason to go." Speaking the words, he was unable to ignore the various photographs, paintings, and sculptures adorning his office, each of them representing key vessels and moments in naval and Starfleet history. He almost wanted to append the obvious question to what he had already said: Was "going there" not the reason for constructing ships like Enterprise in the first place?
"As we have already discussed," Soval countered, "Captain Archer and his crew seem to have enough difficulty staying out of trouble in this part of the galaxy. There is no point in compounding their work by sending them on a long and arduous mission with nothing to gain."
If he had not known Soval better, Forrest would have sworn he detected the slightest hint of amusement in the ambassador's voice.
Not likely.
Still, the admiral felt compelled to agree with his counterpart. There were countless things for Enterprise to discover right here in their own neck of the woods. Perhaps, one day, when Starfleet had many ships at its disposal, some lucky captain and his or her crew would be able to seek out the ultimate fate of the Dokaalan.
One day . . . .
##
**2378**
## Chapter Three
"I AM ZAHANZEI, first minister to the people of the planet Dokaal. I speak to you as the leader of a people in desperate need of assistance from anyone who might hear this message."
Though he had watched the recording twice already, Jean-Luc Picard once again found himself drawn by Zahanzei's appeal as if seeing it for the first time.
"Catastrophic seismic forces are tearing our world apart, and our most experienced scientists believe that total destruction is inevitable. Our planet is the only one in our solar system capable of sustaining life, and we do not possess the resources to evacuate our people to a suitable world in another system. We have only just recently discovered a means of propulsion that would allow us to complete an interstellar journey, but our level of technology is limited. Our calculations tell us that there is insufficient time to build vessels capable of carrying a sufficient number of our people to safety in order to insure the preservation of our race."
Standing before a window offering a picturesque view of a thriving city, the Dokaalan leader's visage was noble and thoughtful, as would befit a person in his position. Tall and thin, he was humanoid in appearance. His skin, possessing a light blue tinge, was free of any blemishes that Picard could see. Deep maroon eyes peered out from beneath a prominent brow, while only small holes represented where the ears and nose might be on a human's head. Completely devoid of hair, his skull tapered to an almost arrow-shaped chin. Despite his stately bearing, Zahanzei still seemed to possess a vulnerability held only barely in check by the need to carry out the duties of his office for the benefit of those he governed.
"Therefore, I ordered the creation of these three small probes, one of which has traveled to you and carries with it my plea on behalf of my people and my world: Please help us."
As the recording completed and the Enterprise's senior staff turned back to the conference table and each other, Picard knew that already their minds had set to work. He could almost see them ordering their individual lists of responsibilities to support a rescue operation on the scale they believed was coming.
"How soon do we get under way, sir?" asked Commander William Riker from where he sat to Picard's right, giving voice to the concern and determination that was evident on the faces of the others.
As he regarded those faces, however, he felt a twinge of regret, knowing that it fell to him to dash those plans and remind them of the reality of their current lot in life.
"Three weeks ago," Picard said, "the U.S.S. Crazy Horse discovered a small probe of unfamiliar design adrift near the Jeluryn Sector. It had suffered massive damage during its rather lengthy voyage, and engineers aboard the Crazy Horse weren't able to retrieve anything of value from its onboard computer system. What they did discover, however, was that this was not the first object encountered from these people. According to Federation data banks, another such device was encountered by a Vulcan ship more than two centuries ago."
"Two centuries?" said Deanna Troi, seated next to Riker and sporting a confused expression. "We're just now learning about it?"
Picard nodded, resisting the urge to smile at the counselor's confusion. "The Vulcan Science Academy spent several months analyzing data retrieved from the first probe. They concluded that the planetary disaster described by First Minister Zahanzei occurred decades before the first probe's discovery, and well before Starfleet possessed any sort of deep-space exploration capability. The Vulcans advised against sending a ship to investigate, and the matter was closed."
"Earth was taking a lot of advice from the Vulcans in those days," said Lieutenant Commander Geordi La Forge, "but it's hard to believe that anyone in Starfleet could resist the urge to find out where that probe had come from. It sounds like just the mission to give to one of those first long-range ships."
Seated next to La Forge, Lieutenant Commander Data replied, "It was a very active, almost chaotic, period in Earth history, Geordi. With only a single vessel of sufficient capability available for such a task, Starfleet's priorities did not allow for a mission of extended duration at that time. By the time such resources were available, Earth found itself embroiled in conflicts with both the Xindi and the Romulans."
In response to the android's words, Picard could not help but glance to the rear wall of the observation lounge and its array of replicas portraying the lineage of starships named Enterprise dating back more than two centuries. Grimly, he reminded himself that in addition to the promise of peaceful exploration, the replicas also represented decades of conflict, both victorious and damaging.
Picard almost smiled as he watched the exchange between the two colleagues. Even in the face of what was shaping up to be little more than a milk run, La Forge and Data were trading information both relevant and trivial, just as they would if they were attempting to solve a looming crisis. Some things will never change.
"Once the Federation was founded," he said, "and with a whole host of new friends, to say nothing of enemies, Starfleet's charter and mission initiatives took them in other directions. After a time, verifying the fate of a single planet which was already believed destroyed for years was lost in the shuffle of larger concerns."
A student of history, Picard was intimately familiar with that period in Earth's evolution from a single civilization to one of the founding parties of what was now a Federation of more than one hundred fifty worlds. Such a feat, carried out in the space of little more than two centuries and accompanied by all manner of ancillary accomplishments and setbacks along the way, would have been more than enough to obscure any desire to investigate the presumed destruction of one planet.
Leaning forward in his chair until his forearms rested on the conference table, Riker said, "I don't understand. If there's nothing we can do for these people, then why show us the message at all?"
"It seems," Picard replied, "that Starfleet Command wishes us to chart the area of space where the probes are believed to have originated, and see if we can determine what exactly happened to the Dokaalan and their world."
"Sir," said Lieutenant Christine Vale, the Enterprise's security chief, from where she sat at the far end of the table, "wouldn't an actual science ship be better equipped for such an assignment?"
Tugging on the lower edge of his uniform jacket, Picard replied, "Perhaps, Lieutenant, but Admiral Nechayev believes that under the current circumstances, the Enterprise is the perfect ship to head up this mission."
A bitter aftertaste remained even as he spoke the words, but Picard vowed he would reveal none of that irritation or disappointment to his subordinates. Vale's point about sending a science vessel in search of the Dokaalan was a valid observation, but there was also the simple matter that no science vessel, or captain of same, was currently believed to be a hindrance to Starfleet.
The recent confrontation with the demon ship at the Rashanar Battle Site, as well as the annihilation of the U.S.S. Juno and several Ontailian warships, was still fresh in many people's minds, particularly Picard's. There were those in Starfleet, many of whom he once had called friends, who believed that his best days as a starship captain were behind him. It did not soothe his emotions to know that the perception was one manufactured to preserve the dignity of the Ontailian government in the face of their own missteps during the incident.
A valuable ally to the Federation in the current post-Dominion War reality, the Ontailians could ill afford a political incident within their own society. Such a disruption might cause them to withdraw their Federation membership, an option viewed by many on both sides as highly undesirable. The only way to ensure the stability of the Ontailian government was to make certain that blame for the demon ship incident was directed elsewhere.
In this case, that meant Picard. Though officially cleared of culpability for the loss of the Juno and the Ontailian ships, so far as the public and Starfleet were concerned, the captain had nonetheless committed a grave error. Many within Starfleet were asking whether Picard had finally begun to succumb in the face of the numerous traumatic experiences he had suffered over the length of his career. Was he still up to the task of commanding a starship, much less the vessel carrying the most renowned name in Starfleet history?
Despite the confusion, resentment, and even outright anger with which some officers in the highest echelons of Starfleet viewed him, Picard had managed to find an un-likely ally in the persona of Admiral Alynna Nechayev. It was she who ultimately had submitted the recommendation that, given the political and strategic challenges facing the Federation, an officer of Picard's experience and talents could not be dismissed from Starfleet so long as he was willing and able to serve. To Picard, the admiral's support had come as a near total surprise.
Picard and Nechayev had clashed more than once over the years, particularly in his handling of the lone Borg his crew had recovered nearly a decade ago, and with it, the discovery of a possible way to destroy the entire Borg Collective in one fell swoop. He had been unwilling to unleash what he considered a genocidal tactic, even on the Federation's most formidable enemy, and that decision had invoked Nechayev's wrath. The Enterprise captain had weathered that storm as well as several others that followed, and a mutual grudging respect had developed along the way, with each officer knowing that Starfleet was better off with the other than without.
Though a Starfleet tribunal already had ruled on Picard's actions with respect to the loss of the Juno and the damage done to relations with the Ontailians, temporary though that might have been, Nechayev had taken it upon herself to watch over Picard and the Enterprise. First, she had given them the chance to prove the existence of the demon ship and clear their names. With that issue laid to rest, there remained the much larger burden of giving Picard some needed breathing space and keeping him from becoming embroiled in any other potentially volatile political situations for the time being.
Sitting across from Counselor Troi, Dr. Beverly Crusher said, "What you mean is that Starfleet isn't sure what to do with us, so they're shuffling us out of the way to avoid any more embarrassment while they figure out a plan."
There was no mistaking the torque of the doctor's delicate jaw or the disgust clouding her dark blue eyes, and though he was tempted to admonish her for the comment, Picard refrained. Crusher, along with the entire ship's complement, was frustrated at the chain of events to this point. They deserved to blow off a bit of steam now and then. Better to do it here, among the privileged company of trusted friends, than elsewhere on the ship where subordinates already battling damaged morale might hear them.
"Admiral Nechayev believes that by assigning the Enterprise to this mission," Picard said, "her crew and most especially her captain will possibly avoid further controversy for at least a while. Therefore, that is exactly what we shall do." Turning to Data, he asked, "Commander, how long to reach Dokaalan space?"
"At warp eight," the android replied, "we will arrive at the Dokaalan system in twenty-six days, eleven hours, and forty-seven minutes. That estimate is based on long-range sensor data obtained from an unmanned exploratory probe sent to chart that region of space sixty-three years ago. Though incomplete, the data suggests . . ."
"Thank you, Commander," Picard said, circumventing an oration that, while no doubt informative, could conceivably take most of the time the Enterprise would spend traveling to its intended destination.
"Though this is supposed to be a low-risk assignment," Riker said, "we're still traveling to a sector that's largely unexplored. I don't think we should go in unprepared."
At the far end of the table, Vale said, "I agree, sir. With your permission, I'd like to conduct a series of scheduled and surprise security drills, as well as request a level-one diagnostic of all defensive systems."
"No problem there," La Forge replied. "My people will need something to do, too."
Picard nodded to the security chief. "Make it so. I leave the details to your discretion, Lieutenant." Turning to Riker and Troi, he said, "Given the length of time it will take us to reach the Dokaalan system, I want you to organize a duty roster that allows for reduced shift rotations for the entire crew. Given recent events, I want them to enjoy as much leisure time as possible." Nodding in Vale's direction and with a small smile, he added, "Feel free to factor in any of the lieutenant's surprise security drills you see fit, however. We wouldn't want to lose our edge, after all."
With a mischievous grin of his own, Riker replied, "Aye, sir."
Before saying anything else, Picard took a moment to regard those sitting around the table, each looking expectantly to him for direction.
Riker, his loyal second-in-command, who during his own career had done almost as much in the name of protecting the Federation way of life as had Picard himself.
Troi, reading him in her own unique way, knowing more about him than anyone ever could.
Beverly, her stately countenance softened slightly with age and yet still consumed by the same drive and passion he had always seen in her.
Data, who even after all these years and without the emotion chip he had been forced to surrender to Starfleet, still managed to convey the sense of wonderment of a precocious child.
La Forge, who possessed a clarity of vision that far exceeded even that provided by his artificial eyes.
Though she had not been a member of the crew for as long as the others, Vale had taken little time to demonstrate her talents and potential. In similar fashion, she had proven herself worthy of those who had preceded her as Enterprise security chief, carving herself a position of respect among the rest of the senior staff.
Shipmates, trusted advisors, valued friends. Picard knew that these six individuals, and by extension every person on the ship, would follow wherever he might lead them. While he could learn to accept how outsiders viewed him, it angered him that his crew could be treated as the pariahs many now believed them to be. Regardless of all they had accomplished over the years, despite the very real debt Starfleet and the Federation itself owed this ship and her crew, they had been sent away in the name of political expediency, no longer considered worthy of the esteem Picard believed they had rightfully earned long ago.
You will regain the respect taken from you, he vowed silently to his shipmates. If it takes the rest of my days, I will see to that.
When no one responded to his query for further questions and Picard dismissed the staff, only Riker remained, much as the captain expected he would. He recognized the way his first officer's shoulders tensed when he had something to say yet was waiting until the appropriate time. Despite the close friendship they had cultivated over the years, ingrained protocol and discipline would always prevent William Riker from speaking freely until any subordinates were out of earshot.
Watching his first officer waiting for the room to clear, Picard noted the touch of gray peppering the man's temples. The badge of maturity seemed at odds with his clean-shaven face, which gave the commander a look of youthful innocence both men knew had been left behind long ago.
"So we're not really out of the doghouse just yet, are we?" Riker finally asked once the doors to the conference lounge had closed. "They're going to just shuffle us from one meaningless assignment to another?" He rose from his seat and began to pace the length of the conference room. Watching him move back and forth, Picard realized that without his beard to hide the lines of his face, it was easy to see how frustrated Riker was by the visible clenching of his jaw.
Settling back in his chair, Picard replied, "I believe the preferred term is 'low-priority mission,' Number One."
His delivery was just deadpan enough to elicit the desired response, that of catching his first officer momentarily off guard before he noticed Picard's teasing smile. Riker laughed in spite of the frustration he was obviously feeling.
"This isn't like when they sent us to the Neutral Zone during the Borg invasion," Riker said. "At least then I could understand their reasons, even if I didn't agree with them."
Picard found himself concurring with that. His previous capture and assimilation by the Borg during their first attack on the Federation twelve years earlier had given the collective all the information needed to cut a destructive swath through Federation space and right to humanity's doorstep. Only Data's skill and Picard's own force of will, battered into near-total submission by the Borg's invasive procedures besieging his mind and body, had prevented Earth from being crushed by perhaps the most formidable oppressor ever known.
Many were certain that Picard had suffered irreparable harm at the hands of his captors. Still others, notably those who had studied every piece of information about the Borg and any scrap of technology salvaged from the wreckage of that first enemy vessel, believed the Enterprise captain might still retain vestiges of a connection to the collective. The risk of his becoming a liability or, worse yet, a weapon for the Borg in the event of a future invasion attempt was too great to ignore.
Accordingly, when the Borg had sent a second massive cube-shaped vessel on a direct attack course for Earth seven years later, the newly commissioned Enterprise, NCC-1701-E, had been sent away from the conflict. As it turned out, Picard had indeed retained a visceral link to the collective, a revelation he had used to his advantage after defying orders and joining the fight, eventually aiding in the destruction of the second Borg ship.
"This is different," Riker continued, stopping his pacing and turning to lock eyes with his captain. "To treat us this way after everything we've done? After everything you've done?"
"We're serving a larger purpose, Number One," Picard replied, hoping to convince himself as much as his first officer. "At least until the situation with the Ontailians is stabilized, Admiral Nechayev feels that assigning us to these types of missions will help minimize our impact to an already volatile state of affairs."
After the truth of the captain's actions surrounding the demon ship was revealed, Starfleet Command had no choice. Despite the belief held by many in those corridors of power that Picard himself should relinquish command, his forcible removal was not an option.
However, the unusual request of the Ontailians had put Starfleet in a quandary. In order to preserve their ally's political stability, it would have to appear that Picard was receiving some form of sanction. Though all of the Enterprise crew knew the truth, for which Picard was thankful, the majority of those serving in Starfleet did not.
"Well, if they want to give us milk runs," Riker said, "then we'll just have to log the best damn milk runs they've ever seen, won't we?" Smiling, he straightened his posture in the manner that told Picard the first officer would carry out his duties on this assignment as he would on any other mission, not that the captain needed such confirmation, of course.
Riker took his leave and returned to the bridge, leaving Picard alone in the conference lounge. Turning in his chair to face the line of viewports forming the room's rear wall, he allowed himself several minutes of quiet, watching stars streaking past as the Enterprise warped toward uncharted space. Ordinarily it was a view that soothed him, but not today. Unlike other occasions, when he might take satisfaction that he and his vessel were heading where none had traveled before, this time was different. Instead, they were running away, retreating as an unruly child might flee the gaze of an admonishing parent.
As he swiveled away from the windows, his eyes once again caught the display of ships on the lounge's rear wall. Studying them, Picard found himself unable to resist dwelling on the history his vessel shared with those depicted on the wall before him. Individually, each ship's captain had enjoyed triumphs and suffered adversities that rivaled and even surpassed his own. Together, they had woven one of Starfleet's most enduring legends.
Had his actions, either those he had actually perpetrated or others perhaps destined to be recorded for posterity, sullied that history? If so, was such damage beyond repair?
No, he decided. I refuse to accept that.
Alone and in the privacy of his own thoughts, however, Picard could not help noting a disturbing lack of conviction.
## Chapter Four
**Translated from the personal journal of Hjatyn:**
THINGS ARE getting worse.
We see only the news feeds from Dokaal now. They are constant, transmitting on all channels. Many have quit reporting for their assigned shifts, be they miners or workers in any of the support sections, and have instead taken to congregating in the public recreation areas to watch the feeds for hours on end. Still others have simply retreated to their private quarters, as if trying to find a place of safety.
Beeliq is one of the few who are trying to maintain some type of normalcy. She continues to carry out her duties at the colony administrator's office, while I try to persevere with my classes. School has been all but canceled, though, and we sit with our students and watch the reports coming from the homeworld.
The quakes are growing in number and intensity. Sometimes three or four occur at different locations around the world during a single day. On other occasions, a site already tormented by one quake is subjected to another, adding to the toll of death and destruction. Rescue workers are hampered or even thwarted when this happens, helpless to do anything in the face of renewed devastation. Resources for rescue and recovery have long since been pushed beyond their limits, and those citizens who can volunteer to assist are already doing so. Even their efforts are not enough.
Many here are frustrated at their inability to render aid. I have heard some people talking about trying to return to Dokaal at any cost. Fearful that some might attempt to take matters into their own hands, the colony administrators have placed guards on the few shuttle transports available to us. I guess they hope this will deter anyone from trying to commandeer any of the ships.
The administrators also have threatened to enact special protection measures on the colonists as well, warning that they will restrict us all to our homes and duty stations if order is not maintained. That seems to be enough incentive for most people to restrain themselves from doing anything foolish, but it does nothing to relieve anyone's anxiety over the situation.
For a time, Beeliq and I said little or nothing to one another about the escalating crisis. I know she felt the need to protect me from all of this at first, somehow, but I could always see the stress and fear she tried to keep to herself. I also know that her attempts to reach her parents on the homeworld have not been successful. Nearly a week ago, the news feeds reported a massive quake near the city where they live. The number of people believed dead has been growing with each update. Beeliq knew I comprehended what this probably meant, but I could tell she was not comfortable talking about it.
Even the meals we shared at the beginning and end of each day were quiet affairs. I think that neither of us wanted to talk for fear of the conversation turning to the situation on Dokaal, after which we would both return to our respective silences more frightened than before.
At tonight's meal, however, I finally gave voice to the thoughts plaguing every person on each of the colonies.
Our planet is dying.
Perhaps it was the way I said it, not as a question but as a statement of undeniable fact, but Beeliq only nodded when I actually did say it. She seemed almost relieved, as if a mammoth burden had been lifted from her.
Then she cried, for the first time since her brother's death.
I cried with her, for my grandparents lost on Dokaal, for the friends I had left behind when we were transferred to the colonies, for everyone who had suffered during this catastrophe. We even cried for those left to endure whatever was yet to come.
As for what that might be, people are fearing the worst. The news reports are making no attempts to soften the harsh reality of what is happening to our planet. Plans for evacuation are in progress, and all across the colonies preparations are under way to receive those precious few who will be able to escape the global devastation. It will be but a fraction of the population, a fact not lost on people who have come to realize that our planet's days, to say nothing of their very own, are numbered.
And what about those of us who already live here among the asteroids? We are trapped here, helpless to do anything except wait for our homeworld to die. What will we do in the aftermath of the coming disaster? How will we survive? Out of necessity, the colonies are able to sustain themselves for the long periods of time between supply shipments from Dokaal, but what will happen when the ships stop coming? We will have more people living here than the colony facilities were designed to support, so adjustments will have to be made quickly to accommodate them.
Caesi tells me that his wife and the other administrators have had plans set in motion for some time to deal with this situation. This means that they have known the awful truth for longer than the public has, and have been preparing. Part of me is relieved because I know that those in charge have retained their focus in the midst of this crisis and are working to give us the best chance of survival.
However, I am also concerned that there may be other facts that our leaders have withheld from us. Perhaps things are more serious than is generally believed, and the administrators are trying to prevent panic from escalating. Were I in charge, I think I would want to inform the people as much as possible, no matter how unsettling the facts might be, and trust that their initial fear and uncertainty would be defeated by their desire to survive and protect their families. I think that displaying great faith in those you lead would better allow them to trust in your guidance.
In the days ahead, I think that both the people and our leaders will need such trust if we are to survive.
## Chapter Five
SUNRISE on Qo'noS.
Since arriving on the homeworld as the Federation's ambassador to the Klingon Empire, Worf had yet to tire of the magnificent view afforded by the trio of large windows forming his office's back wall. Beyond the transparasteel barriers, the sun was just beginning to highlight the skyline, burning a fiery red and bathing everything in its harsh crimson hue.
Before his current position brought him here as a matter of course, he had visited Qo'noS only sporadically since leaving with his parents for Khitomer at the age of six. Most of those visits had not been under pleasant circumstances, so it was with no small amount of comfort that he was able to sit here, as he did most mornings before beginning his official duties, simply to relax and take in the vast metropolis before him. Worf had decided long ago that the First City was at its most peaceful during this time of day.
It was also one of the few occasions where he felt a true connection to the capital. Just as the robes he now wore as a symbol of diplomacy shrouded the beating heart of a warrior, a blanket of tranquility covered this, the very cradle of the Klingon Empire and the countless soldiers who had served it over the centuries. How easy would it be to simply sit here, ignoring the numerous appointments and responsibilities conspiring to drown him in a sea of bureaucratic chaos, and just watch the city come alive for the start of a glorious new day?
"They're calling for rain later this morning," a voice said from behind him.
Perhaps I will try again tomorrow, Worf amended silently, sighing in amused resignation as he turned from the windows to see Giancarlo Wu standing in the doorway leading from his office.
As always, his chief aide was impeccably dressed, his black trousers and shoes accentuated by a dark blue shirt and maroon vest. Wu affected an aristocratic air that in Worf's eyes was ideal for the types of diplomatic and social situations the ambassador found himself navigating, which was a good thing.
Having served at the embassy for nearly a decade, Wu's seemingly unmatched familiarity with the political minutiae that consumed so much of Worf's time, to say nothing of his superior patience for it, had proven invaluable time and again. In fact, the ambassador even had sent his aide on various missions of his own, comfortable in the knowledge that Wu's consummate skill and experience were more than enough to handle whatever was required.
"Good morning," Worf said, knowing that Wu already had been in his own office for at least an hour. As was the human's habit, he was here before sunrise each day and did not depart until the evening hours. It was normal for him to leave Worf to work alone upon his own arrival, his entry to the ambassador's office signaling the official start of the day.
"And to you, Ambassador," Wu replied before glancing down at the omnipresent padd in his right hand. Studying the device, he affected an amused expression. "I have good news and bad news. Which would you prefer to hear first?"
They both knew it was a rhetorical question. Within moments of their first meeting two years earlier, Worf had directed Wu never to withhold any information or soften it in any way, no matter how unpleasant it might be to hear. He had expected his aide to resist those instructions at first, as it had probably been Wu's habit to dissemble out of concern for the sensitivities of human diplomats. The man had instead embraced Worf's preference for direct dialogue in true Klingon fashion.
Tapping commands into his padd with such speed that Worf thought the melodic tones generated by the individual keystrokes might actually blur into a single extended whine, Wu said, "The emperor sends his regrets at having to cancel the audience you requested with him next week. He has urgent business offworld and will have your meeting rescheduled upon his return."
Worf nodded. "Notify his office that I will submit a new request through official channels and appreciate any assistance they can offer in selecting an alternative appointment." There were protocols to be observed, after all, and His Excellency was free to honor or dismiss such requests at his discretion. As it was, Worf considered it a personal honor that any sort of explanation for the cancellation of their meeting had been offered.
Of course, he did enjoy a closer relationship with Kahless than most Klingons, including those currently serving on the High Council. After the revelation that clerics at the monastery on Boreth had created a clone of the original emperor in a scheme to provide what they perceived as sorely needed leadership to the troubled Klingon Empire nearly a decade ago, Worf had been the first outsider to meet with him. Later, he had convinced Gowron, chancellor of the High Council at the time, to install the cloned version of the empire's greatest and most storied warrior as ceremonial emperor to the Klingon people. And two years ago, Kahless was instrumental in aiding Gowron's successor, Martok, in surviving a coup d'état. With honorable warriors such as Chancellor Martok—Worf's friend and mentor—leading the way, and Kahless's guidance, the Empire would regain its former glory.
Though Kahless had expressed his eternal appreciation to Worf, the ambassador had always been careful not to give the appearance of using his friendship to curry favor, particularly after taking on his diplomatic posting. Worf would not dream of circumventing the normal process for an audience with the emperor.
"On a brighter note," Wu continued, "Chancellor Martok passes on word that he still expects you for dinner this evening, assuming your schedule permits, of course."
Worf smiled at that. Despite his aide's straight delivery, there was no mistaking the humor behind the words. After all, even if one were brave enough to casually dismiss an invitation from a chancellor of the High Council, it was sheer foolhardiness to do so when that same person was also the ruler of the House to which one belonged.
"Assuming there are no interstellar incidents in the offing," he replied, "please advise the chancellor that I will be there."
Nodding, Wu made another entry into his padd. "Here's the best news of the day. Your son sent a communiqué that he has been granted leave from the Ya'Vang, and plans to be here in about two weeks. Can I assume your schedule will permit a brief vacation for his benefit?"
Though he knew Wu did not, and could not, mean anything else by asking the question, Worf realized that at another time, he might well have considered not making plans with Alexander. To say that their relationship had been strained from the beginning was an understatement of galactic proportions. After years of struggling to understand one another, father and son had finally reached a point where they enjoyed each other's company. Alexander's duties aboard the Ya'Vang coupled with Worf's own diplomatic responsibilities made those occasions rare, and Worf was thrilled when such opportunities presented themselves.
"Absolutely," he said to Wu. "See to it that any routine matters that might take place during his time here are rescheduled accordingly." With luck, Worf's duties would permit him the brief respite.
After a moment, his aide said, "Ambassador, I've also done some checking with a friend of mine at Starfleet Command. Apparently, a decision has been made regarding the Enterprise."
Worf sat quietly as Wu described the political minefield Captain Picard had left for both the Federation and the Ontailians to traverse, as well as the new "mission" Starfleet had given Picard and his crew. The only outward response he allowed was the tightening of his jaw, his frustration with the situation growing with each second he listened to Wu's report.
He was already fully aware of the incident with the Juno and the Ontailian vessels that had been destroyed. Colleagues in Starfleet had kept him apprised of the Enterprise crew's treatment in the aftermath of that tragedy. At the outset of the incident, Worf could understand the need to investigate the matter with utmost care, including the possibility that Jean-Luc Picard could have become mentally unbalanced to the point of willfully murdering innocent people.
The very idea was laughable, of course, a fact later confirmed by Starfleet specialists. What galled Worf even more than Picard's initial treatment following the incident was how he and the Enterprise crew had been "disposed of," at least for the time being.
Exhaling in disgust, Worf let his eyes wander to the wall of his office where he kept the small collection of mementos he allowed himself. Awards bestowed from both Starfleet and the Empire hung alongside photographs of Alexander and his son's mother, K'Ehleyr, as well as a still-humorous image of him and the command staff of Deep Space 9, dressed in the uniforms of the Earth game called "baseball." His eyes lingered for a moment on his wedding photo with Jadzia Dax, and he paused long enough to send a silent message to her in Sto-Vo-Kor, where she now hunted with the other warriors who had honorably given their lives in combat.
For the first time, Worf realized that among the keepsakes was no overt reminder of his time on the Enterprise. While he would scarcely have given the observation a second thought only a few years ago, he now found the idea troubling for reasons he could not explain, at least not yet.
Was it because of the situation his former shipmates currently faced, and that he was not there to stand with them?
Opportunities to see his friends on the Enterprise had been rare, particularly since he took on his role as ambassador. Other than the time the ship had ferried him to the Klingon border for his first diplomatic assignment on taD, the gateways crisis, and the mission involving the mysterious Malkus artifact, the opportunities had been few and far between. While he knew he was carrying out important duties here on behalf of both the Federation and the Empire, there were times he wished he were still serving in Starfleet, doing his part to look after his comrades. He wanted to help them now, but what could he do from here?
As if reading his mind, Wu said, "You know, with your travel schedule being what it is in coming months, it would not be unusual to request a Starfleet vessel be detailed for courier duty. I'm sure that special consideration would be given if you were to ask for a specific vessel for that purpose, assuming that ship's mission priorities permitted it."
It was an interesting notion, Worf decided, and a tempting one. Such an assignment normally was viewed as an honor by Starfleet brass, even if individual ship crews and their captains regarded the duty as only slightly less glamorous than replacing navigational buoys. Being specifically requested for such a mission was further considered to be a singular privilege. Worf also realized that by having the Enterprise as his courier vessel, he would be able to call upon Picard's own formidable diplomatic skills. If nothing else, it would surely be a better assignment than being "banished" to some faraway corner of the galaxy.
For that reason alone, Worf discarded the idea.
Shaking his head, he replied, "No. That could be perceived as using my position to come to Captain Picard's aid." While he did not care how such a move might reflect on him personally, Worf did not want to add further unfavorable light to Picard or the Enterprise. Besides, he knew his shipmates would find a way to weather this controversy without his help, and they would do so beginning with this odd assignment Starfleet had seen fit to give them.
"Where is this Dokaal system?" he asked.
Checking his padd, Wu replied, "Beyond the limits of explored space, it seems, out past Cardassian and Tholian territory. Ordinarily it would be a plum assignment, especially for such a passionate explorer as Captain Picard. Under the circumstances, however, anyone with even cursory knowledge of the situation will see this tasking for what it truly is."
Worf agreed. Not actually a punishment, so far as the legal or technical definition of the term was concerned, the Enterprise's assignment to investigate the origin of a distress signal sent more than two centuries ago was a slap in the face to a man of Picard's stature and accomplishments, to say nothing of the rest of his crew.
While the complete details of the so-called Ontailian Incident had been classified, Worf knew that there were those in Starfleet who had called for Picard's dismissal from service in the wake of the Juno's loss. Despite his exoneration, political schemers who had lost face during the incident would be looking for restitution. Publicly reprimanding the Enterprise crew, particularly Picard, would not sit well with the numerous allies the captain had garnered over the years. Therefore, all they could do was send him on a mundane assignment and get him out of the way. Perhaps they would dispatch him on another such mission once he had completed this one, and another after that, and keep doing so until Picard finally resigned in frustration.
That was unlikely, Worf decided. Admiral Nechayev was far too shrewd an officer to allow the captain to leave under such circumstances. As she had with other officers on different occasions, she would find a way to protect Picard until the current situation subsided.
As for Picard himself, he was as adept at playing the "political game" as anyone he had ever encountered. His brinksmanship skills were on par with his command abilities, rivaling even the very talented individuals Worf had come across since becoming an ambassador. The big difference between Picard and career politicians, of course, was how and why he put those skills into play, and a key advantage he held over those who would see him removed from command of the Enterprise was his seemingly limitless reserves of patience.
Worf smiled at that as his gaze moved to the corner of his desk and to the small leather-bound book he had deliberately placed there. A gift from Picard, it was a reproduction of an ancient Earth text, The Art of War.
He had read the book while a student at Starfleet Academy, of course. However, it was not until revisiting it, this time benefiting from many more years of experience, that he realized the volume's multilayered message and just how appropriate a gift his former captain had offered. Despite the book's obvious title, the words of wisdom recorded by the human warrior Sun Tzu centuries ago were not only a timeless guide for battle, but were also applicable to a great many other situations, including politics.
There was yet one more message carried within the pages of the book, Worf realized, one even Picard had not anticipated when he had sent it: No matter how long this "game" went on between him and Starfleet, Worf was certain that his former captain would emerge victorious.
While he knew that Picard would appear confident in any public setting, a pillar of strength to those who looked to him for leadership, what toll would this struggle exact on the man himself? How would it affect him during those moments of solitude he cherished? Though Worf was concerned for his former captain's well-being, both physical and mental, he knew that if asked directly, even in a private conversation, Picard would almost certainly conceal his true feelings.
To obtain the information he sought, Worf decided he would have to go about getting it another way.
## Chapter Six
DROPPING THE PADD onto his desk, Geordi La Forge closed his eyes and rubbed his temples, groaning in satisfaction at the momentary relief the action brought. Though his eyes might be artificial, the muscles and nerve endings that received the information supplied by his ocular implants were still nothing but good old-fashioned human tissue, and they were tired.
With days of open space ahead of them and hours of idle time likely to result, La Forge had already begun to straddle the fine line between giving his engineering crew purposeful tasks and loading them up with busy-work. His first impulse as chief engineer was to take advantage of the long haul to the Dokaalan system by putting the Sovereign-class ship through a stem-to-stern regimen of diagnostics and system tests. It would be a lot of work, but La Forge had good reason for it.
Even now, three years after the end of the Dominion War, Starfleet's ship-maintenance facilities were still laboring to alleviate the backlog of service and repair requests. The fleet was struggling to return as many ships to active duty as they could in the shortest amount of time possible, so routine and noncritical tasks were being deferred. Engineering staffs aboard many ships, particularly those with limited access to such facilities in the first place due to their current assignments, were taking matters into their own hands. Already formidable technical skills were being enhanced through impromptu on-the-job training as they took on some of the more complex tasks usually performed at drydocks and starbases.
Knowing that the Enterprise probably would be out of touch with the level of Starfleet support it had enjoyed in recent years, La Forge and the rest of the department heads had taken care to insure that the ship's stores were fully stocked with all manner of spare equipment and replacement parts to maintain the myriad onboard systems. For the engineering section, this included a few bulkier components not usually carried aboard ship, as well as replacements for items normally diagnosed and repaired only at a drydock facility.
He also knew that their lengthy journey would be just the opportunity to experiment with increasing the graviton loads of the deflector shield generators, or perhaps to replace that pair of power couplings in the impulse propulsion system on which he was keeping watch, and those were just off the top of his head. Even with Captain Picard's desire for the senior staff to afford the crew as much recreational time as possible during the voyage, there would be plenty of opportunities for him to see to his project list and still allow his people some time for rest and relaxation. That in itself would be a welcome change for a ship that typically saw little inactivity.
Not for the first time, La Forge observed just how fortunate he was to lead the complement of engineers assigned to the Enterprise. One of the many benefits of serving on the Federation flagship was that, sooner or later, the best and brightest of Starfleet's engineering minds ended up here. He thought of Reg Barclay, who served on two incarnations of the starship before becoming a key player on Project Pathfinder and aiding the U.S.S. Voyager in its return from the Delta Quadrant. And there was Sonya Gomez, who began her career on the Enterprise as an unsure ensign and now served as a highly capable commander aboard one of the ships assigned to the elite Starfleet Corps of Engineers.
His mental list went on until La Forge paused at the realization that, in the eyes of many, the Enterprise might no longer be the destination of choice for the most talented personnel in Starfleet. There was also the distinct possibility that some members of his current engineering crew might start to explore better opportunities for themselves elsewhere. After all, there was little to hone one's skill set in missions like this one.
I don't want to lose good people simply because there isn't enough to keep them here anymore.
It would require an extra effort from him to make sure that his engineers' sense of purpose was maintained. Simply keeping them occupied at their duty stations would not be enough. Lieutenant Vale's idea of running security drills, which would include diagnostic tests of the ship's defensive systems, dovetailed nicely with his own agenda.
With a plan for success already in action, La Forge had also reminded himself that part of the equation was to see to it that his people also set aside less pressing matters and spent some time on more frivolous pursuits.
And that includes me, he mused as he left his office and made his way from the engineering levels to the upper decks of the saucer section, heading for officers' quarters. Walking the corridors, he was comforted by the steady rhythm of the Enterprise's warp drive as the vessel powered toward the Dokaalan system. It was the smooth, strong sound of a well-maintained ship, he knew. Most people eventually learned to tune out the omnipresent thrum of the engines, but La Forge always listened for it, knowing that it would often provide the first clue as to a problem in the heart of his beloved ship.
Finally, he came to one particular door, hoping even as he reached for the call button that his leisure plans also included the person he had come to see.
"Come in, please." Data's voice filtered through the panel positioned next to the door. As La Forge stepped into his friend's quarters, he realized that almost all of the lights in the room had been extinguished. The only signs of activity came from the android himself, seated before the extensive computer station that dominated the room's right wall. Looking up at the engineer's approach, Data said, "Hello, Geordi."
La Forge smiled as he moved farther into the room. "What are you working on?"
"I have been studying the information contained on the two Dokaalan probes, as well as the reports compiled by the Vulcan Science Directorate in 2151. While neither the Vulcans nor Starfleet specialists were able to determine their exact point of origin, there are clues within the probes' recorded messages that may help us narrow our search parameters once we arrive in the Dokaalan sector of space."
Taking a seat in the other chair positioned near the workstation, La Forge admitted to himself that his interest was piqued. "Really?"
"I have been analyzing the visual transmission by the Dokaalan leader," the android continued, gesturing to an image from the centuries-old transmission frozen on one display monitor. "Notice the color of the sun and the orange hue of the sky behind First Minister Zahanzei. This suggests that their planet orbited a star of the spectral class K-1. Given that, the size of the star in relation to the planet suggests an orbital path within the ecosphere of a typical K-1 star as I have plotted here." Tapping a command string into his console, Data called up a tactical display that showed a haze around an orange point of light against a grid demarcating dozens of light-years.
La Forge nodded approvingly. "That seems like the place to start looking, then." It would be simple for Data to take the information he had gathered here and correlate it with the star charts and other navigational aids stored in the main computer. He would be able to determine if this star system was the former home of the Dokaalan long before the Enterprise arrived there.
Data said, "I have also cross-referenced the visible characteristics of the Dokaalan race with all available information from Starfleet Medical biological files. Based on the first minister's epidermal coloration, facial physiognomy, and overall structure, he physically resembles fourteen distinct races known to the Federation."
Confused at this, La Forge said, "That's interesting, Data, but I'm not sure where you're going with it."
"I accessed all available geophysical information on the planets to which those races are native," the android replied as he keyed the console again, and La Forge watched one monitor begin to scroll columns of data faster than he could read it. For a moment he mused that the effect would be dizzying—if he had real eyes.
"As common environments lead to common species development," Data continued, "I have compiled a list of naturally occurring elements on those known planets as well as their percentages of concentration. Assuming the Vulcans were correct when they reached their original conclusion that Dokaal indeed exploded due to prolonged tectonic stress, programming our sensors to detect such elements should help us locate planetary debris."
"Um, okay," La Forge said, starting to wonder just how much time Data had devoted to this research exercise. "That's not a bad theory, but . . ."
Entering yet another string of commands, Data called up a new image to one of the display monitors. "And here, I have created a mathematical construct of the planet's geothermal explosion, starting with the mass of a typical Class-M planet. Such destruction is likely to have exerted enough force to propel fragments of the planet in this manner."
"Uh, Data?"
Focused on his report, Data continued, "Lack of surveys in this region prevents us from accounting completely for any gravitational effects of surrounding stars or planetary bodies. It does, however, give me reason to believe that fragments of the planet could be encountered as soon as . . ."
"Data!"
The android halted and turned to face him. "Yes, Geordi?"
La Forge took one look at his friend's somewhat quizzical expression and laughed a bit. "Data, this is all very helpful, but did Captain Picard ask you to put it together?"
"The captain tasked me with tightening the focus of our search in an attempt to determine the probe's origin point within the shortest amount of time," Data replied. "He was not specific with the details of his request, so I have exercised my own initiative in order to provide the most comprehensive investigation possible."
Smiling, the chief engineer put a hand on Data's shoulder. "Data, I know you love doing this kind of thing, but when the captain said he wanted the crew to take some time off during the trip, he meant you, too. I think you've accomplished enough for one day, so what do you say about finding something relaxing to do?"
"I do not understand," the android replied. "You said this information would prove useful in our mission. Should I not continue?"
"Oh, I'm sure it will, Data," La Forge said, trying to explain himself without sounding too condescending. "I'm sorry. What you're doing is important. I thought that maybe you were just working so hard at it because you were bored."
"While I did experience sensations comparable to boredom on four separate occasions after the installation of my emotion chip," Data replied, "I have found no such variations in my motivational subroutines since the chip's removal. I do not believe I remain capable of boredom."
"I see," La Forge said in a soft voice, finding himself taken aback by his friend's stark admission. In the wake of the incident with the demon ship, Data had been ordered to surrender his treasured emotion chip to Starfleet scientists. The slightest pleasure or the deepest pain were foreign sensations to him once again. Perhaps it was a blessing that he would be incapable of even aching for his own loss, and La Forge now realized that he himself had not taken the time to appreciate the full ramifications of his friend's choice.
With all of the activity surrounding the status of Captain Picard and the Enterprise in the wake of the demon-ship incident, the engineer had not taken the time to seek Data out and discuss his decision and its results in detail. Now he wondered whether he might have been unconsciously dodging the topic.
"Data, I'm sorry," La Forge said. "I just realized that was a pretty thoughtless thing for me to say."
The android nodded, appearing almost to console him rather than the other way around. "It is fine, Geordi. Without emotions to offend, I am the best individual on whom you can demonstrate your thoughtlessness."
Laughing aloud at that, La Forge suddenly felt as though he had been caught in a temporal loop that had tossed him into a conversation with his friend that could have occurred more than a decade ago.
In many ways, that was precisely what had happened. This "version" of Data, without Dr. Noonien Soong's emotion chip, seemed more like the person he had met during the Farpoint mission, his first assignment aboard the Enterprise, than the close friend he had accompanied to the Starfleet tribunal.
According to the reports detailing the battery of diagnostic tests Starfleet technicians had performed on Data, the android's memory banks had been unaffected by the emotion chip's removal. His ability to access information regarding their travels and missions together appeared to have remained intact. However, without the chip to enhance his personal recollections of his experiences, his drawing of information from those memory files would carry the emotional warmth and impact of an encyclopedic database.
"It just occurred to me," La Forge said, "that in a lot of ways, you're starting over, aren't you?"
Appearing to mull over the engineer's words, Data paused several beats before responding. "I had not considered that before now. According to my self-diagnostics, my internal calculations are now performing at a rate that is 2.6877 percent more efficient than when the emotion chip was an active part of my systems. My current processing rate is within 0.0023 percent of my efficiency rating on Stardate 48642.8, my last internal diagnostic before the chip was installed." Nodding, he added, "In a manner of speaking, I suppose this does mean that I am starting over, at least in some ways."
La Forge forced a smile, well aware that his friend, in all likelihood, had no clue that he really had changed. He wondered if Data had felt compelled to discuss the situation with anyone, or whether it might help him, or perhaps both of them, to better appreciate what this all meant.
Deciding to take advantage of the opening, he asked, "Would you like to talk about it?"
"Would that make you feel better, Geordi?"
I guess it's dumb for me to think it might make you feel better.
"Yes, Data, I think it would." La Forge considered several possible avenues of inquiry before finally deciding it best to start by keeping things simple. "Have you noticed anything different in your ability to operate or perform your duties? Aside from the increased efficiency, I mean."
"I have not."
"Have you sensed any, well, unexplained interruptions in your routines or protocols? Any lapses in function?"
Data shook his head. "I have recorded no such lapses."
"Your positronic brain and its accompanying programming have adapted over the past few years in order to function with your emotion chip," La Forge said. "Its removal is sure to affect, at least in some way, your overall operating systems. Do you sense any . . . loss?"
"As I have stated, I do not."
"That just doesn't seem right to me," La Forge said in a tone that belied his frustration. He was fumbling for the words and he knew the logical answer to the question he wanted to ask, so why did articulating that question seem so difficult? "Do you miss the chip, Data?" he asked finally.
The android's head cocked to one side in his typical expression of thoughtfulness. "I understand what you are attempting to say, Geordi, but no, I do not miss my emotions. Rather, without them, I am following a new sense of purpose."
This caught the engineer by surprise. "Really? In what way?"
"My quest to better understand humanity was driven in part because I operated under the axiom that such information was required if I were to create my own emotional subroutines. I now know that creating such subroutines would result only in redundancy, as they already exist within the chip. Since the chip may be reinstalled someday, it appears that my energy and abilities would better serve the ship were I not pursuing goals of a personal nature."
The blunt statement stunned La Forge. "But Data, that very pursuit is what makes you you. No one expects you to give up part of yourself, regardless of whether you have that chip."
"I understand that," Data replied, "but such efforts now seem unnecessary to my duties aboard the Enterprise."
"Data," La Forge said, unsure how to proceed from here, "I . . . I don't know what to say to that." He shifted in his seat, suddenly uncomfortable with the direction this conversation had taken. "What about playing the violin or painting or acting out on the holodeck?" La Forge asked. "Are you saying that you don't care about any of that anymore?"
He allowed his gaze to wander about Data's quarters, seeing the mementos and other items the android had collected over the years. Placed carefully on a small table was the violin he had learned to play years ago, even going so far as to participate in numerous impromptu concerts performed with other Enterprise crew members who played other musical instruments. A display case mounted on one wall held the various medals and awards Data had earned during his Starfleet career. One bookshelf held a few treasured volumes: The Collected Works of William Shakespeare, which had been a gift from Captain Picard; The Dream of the Fire by K'Ratak, given to him by Worf; and I, Robot, a work of twentieth-century speculative fiction that La Forge himself had offered as a present some years ago.
Did nothing in the room offer an emotional connection any longer? Had all of these once-treasured items lost their meaning and value for Data? La Forge wondered what else his friend might have lost through the simple act of surrendering his emotion chip. Did Data believe that all the things he had once done for fun, or at least for the cataloguing of those sensory deviations that might approximate fun, no longer held any interest for him?
"I do not require or even desire recreation or hobbies as I once did," the android said flatly. After a moment, he added, "However, I do recognize the benefits of companionship and spending time participating in common activities of interest. If you would like, I will accompany you to the activity of your choice."
"Uh, sure, Data," La Forge said as he grappled with the sensation that he had just lost one of his best friends. He found himself trying to remember his old methods of introducing Data to intrinsically human experiences, but then again, that was when the android wanted to embrace such opportunities. Now that he seemed rather aloof to it all, where should Geordi start?
"Maybe we could try the holodeck?" he suggested. "I helped Lieutenant Osborne load a whole batch of new programs before we left Earth, including a couple of Sherlock Holmes mysteries written just last year."
"An excellent suggestion," Data said as he rose from his seat. "That should prove most entertaining."
As he followed his friend out into the corridor, however, La Forge was already beginning to have his doubts.
## Chapter Seven
To: | Dr. Yerbi Fandau, Surgeon General
Headquarters, Starfleet Medical Services
Division
San Francisco, Earth
---|---
From: | Dr. Beverly Crusher, Chief Medical Officer
U.S.S. Enterprise-NCC-1701-E
Dear Yerbi,
I was pleasantly surprised on my return to the Enterprise to find your communiqué waiting for me. It was a gracious way for you to follow up our meeting, especially knowing how busy you must be these days. I also appreciate your sending along the monograph by Dr. zh'Costeth on Andorian toxic encephalopathy that we discussed, as I have been following her research for some time.
Please forgive the delay in my response. Truth be told, I had not at all anticipated hearing from you so quickly given all the preparations you must be making. It should not surprise you that I still am grappling with the news of your decision to retire. While I'll miss your leadership and professional counsel, I hope you know that no one is as happy for you as I am that you feel ready to step away from your duties and enjoy life. Can I admit to being a little jealous of your plans to join Glinn and her children on Beta Trianguli III? Embrace every opportunity to enjoy your family, my friend. I know how much they mean to you.
Also, I must admit to being very flattered by your now formal offer for me to succeed you as Surgeon General. This especially is gratifying in light of your personal recommendation being approved by the Federation Council. I credit so much of my interest in curative medicine and xenobiological research to the invaluable mentoring I have received by your hand over the years. Knowing that you would entrust me to continue the practices and policies you have instituted during your tenure is an honor indeed.
When we last spoke, we laughed about the twists our lives often take when we least expect them. Had my desire to heed the call of practicing medicine in the field not led me back to the Enterprise after only a year at Starfleet Medical, I might still be serving in the very position you now are asking me to resume. That year taught me much about the bureaucratic side of medicine, something you know I continue to regard as a necessary evil. I do, however, want you to know that I understand and appreciate how the position can provide me the best of both worlds, if only I allow it. I could reintroduce myself to the inner circle of leadership at Starfleet Medical while following my own research pursuits. I also find very appealing the aspects of guiding other physicians and researchers in their various projects. To me, that's like having all the fun of being a teacher without the burden of having to grade term papers.
I realize that such an offer cannot remain on the table for long, but please know that I am giving serious consideration to it. As soon as time permits, I promise to contact you to discuss the matter further.
Again, thank you. Once more, you have proven yourself as an unwavering advocate and a treasured friend.
Sincerely,
Beverly
Reading her letter for the fifth time, Beverly Crusher found her finger wavering over her data padd, hesitating to send it.
It would have been easier to simply record a visual message to Dr. Fandau, but that seemed so informal, considering the subject matter of his correspondence. An actual written letter lent a credence to his request that a visual recording lacked.
With that in mind, she had still deferred writing the letter as long as she could, and even then she had agonized over her choice of every word in uncounted drafts. Now she lingered over her actions yet again.
She believed her sincerity showed in her writing, as she had devoted a substantial amount of time to considering Dr. Fandau's offer. Being asked to once again lead Starfleet Medical, at this point in her career, would allow her much latitude in the pursuit of her personal goals. It would put her back on Earth, a place where Wesley might need her to be should his time with the Travelers come to an end. It would give her some stability in her career that her life aboard a starship could not provide. No one really would fault her for accepting the offer, coming as it had from an old friend and trusted mentor. It was not as if she were asking to be assigned to another ship, after all, even though she wished that Yerbi's timing could have been better.
Why do I feel like a deserter?
Crusher had always considered physicians as the first persons expected to act in a time of crisis. In all her career, she never had hesitated to scoop up a medikit and rush to an emergency situation, or failed to insure that sickbay was prepared to treat one or dozens of injuries at a moment's notice. She strived to be a calm presence and an efficient, capable healer no matter what the challenge or working conditions.
And yet now, when the political pressure being directed at the Enterprise seemed tuned to its highest intensity in her experience, at a time when the crew—Jean-Luc Picard in particular—might very well need her most, she was here, alone in her office and thinking about leaving the ship. For the first time in years, she was questioning herself and felt her confidence in her own decision-making skills faltering.
Why now? And why does it feel like I'm the only senior officer looking to get out?
The pneumatic hiss of the sickbay doors followed by a pained moan drew Crusher from her reverie and she bolted from her seat, already forgetting the padd displaying the still unsent letter. She raced into the main sickbay area to find a pair of crew members, each wearing exercise fatigues. She recognized Ensign Jarek Maxson from the ship's security division, a tall and muscular human male, cradling a woman in his arms.
"Lieutenant Perim?" she said as she got her first look at the woman's face. Perim had been serving on the Enterprise as a conn officer for the past few years and was also one of the ship's handful of Trill crew members. Taking some of the load of the lieutenant's weight from Ensign Maxson, Crusher asked, "What happened?"
"It's my knee, Doctor," Perim replied, the discomfort evident in her voice as she spoke. "I hope I didn't blow it out again."
With Maxson's help, Crusher eased Perim onto a diagnostic bed, its array of biosensors automatically activating as the injured officer attempted to adjust herself to a more comfortable position. Drawing a breath through gritted teeth, Perim groaned. "Damm it!"
Crusher produced a medical tricorder from the pocket of her smock and stepped around the bed to stand next to Maxson. He said nothing, but Crusher saw his expression of concern as he watched. She also noticed that his face was covered in sweat and grime.
Pulling the tricorder's separate peripheral scanner free, she activated the unit and waved it over Perim's right leg. "I'm afraid it is your knee again," the doctor said a moment later, reviewing the tricorder's scan readings. "Been hiking the Tenaran ice cliffs again?"
Maxson answered, "Today, it was Half Dome."
"Well, tomorrow, it's a nice, safe, boring chair," said Crusher, allowing a smile in the hope it would ease some of Perim's concern. She traded her tricorder for a hypospray and dosed Perim with enough terakine to cut her pain. The doctor expected the standard analgesic to work quickly, given that the dose did not need to be metered with benzocyatizine, as would be the case for a joined Trill.
Crusher was thankful that none of the Trill currently assigned to the Enterprise carried the symbionts that distinguished the species as unique among Federation members. While the biological concepts relating to Trill humanoid hosts and vermiform symbionts fascinated her, particularly in the years after her very personal encounter with Ambassador Odan, the doctor was well aware that the risks associated with any emergency medical treatment escalated steeply for both Trill beings in a symbiotic relationship.
Perim closed her eyes and breathed deeply as Crusher watched the medicine take effect. A few moments later, the Trill opened her eyes and smiled a bit. "Much better. Thanks, Doctor."
"I can repair the damage easily enough," Crusher said, "but we should probably talk about this. Would you like to do it now or later?"
"Now's as good as time as any," Perim replied, then turned to Maxson. "Jarek, I'm fine. Go on and finish the hike. We still have the holodeck booked for another hour, I'd bet."
"Well, only if you're sure you don't need anything," the ensign said, his concerned expression relaxing only slightly.
"Go," Perim said, smiling as she waved him away. After he had gone, she said to Crusher, "I think this upset him more than it did me."
"I have to wonder," the doctor said, "what's more hazardous? Hiking in the holodeck or hanging around with Ensign Maxson?"
"But he's so cute," Perim said, laughing. "Doctor, it's just a fluke he was with me again when I got hurt. He's not a bondo or anything."
"A bondo?"
"Oh, a . . . what's the word," Perim said to clarify. "You know, um, a jinx."
"Got it," Crusher said, nodding as she worked to suppress a grin. The time for being a friend was over, and now she had to play the part of concerned physician.
"So, Kell, here we are, looking at your third ligament problem in as many months. I think you know the drill by now. Plan on spending the rest of the day under a bioregenerative field for your knee, but the reality is that it's time to consider a bioim—"
"Please, Doctor, don't say it," Perim said, cutting her off and affecting a playful wince.
"A bioimplant replacement for your knee," Crusher finished, raising the volume of her voice while maintaining a tone of compassion. "I know you're hesitant, but there's no reason to keep putting it off. Your ligaments are not responding to the regeneration treatments as we'd hoped." She had to hide her amused expression as she watched Perim fidget on the table, sighing deeply and closing her eyes.
"Maybe if I stopped pushing myself," the Trill said. "I could give up the hikes for . . . well, I don't know, cooking classes?"
Crusher laughed softly, recognizing the lieutenant's humor as a good-natured attempt to deal with a diagnosis she obviously did not want to hear. "Kell, you're an active, physically fit young woman, and medically we have the treatment available for you to stay that way. Besides, in our business, the last thing you want is a body that could fail you when you least expect it."
Looking away as if to consider the doctor's words, Perim finally nodded a moment later. "I know you're right, really I do. I just hate the idea of surgery, or of having some kind of artificial component to replace a part of my body."
Crusher left the diagnostic bed long enough to wheel a stool and a field emitter to Perim's side. She swung the arm of the emitter to position it over the lieutenant's injured knee and, touching a small input pad, activated a soft-blue-colored beam that washed over the reclining woman's leg.
"It's a pretty simple procedure, Kell. I could schedule it today and in a few days, you'll never know the difference."
"But Dr. Crusher, I will know the difference," Perim said, the first hint of anger lacing her words. "It'll be something inside of me that is not me. I know that sounds stupid, but I can't help myself. I've been that way all of my life."
"It's not stupid," Crusher said, focusing her attention more on the emitter than on her patient. "I guess it just seems a bit . . . unusual . . ."
Perim filled in the pause herself. "For a Trill, you mean? That's what you wanted to say."
The doctor sheepishly admitted to herself that it was exactly what she wanted to say, or at least how she automatically completed the statement in her mind. "Yes," she admitted with a tinge of regret. "Yes, Kell, it is, and now it's me being the stupid one. I'm sorry."
"It's all right, Doctor," the lieutenant replied, sighing as the words were spoken. "It's nothing I haven't been asked about before."
Several moments passed as the two women sat in silence, the normally unobtrusive sounds of the sickbay's medical monitors and the hum of the starship's engines now quite audible to Crusher. How was it that she never noticed the omnipresent background noises except when she was searching for words that might help navigate an awkward moment in conversation? She busied herself adjusting the regenerative field's emitter a bit before Perim finally spoke again.
"You don't know this," she began, "but I was almost joined once."
The admission caught Crusher off guard. So far as she knew, nothing about this was included in Perim's personnel file. Then again, there was no reason for such information to be recorded, was there?
Returning the lieutenant's gaze, she replied in a soft voice, "I didn't know. May I ask what happened?"
"It's not a long story," Perim said. "My parents were never joined, but it was a dream that my mother had for each of us. I was perfectly happy without all of the stress of dealing with the Symbiosis Commission. I got good scorings in school, I played a lot of wusher and parrises squares, things were fine. Then one day, these two people came to the door to take me for testing. My mother had submitted my application to the commission and I didn't even know it."
"And you were surprised?" Crusher asked.
"I shouldn't have been, but I guess looking back it all was a bit of a shock." Shaking her head, Perim continued, "And I was gone for weeks to take more tests until I finally went before the evaluation board for consideration."
"What happened?"
Perim smiled a bit. "They said I had qualified, but I declined." Crusher felt her jaw drop a bit as Perim paused. "It embarrassed our whole family, and . . . well, things have never been the same with my mother, but I walked away."
"That does surprise me, Kell," the doctor said. "I thought approvals to join were few and very coveted."
Perim paused, mulling over Crusher's statement a bit before answering. "Imagine yourself without arms or legs or any real means of getting around at all beyond the perimeter of a pool in a cave. You discover that other beings exist who can take you out of the pool, beyond the cave, into the warmth of the sun and anywhere in the galaxy. Then imagine those other beings as the only means for you to sense more intensely everything in your environment, and I mean everything . . . food, music, a cool breeze from the ocean, the touch of a man. You're not just dependent on those beings, but actually addicted to them through the intense bonding that you share. You cling to that connection, define your life around it, and guard it jealously."
Crusher nodded as she listened. It was not hard for her to imagine what Perim was relating. Commander Riker had offered similar descriptions in the days after he had carried Ambassador Odan's Trill symboint.
"So, Doctor," Perim continued, "in that case, wouldn't you do everything in your power to preserve your connection with your host? Fight to the death? Maybe tempt your host with a new ability to draw upon a greater knowledge or wisdom? And just maybe, over the generations, might you convince your host that carrying you around was something desirable, a privilege or even an honor for you?"
Finding herself without words, Crusher was unsure as to whether the blank expression she was certain was on her face would either puzzle or amuse Perim.
For generations, the people of Earth had challenged their belief systems with discussions of how the biological abilities of nonhumans affected their own ethical thinking constructs. In her days at the Academy, she and other medical students regularly posited the true impact on human experience of a Vulcan mind-meld or a Denobulan mating scheme or a Deltan oath of celibacy. Crusher certainly was no stranger to the bioethical implications of any symbiotic relationship, including but not limited to the dominant species of Trill.
"It's not as though I'm the only Trill who feels this way," Perim said.
"Oh, uh, of course not," Crusher said, stammering a bit. "It's just that I've never talked about this with a Trill before." In fact, such discussions typically took place among peers, fellow physicians and researchers, and generally human ones. This was a first for Beverly Crusher to hear a near damning of the Trill cultural system from a member of the species herself.
"Tell me, Doctor, have you ever discussed the physiological impact of suppressing emotions with a Vulcan before?"
"Well, yes, I have," Crusher replied.
"And I'm willing to bet that you've talked with Captain Picard at length about the rationale and justifications of the Borg collective?"
Crusher actually felt herself flinch at that question. She and Captain Picard had spoken at length about the Borg on numerous occasions, though usually it was in the context of his own traumatic experiences with them. In the months following his abduction and transformation into Locutus, it had been very difficult for Picard to discuss the incident and what he had been feeling. The intervening years had eased that pain somewhat, but Crusher knew that the captain might never fully come to terms with what had happened to him.
Unsure whether she appreciated what she perceived as a loaded question, the doctor nevertheless nodded in response. "Yes, of course I've talked with him."
"Well then," Perim said, "anytime you want to talk about Trills, just pull up a chair. Maybe we can broaden each other's horizons a bit. Besides, the more time I talk, the less time I have to tear myself up in the holodeck."
Smiling, Crusher nodded as she rose from her seat. "I just might take you up on that, Kell. You've given me something new to think about, and that's my favorite part of this job."
"Then you must really like it here on a starship," the Trill said as she lay back on the diagnostic bed. "I've learned something or found something new to think about just about every day since I came aboard."
Saying nothing as she made her way back to her office, Crusher stopped short when her gaze fell upon the still-activated padd lying atop her desk. With it came everything she had been thinking about and putting off and agonizing over for the past several days.
Damm it.
Perim was right. She did like it here on the Enterprise, but she had liked it at the Arvada III colony and in San Francisco and on Delos IV and other places she once called home.
They were also places she had left behind.
Standing alone in her private refuge, protected from the eyes of her staff or Kell Perim or anyone else who might enter sickbay, Beverly Crusher shook her head and sighed in exasperation.
I guess making the decision just got harder.
## Chapter Eight
"LIEUTENANT?"
Lost in thought, Christine Vale was startled by the forceful voice coming from her right. Looking up, she saw Lieutenant Taurik, one of the Enterprise's junior engineers, standing next to her. In the subdued lighting of the dining facility, the Vulcan's green-tinged skin looked even paler than usual, and his black hair seemed to absorb some of the room's ambient light.
"I'm sorry," Vale said as she reached for her glass of juice, as untouched as the rest of the meal she had prepared in one of the dining hall's replicators. It was a pitiful attempt to cover up the fact that she had allowed her mind to wander, one she knew the engineer probably saw through easily. Sighing in resignation, she shook her head. "I guess I sort of drifted away there for a minute. I hope you weren't standing there long."
Taurik replied, "Precisely one minute and forty-three seconds." His expression never wavered as he added, "I had begun to wonder if you had fallen asleep or perhaps suffered some form of hearing loss."
Vale chuckled at that. Few Vulcans understood humor, at least in the manner that humans embraced it, and fewer still actually employed it themselves. Taurik was an exception to that unwritten rule, his stoic nature being ideal for the deadpan manner he used to deliver his attempts at humor. By Vulcan standards, the engineer was practically jovial.
Holding a tray of his own, Taurik said, "I hope I am not interrupting you, but I was wondering whether I might speak to you for a few moments." Vale indicated the empty chair across from her and the engineer sat down. His tray held a single bowl containing what her nose told her was plomeek soup, a Vulcan dish.
"What's on your mind?" Vale asked, watching with some surprise as the engineer seemed to search for the appropriate words.
"Though you and I are of equal rank," he said, "as security chief, you are cognizant of things others of us are not. I was wondering whether you had noticed anything out of the ordinary in the behavior of the senior staff. I am speaking specifically of Commander La Forge."
An odd question coming from a Vulcan, Vale thought, even Taurik. Perhaps all the time he had spent among humans had rubbed off on him in other ways. "How do you mean?"
Straightening in his seat, Taurik replied, "I have heard some of the other engineers talking, and they all seem to agree that the commander has not 'been himself lately,' as one put it. I admit that while I do not understand the full range of human emotions, I believe I am familiar enough with his personality to know when there is a . . . deviation."
Vale cocked an eyebrow at that. "A deviation," she repeated, nodding after a moment. "Well, we've all had a lot on our minds lately. He could just be tired. I'm sure he'd be open to talking about it if one of his people thought it was affecting his duties in some way."
Taurik shook his head. "No, it is nothing like that. My interpretation of the others' comments is that they are troubled about his well-being. I would be remiss if I did not say I shared their concern." Pausing a moment, he added, "I apologize if I am overstepping my bounds, but it has been my experience that humans often work out their problems by talking about them to someone else."
"Thinking of a career change, Taurik?" Vale asked, grinning. "Counselor Troi might have something to say about you muscling in on her turf." She almost laughed at the shock that momentarily clouded the Vulcan's expression. It was fleeting and Taurik regained his control almost instantly, but there had been no mistaking his reaction. Even as he opened his mouth to defend himself, the security chief raised her hand. "I'm kidding. Look, this whole affair with Starfleet and the captain has us all a little frustrated, probably because there's really not anything we can do about it. I've tried to keep it from affecting my work, and I'm sure Commander La Forge has too, but he deserves to know if you or someone else under his command is troubled. I think it speaks well of you and the others to be concerned. Have you tried talking to him about it?"
"I have not," he replied, "but perhaps you are correct in that I should approach him."
Vale nodded in approval. As Taurik had already said, discussing a problem with someone else helped to resolve the issue. At the very least, it sometimes made the problem seem as though it was not insurmountable.
Truth be told, she had not yet discussed with anyone else her own feelings over Starfleet's decision to send the Enterprise on this latest mission or the manner in which they had treated Captain Picard. Displaying anger over how the entire affair had unfolded did not seem to be the right avenue to take, even though she could easily have argued the justification for such an emotion. Disappointment, perhaps? Yes, that seemed more appropriate.
Her thoughts were interrupted by the pleasant aroma of Taurik's plomeek soup as the Vulcan brought a spoonful to his mouth and sipped it. The action caused her stomach to grumble, reminding her that her own meal remained largely untouched.
"Tell me something, Taurik," she said after eating a few bites. "What made you request a transfer back to the Enterprise?"
The Vulcan replied, "I had not yet had the opportunity to serve aboard a Sovereign-class vessel, and felt such an assignment would provide an opportunity to enhance my skills and experience. That the Enterprise-E was the first such vessel in need of replacement engineers was fortunate happenstance. I am most pleased to be a part of Commander La Forge's team once again."
Vale recalled from her review of Taurik's service record when he had transferred aboard that he had been posted to the Enterprise-D after graduating from Starfleet Academy. Following that vessel's destruction, he was one of several crew members to be transferred to other assignments. In his case, it was to the Utopia Planitia shipyards orbiting Mars. When the Dominion War started, he joined the crew of the U.S.S. Ilan Ramon, where he remained throughout the conflict. His transfer to the Enterprise-E had come only two months before the incident with the Juno.
Unable to suppress a humorless smile, Vale said, "Given what's happened, I bet you're regretting that decision now, huh?"
"Regret?" Taurik asked. "Our current mission will provide the entire engineering staff an uncommon opportunity to expand our skills, without the benefit of Starfleet repair facilities. It will be a most interesting challenge."
Vale could not argue with that. Part of her welcomed the coming mission, for at its heart was the embodiment of why she had entered Starfleet in the first place. It seemed like forever since they had been given a mission of pure exploration, and now they were traveling to a part of space never before visited for just that purpose. Under any other circumstances, the promise of discovery would be exciting.
Instead, thanks to the way Starfleet had seen fit to give them their new assignment, the entire undertaking left a sour taste in her mouth.
"Lieutenant," Taurik said, "before the Enterprise departed on this mission, Starfleet extended an offer of transfer to another assignment to any member of the crew who might want it. If I may ask: Do you regret not taking advantage of that opportunity?"
"No," Vale replied without hesitation. Though Starfleet had seemed to focus its attention, and its ire, on Captain Picard with regard to the Juno incident and the fallout with the Ontailians, practically the entire crew had felt that scrutiny in one fashion or another. Rumors had run rampant that remaining on the Enterprise in the wake of the affair was an almost certain deathblow to one's career.
Nearly two dozen members of the ship's complement had elected to accept transfers to other vessels or stations, but her check of the personnel files for those individuals revealed that most of them had been assigned to the ship for only a short time to begin with. Perhaps they had not been aboard long enough to appreciate fully the sense of family displayed by those who had served here for a much longer time. Maybe there were those in the upper ranks of Starfleet who had lost their faith in Picard, but most who had served under him for years still trusted him without reservation. Even though she herself had been aboard the ship for a short time compared with others, she still felt a sense of belonging unmatched by any of her previous postings.
"I've only been the security chief here for a couple of years," she said, "but I see no reason to leave now." In truth, she had not given the decision a moment's thought. In her view, there were no other captains in Starfleet, and no other crews for that matter, with whom she wanted to serve. Looking around the dining room and seeing the dozen or so crew members sitting at other tables, recognizing each of them even though they were assigned to departments throughout the ship, only reinforced her feelings: For better or worse, the Enterprise was still the place to be.
She might not like where they were going, or why, but if she had to go, then she was happy to do so aboard this ship and alongside this crew. Besides, if she knew Picard as well as she should even after her arguably short tour of duty, it went without saying that the captain would find a way to turn their current setback into an opportunity for redemption.
And there's no way I'm going to miss having a ringside seat for that.
## Chapter Nine
SETTING HIS PADD DOWN on the table before him, Will Riker raised his arms over his head, interlocked his fingers, and reached for the ceiling, welcoming the sensation as his back muscles flexed and stretched. That small motion, along with a deep cleansing of breath, helped clear his head and worked to shake off the fatigue that had been building steadily all afternoon.
Oh yeah, he chided himself. I feel like two slips of latinum, all right.
The task of reconfiguring the crew's duty rosters, to allow for ample free time as requested by Captain Picard while keeping the most qualified officers on hand across the day, had proven anything but simple. Even with the input of the department heads, it seemed to be taking forever. He wanted it done, though, so here he sat as he had for the past several hours, hunched over his data padd. He had forsaken his quarters for a seat in one of the Enterprise's dining lounges, but refused to break for anything more than a mug of raktajino—or had it been two?—until he was finished.
Tuning out any distractions from the comings and goings of crew members, he found himself pushing to complete the assignment in short order, just as he had done with all of his tasks during the last few days. Not that Riker viewed himself as typically lackadaisical when it came to his orders; on the contrary, he strived to be efficient and precise, not merely to please himself but to set a standard for the rest of the crew on how Captain Picard should be followed.
Riker stepped up his pace now because he felt that loyalty had been compromised, and not by any member of the Enterprise crew. No, it had been wounded by the elite of Starfleet Command, and that, more than anything, angered him.
For two-thirds of his Starfleet career, he had served as Jean-Luc Picard's first officer. During that time, Riker had watched his captain make life-or-death decisions and lead fragile diplomatic negotiations, all while continuing to revel in the wonder of the unknown.
Time and again, Riker had been invited to leave Picard's side and assume a command of his own. Each time, he had declined, feeling that he still had more to learn, and more to contribute, right here. His place, he continued to believe, was on the Enterprise.
He had tried to rationalize Starfleet's viewpoint, arguing with himself that his understanding of Picard was something he had honed through years of experience. Many Starfleet admirals obviously did not share that perception, most likely only gleaning a fraction of it from reviewing mission reports or hearing apocryphal stories at strategy sessions. Consequently, they failed to appreciate or really even comprehend just how fortunate the Federation was to have Picard as one of its representatives. Otherwise, the first officer decided, they would not be doling out to the Enterprise captain the most menial of responsibilities and effectively putting him out to pasture, sending him to graze in the galaxy's open fields as did the Alaskan caribou Riker had watched in his youth.
It's no way to treat any captain, much less my captain.
Sighing loudly, Riker tossed his padd onto the table. Leaning back in his chair, he said, "Computer, dim lighting in this area to forty percent."
As the illumination in the portion of the lounge he currently occupied grew softer and more relaxing, he heard a voice call out in mock disapproval. "That's not very conducive to getting any work done, you know."
Looking up at the new voice, one that most definitely did not belong to the ship's computer, Riker sat upright and smiled at the new arrival. "Hello, Deanna. I didn't see you come in."
Deanna Troi returned the smile, her dark hair framing her soft features. As she drew closer, Riker was sure he detected the faintest hint of the Risian perfume she liked to wear on occasion. It was a pleasing scent, which was why he had purchased the perfume for her in the first place.
"You seem fairly engrossed there," she said. "Still working out the rosters?"
"You guessed it," he said, gesturing for her to take a nearby seat. "I might've been done sooner, but I'm trying to rig things for everyone to make the most out of this relaxation time prescribed by the captain. I'm adjusting the three shifts into four and rotating them so that everyone has opportunities for downtime at varied hours of the day."
Troi smirked as she settled into a chair at Riker's right. "Sounds complicated."
"You'd know if you'd been working on your assignment as well."
"Oh, but I have," she said. "It's done and filed for your review."
His eyebrow rising suspiciously, Riker retrieved his padd. A few touches brought Troi's proposed duty-roster alterations to its screen. "Well . . . damn, Deanna, this is pretty sharp."
"I found it easier to cut required postings in each department and extend the three shifts by two hours each. That allows for twenty-hour breaks while offering the duty-time variations you are suggesting."
"And it gives people even more time off than I'd calculated," Riker said, nodding appreciatively. "Excellent work, Counselor."
"It's nothing we haven't discussed before," she said, her expression turning to one of understanding. "You would have hit on it, too, were you not so preoccupied."
"I'm not that preoccupied."
Troi offered a slight smile. "Will, even a non-Betazoid could sense that you're not all here right now."
Never could fool you, could I?
Reaching out, she placed one hand on Riker's forearm. The simple touch caused him to relax muscles in his neck and shoulders for the first time in what seemed like days. "I've asked before and I'll ask again," she said. "Are you ready to talk about it?"
Frowning, Riker began to turn away, but her presence had already succeeded in disarming him as efficiently as ever. He knew there was no one else on the ship—hell, in his life—to whom he would rather vent his feelings and frustrations at that moment. Still, he hesitated as he questioned whether she was seeking connection with him as his ship's counselor, his fellow officer, his friend, or his Imzadi.
Maybe it doesn't matter right now.
"Deanna," he said, "this whole situation can't be sitting well with you, either. What would I say that you don't already know?"
"I'm not seeking information, Will," she said, her voice continuing to soothe the edge on his nerves. "Just talk to me. If it'll help, I could use someone to talk to myself."
Nodding at that, Riker finally felt himself beginning to relax, the full effect of Deanna's presence asserting itself as it always had. "I'm not worried so much about my feelings over what's happened, but I am worried about Captain Picard. It might help me to know how he feels. What are you sensing from him?"
"He's hurting," Troi said, meeting his gaze. "It's as if he's mourning, in a way, for the way things used to be. I sense some embarrassment, as though he feels he's let the entire crew down or tarnished our reputations by his actions and decisions."
"Captain Picard has nothing to be embarrassed about," Riker countered. "This whole mess is so wrong for so many reasons." He realized his voice had risen as he spoke the last words, carrying across the lounge and attracting the attention of officers seated at other tables. Clearing his throat, he affected a weak smile to Troi. "Sorry."
"The captain doesn't seem to harbor any ill will against Starfleet or his superior officers," Troi said. "He understands this is the way things have to be. The captain would sacrifice his standing and reputation for any of us, Will. It's not a shock that he would do so for the Ontailians as well. I've never seen him place a boundary on his respect for any race or culture."
Riker nodded. "Well, no argument there."
"I think he just needs time to sort this all out for himself," Troi said. "Hopefully he'll eventually feel comfortable discussing the matter with me."
Smiling, Riker said, "You do have an uncanny ability to get people to talk."
"You, sir," Troi said, adding a touch of a purr to her voice, "are merely more susceptible to the power of suggestion than most."
"Now, hold on," Riker said, holding up both hands with an air of mock defensiveness, "Consider the source, here. When it comes to you, I . . ."
A voice over his combadge interrupted his train of thought. "Commander Riker, you have a priority subspace transmission on an encoded channel."
Tapping his communicator, the first officer replied, "Riker here. Who's the message from?"
"According to this," said the voice, which Riker recognized as belonging to the beta-shift tactical officer, Lieutenant Hines, "it's from the Federation ambassador to Qo'noS. Shall I route it to your quarters?"
Riker looked at Troi, raising his eyebrows and adopting a low tone of voice. "I guess news travels fast." He scanned the lounge and saw an unoccupied table with a computer terminal sitting atop it. "Lieutenant, route it down here, please. Riker out."
"I'll catch up with you later then," Troi said as she rose from her seat.
"Stick around," he replied, moving to the other table. "You know I'll only repeat it all to you over dinner."
"Oh, so now it's dinner we're having?"
Riker grinned as he sat down at the computer station and spun the terminal's flat-panel screen to face them both. He tapped a control and a moment later was rewarded with an image of Worf, dressed in his ambassadorial robes, filling the screen.
"Hello, Worf," Riker said to his former shipmate. "This is a surprise. Deanna is with me, too, so watch that language of yours."
"So I see, Commander." Worf's expression, as usual, showed no signs of amusement in response to Riker's remark. "You both appear well."
"Thanks, Worf," Troi said. "It's good to see you, too."
Riker asked, "And how goes your assignment?"
The Klingon's shoulders rose and fell with a protracted sigh. "It presents its share of . . . challenges. Dare I pose the same question to you?"
"Oh, we're doing just fine," Riker replied, not bothering to edit any frustration from his voice. "We're well on our way to where no one has bothered to go before."
"I am aware of the nature of your mission," Worf said. "It would have been more appropriately handled by a ship other than the Enterprise."
"Your powers of assessment are as sharp as always," Riker said. "It's a step up from all of us being sent to our rooms without supper."
The first officer saw his friend's expression cloud over, making him appear even more dour than usual. "I confess that I am concerned for the captain's well-being," he said.
"We all are," Troi replied. "I believe that he's coping as best he can under the circumstances, and that he's drawing strength from the support of his friends." Smiling, she added, "He might appreciate hearing from you sometime soon."
Shaking his head, Worf said, "When I was forced to accept discommendation from the Empire, the captain stood at my side and helped my family regain its standing. I promise you that I will do all in my power to support him in this time as he did for me."
"I never thought otherwise, Worf," Riker replied, smiling. "It never hurts to have a few friends in high places."
"Indeed," the Klingon said. "The right person in the right position is sometimes all it takes to turn a tide of opinion, after all."
As his friend's eyes bored into him even across the vast distance separating them, Riker felt any reply he might have made die in his throat. There was something powerful behind Worf's words, something the first officer could not quite identify.
Apparently sensing the awkward pause, Troi said, "Please keep in touch, Worf. It's always good to hear from you."
"I shall," the ambassador replied, a smile forming or the first time on his usually intimidating features. "I wish you good luck in the Dokaal sector. Worf out."
As the Klingon's image was replaced with the familiar starred oval symbolizing the United Federation of Planets, Riker played his friend's remarks over in his mind once again. Was Worf suggesting that he contact another starship commander to help stir some goodwill for Picard among the ranks? Was he of the mind that, to the right person, a leak of the facts regarding the demon-ship incident would work in the captain's favor?
Or, was it something else? Something more personal?
Prior to Worf's departure from Deep Space 9 for the Federation embassy on Qo'noS, Riker had contacted his friend to wish him well. During that conversation, as he beheld his former shipmate and the new direction his life was about to take, Riker remembered thinking about his own career and the choices he had made.
At one time on the fast track for command, Riker had been offered a ship of his own on three separate occasions. He had carefully considered each appointment, but in the end had declined them all and chosen instead to remain on the Enterprise. Even though he had garnered a distinguished service record while assigned as executive officer of the U.S.S. Hood, when the first offer for promotion was presented, he had opted to serve under Jean-Luc Picard. A tour of duty as first officer of the Federation flagship was not an opportunity to be dismissed lightly, after all.
He had spent more than a decade as Picard's second-in-command, far longer than would be considered normal for an officer of his age and accomplishments. He had seen men and women, younger than himself, continue to climb the career ladder, progressing to captaincies of their own. With that in mind, why had he not taken advantage of the offers presented to him and advanced his career along the accepted lines?
The answer, odd as it might be, was simple. None of the ships Riker had been offered was the Enterprise. They did not hold lineages and histories as storied as the vessel on which he currently served.
His decision to remain as Picard's first officer was the wisest move he could have made, so far as Riker himself was concerned. He truly believed that the value of all he had learned during the ensuing years under Picard's mentorship far surpassed even the experiences he would have acquired as captain of his own vessel. In Riker's eyes, there was no finer leader in Starfleet, and no one more deserving of his unflagging respect and support.
Still, had the time finally come for Riker to move on? Had Worf, with his mysterious words, suggested that the best way he could continue to serve Picard, to say nothing of Riker himself, would be to finally accept promotion and appointment to a vessel of his own?
How did we get to thinking about this, he wondered. These were thoughts that had not occupied his mind in . . . well, longer than he could remember.
"Will?" Troi asked, obviously sensing his unease. Blinking rapidly, Riker looked up to see the counselor staring at him from across the dining table. "Is something wrong?"
He shook his head to clear away the remaining wisps of his reverie. "No, no. I'm fine. Just lost in thought." Flashing what he hoped was an encouraging smile, he added, "Don't worry. I'm just tired, is all."
"Are you hungry, too?" Troi asked, the question enough to cause his stomach to grumble in response.
"Yes," he admitted, "for food and for company."
Troi's eyes met his and she smiled. "Good. Then we're in the right place."
## Chapter Ten
**Translated from the personal journal of Hjatyn:**
I HAVE TRIED on several occasions to craft this entry, failing miserably with each of my previous attempts. Much has happened since I was last able to record my thoughts in anything approaching an ordered manner. Even as I write this, I am still finding it difficult to accept the reality of our situation.
After watching the crisis build over the course of nearly an entire cycle, those of us living among the asteroids could only stand by as our homeworld entered its death throes. Huddled in our quarters, Beeliq and I sought solace in one another's embrace, watching in silence as the news feeds overflowed with images of horrific destruction. People begged for help and for the quakes to end. Some even prayed for the end to come just so that the suffering would stop. They cried for release and I wept as well, for it was all I could do for them.
Having continued to increase in number and force, seemingly with each passing day, the quakes' destructive power was nearly rivaled by the other effects they unleashed across the planet. Enormous tidal waves slammed into coastal and island communities, wiping away most if not all evidence of civilization. Avalanches of rock and snow caused similar devastation in mountain areas. People stranded in remote regions had no hope of rescue as emergency service providers, already bogged down by the problems facing them in the more heavily populated areas, worked frantically to assist the growing number of victims.
Law and order had deteriorated in the face of the calamity, replaced by anarchy as people took matters into their own hands. Whether trying to flee the cities for the relative safety of the outlying regions or taking to the streets in search of food or medical assistance, citizens and law-enforcement officers clashed in ever-increasing incidents of civil unrest. This chaos only served to further hamper an already overburdened emergency response force, which in turn caused even more discord among the populace. In short order, both sides had seized one another, forming a deadly embrace from which there was no escape.
And what of those fortunate enough to flee the planet? Though the final tally has not been made public, it did not require much effort to figure out that a mere four or five thousand people could have been safely transported from Dokaal using every available space vessel. Once the order for evacuation was given, ships traveled back and forth in a constant convoy, each trip taking weeks. Upon their arrival, evacuees were transferred to various outposts throughout the colonies in an attempt to spread the additional burden as equitably and efficiently as possible.
Then, it happened.
Our first indication came when the news feeds began to stop, not all at once and not immediately. Some journalists were able to report massive quake activity before their signal was lost. Others simply ceased transmission in mid-report, taken by apparent surprise. Regardless of how it happened, one by one, each of the broadcasts vanished in a storm of static.
The communications center for the mining colonies informed viewers that they were attempting to regain the lost signals from our home planet, but they knew, just as we did, what had really happened.
Any lingering doubt was quickly erased by the images transmitted by one of the last ships to flee the planet, escaping with its final group of evacuees mere hours before the final cataclysmic event.
The initial pictures of our homeworld sent to us by that last ship were reminiscent of those transmitted by the first travelers courageous enough to leave the confines of our planet. Just as it appeared in those low-quality views I remember from my youth, the planet was a beacon of peace and prosperity, of life and potential, as well as an anchor for those brave enough to venture into the vast unknown.
All of that was soon shattered as our world came apart.
It is an image forever burned into my memory. Captured with haunting clarity, the transmission from the rescue vessel dispassionately broadcast our world's final moments and the simultaneous deaths of the uncounted people that could not be saved. At first the planet seemed to collapse in on itself before splintering into billions of fragments, slung outward in all directions along with magma from the molten core. The core itself, now freed from the tremendous pressure at the heart of the planet, vaporized as it succumbed to the sudden vacuum, creating a kaleidoscopic display that only served to punctuate the awesome destructive power that had been unleashed.
Dokaal was gone.
In the immediate aftermath of the catastrophe, I considered those left behind to be the fortunate ones. At least for them, the suffering was over and they could rest. For those of us left behind, our battles were just beginning, with our first priority being simple survival.
Faced with the sudden influx of several thousand new inhabitants, adjustments have to be made to support them, to say nothing of the thousands of colonists already living among the asteroids. For the newcomers, their abrupt arrival means that they will have to undergo an accelerated regimen of inoculations in order to survive the omnipresent radiation surrounding the asteroid field. Without the medications, which in essence alter a person's body chemistry at the cellular level, no one can survive here. For workers normally assigned to the colonies, the series of injections is carried out during an acclimation period prior to their arrival, but the survivors of Dokaal do not have that luxury.
The challenges extend to our facilities, as well. Designed for short-duration assignments after which crews were rotated back to Dokaal, our outposts are not capable of sustaining us indefinitely without the massive enhancement of our support systems. Such efforts already were under way practically from the moment the emergency situation on our homeworld was revealed. Knowing we would soon be without the benefit of the regular logistical aid we typically enjoyed from Dokaal, supply shipments were stepped up in addition to the transfer of those selected for evacuation. Despite all that preparation, much work still remains.
Things once taken for granted, such as the availability of food and drinking water, replacement supplies and components required to maintain the colony's support systems—even the expectation of privacy—are just some of the first things that have been impacted by the emergency measures enacted following the disaster. Power usage already has been redistributed throughout the colonies in order to conserve resources. Two, sometimes three families are being forced to share quarters originally intended for a single group. The living areas occupied by those without families, already cramped and utilitarian in nature, have been reconfigured to support twice the number for which they were designed.
One advantage of living in an asteroid field is that there is no shortage of key resources. The mining colonies' ore-processing plants and other factories are ideally suited to converting raw material into finished products used to construct new outpost facilities and maintain our current structures as required by the community. Indeed, they had already been doing so since long before my birth. In addition to easing the burden of supporting our expanded population, it also offers constructive, meaningful work for a people whose entire existence had been predicated on toiling to provide for others.
Still, the work to make the best of our dire situation is being hampered on many fronts. Throughout the colonies, administrators and security forces are facing panic and uncertainty in the midst of the rapidly unfolding situation. Some of the colonists are inciting riots, and there have even been reports of a few deaths. I know the unrest is born of fear rather than anger, but that does not lessen its severity.
People are too scared to place their trust in the colony leaders, who are now the sole arbiters of organized civilization remaining to us. They are woefully unprepared for the new responsibilities that have been thrust upon them.
One step in the right direction, however, is a plan put forth by the administrators to better communicate with the rest of our people. Each colony's habitation section is to select a representative, who will in turn act as a liaison between their group and the administration, communicating information back to their respective group as well as giving voice to concerns and grievances filed by the citizenry. Beeliq has already volunteered to act as the representative for our group. With this and other initiatives being put forth by the administration as well as the people themselves, we might eventually achieve some semblance of routine or perhaps even something approaching normalcy.
Still, I believe that our survival will be an unending struggle.
## Chapter Eleven
"BRIDGE TO CAPTAIN PICARD." The voice of Commander Riker filtered through the intercom into Picard's ready room. "We're approaching the Dokaalan system, sir."
Looking up from the book he was reading, Picard smiled as he replied to the intercom. "Thank you, Number One. I'm on my way." After nearly four weeks of uneventful travel, the Enterprise had arrived. Now they could finally get to work.
Feeling the rush of anticipation at his first officer's report, Picard smiled as he closed the book in his hands and carefully laid the tome on his desk. Layered with adventure, intrigue, and a cast of characters that engaged him in the same way as the classical literature he preferred, the book had never failed to put him at ease on the rare occasions he could lose himself in its pages. Written nearly a century earlier and though clearly labeled as a work of fiction, it purported to be the "real story" of Earth's first encounter with the Vulcans.
Except, of course, he mused with a smile, that it didn't happen that way at all.
Commander Riker, with his penchant for the curious when selecting gifts, had replicated a copy of the novel for Picard as a birthday present shortly after the Enterprise's encounter with Zefram Cochrane in the twenty-first century. Given his and the crew's covert involvement with the legendary man's historic initial warp-speed flight as well as humanity's first officially recorded encounter with an alien species, the book was a particularly whimsical gift. Though he did not normally partake of popular fiction for his leisure reading, Picard had nevertheless found the story to be so engrossing that he had reread the book several times in the years since first receiving it.
When done well, he decided, fictional first contact is almost as exhilarating as the real thing.
Picard exited his ready room and stepped onto the bridge to hear Commander Riker issuing the order to slow to impulse power. As the ship dropped out of warp space, the captain turned his attention to the main viewer and saw the multicolored streaks of light revert to distant points of light against the black tapestry that was the space surrounding the Enterprise. Even after all these years, he never tired of that sight.
"Report," he prompted as he crossed the bridge, stopping in his habitual place between and just behind the forward conn and ops positions.
Rising from the command chair in deference to the captain, Riker said, "We've just entered the system, sir. Long-range scans show no signs of other vessel activity anywhere in the area, but that's not saying much."
"Explain," Picard said, frowning at the report.
Turning in his chair at the ops position, Data said, "Our sensors are encountering a great deal of interference which appears to be caused by low-level radiation emanating from the massive asteroid field orbiting this system's sun between the sixth and seventh planets. The radiation is a by-product of various minerals and ores comprising the bulk of the asteroids. It is an effect that will worsen as we move farther into the system."
According to information gleaned from the probe recovered by the Vulcan ship in 2151, the asteroid belt had played an integral part in the Dokaalan people's economy, with all manner of minerals and other raw materials being extracted for various uses. A great portion of the people's limited interplanetary spaceflight capability had been devoted to a burgeoning mining industry, with dozens of freighters and personnel transports supporting a network of colonies operating among the asteroids.
"Is the radiation a danger to us?" Counselor Troi asked, rising from her own station and stepping forward until she stood next to Picard.
From the engineering station at the rear of the bridge, La Forge replied, "I don't think so, Counselor. Even in a reduced state, our deflector shields should be more than enough to protect us. I'll know more once we've finished analyzing our readings and after I've consulted with Dr. Crusher. As for the sensors, I've already got my people working on retuning them to offset the radiation's effects. We won't be at full capacity, but at least we won't be blind."
Satisfied with that, Picard turned his attention back to the main viewer, where a faint gray and brown band was just becoming visible on the screen. The asteroid field, he presumed, watching the swath of rubble and who knew what else continuing to grow and expand as the Enterprise traveled deeper into the Dokaalan system.
"Considering the extent to which the Dokaalan relied on the asteroid field," he said, "their physiology must have possessed a natural resistance to the radiation." Looking to Data, he said, "Commander, the message recorded by the Dokaalan first minister stated that as many people as possible would be evacuated to the mining colonies situated among the asteroids. Have you detected anything that might indicate the presence of such settlements?"
Shaking his head, the android replied, "Not as yet, sir. With our compromised sensors, we will have to move deeper into the system before we can hope for reliable readings."
"Do you still think we might find something, Captain?" Troi asked.
"I honestly have no idea," Picard replied. "At the very least, we might find some remnants of their civilization, some clue as to what actually happened after the probes were launched and how survivors, if there were any, might have coped." Smiling slightly, he added, "We may as well make the most of our opportunity to examine all the possibilities. Wouldn't you agree, Counselor?"
Picard's orders for this assignment had not been terribly specific, owing in no small part, he suspected, to the nature of their issuance. Admiral Nechayev had sent him and the Enterprise to the Dokaalan system as a means of keeping them out of the spotlight for a time. The mission itself was simple, yet lengthy in duration, and Nechayev had therefore left the details to Picard. It comforted him to know that despite all that had happened, the admiral still trusted him to exercise his judgment, regardless of the task he was assigned.
Hours before they entered the region, long-range sensors had determined that the fourth planet, once the home of the Dokaalan people, had in fact been destroyed. Its debris had expanded in all directions to form a smaller, less dense asteroid field than the one blocking the Enterprise's path through the system. Essentially, their mission was completed, at least according to the letter of Nechayev's instructions.
However, the vagueness of the admiral's orders meant, to Picard at least, that he had a good deal of latitude in which to work. Why not exercise it, and see what else there was to learn here? Perhaps they could determine what actually caused the Dokaalan planet's destruction.
Moving to his command chair, Picard said, "Mr. Data, will you be able to negotiate the asteroid field even with reduced sensor capability?"
The android nodded. "Our navigational sensors and deflectors do not seem to be impeded by the radiation to the same degree as our defensive shields. It should be possible to augment their power sufficiently to provide the data I will need to guide the ship. However, I would recommend proceeding through the field with maneuvering thrusters only."
"I don't suppose you'd want to take the helm, sir?" Riker asked, a mischievous glint in his eye. "As I recall, you have a knack for this sort of thing."
It had been more than a decade since the Enterprise-D happened across a Promellian battle cruiser, derelict for centuries and drifting within an asteroid field not altogether different from the one they were currently approaching. It was soon discovered that a network of energy-draining devices had captured the ancient vessel and those same traps were threatening to ensnare the Enterprise. La Forge devised a plan using minimal power to maneuver the ship out of danger, and Picard himself piloted the vessel free of the trap.
Smiling at the memory the first officer's question evoked, Picard tugged down on his uniform tunic and settled himself more comfortably in his chair. "I think I'll allow Mr. Data the pleasure this time, Number One." Looking to the tactical station, he said, "Lieutenant Vale, please dispatch my latest status report to Admiral Nechayev." The admiral would be reading the report even before the Enterprise finished navigating the asteroid field, he guessed, thanks to the network of relay buoys deployed by the starship during the journey here from Federation space.
"Aye, sir," Vale replied. "Sending the message now."
At the ops station, Data finished entering a sequence of commands before turning to look over his shoulder. "I have plotted a preliminary course through the field, Captain, though I will almost certainly have to modify our heading while en route. It will take approximately nine hours to complete the crossing and will require me to assume control of the conn station as well as my own." Looking to Lieutenant Perim seated at the station to his right, he said, "No offense intended toward your own abilities, Lieutenant."
"None taken, Commander," Perim replied. "Are you sure there's nothing I can do to help?"
The android shook his head. "No, but thank you." He tapped a new series of commands to his console, and the ops panel before Perim's promptly went dark.
To the conn officer, Picard said, "You are relieved for the time being, Lieutenant." With a smile he added, "Take some time and rest that knee of yours. Dr. Crusher will be happy with both of us for that."
Smiling as she rose from her station, Perim nodded to the captain and said, "I'll be sure to inform her that she has you to thank, sir," before heading for the turbolift set into the bridge's starboard bulkhead.
The orders given, there was precious little else for the captain to do as his officers returned their attention to their various duties. Sitting quietly and observing the activity taking place around him, he reflected that it was almost possible to forget the reasons behind their being sent here in the first place.
Almost, he thought, but not quite.
"Now entering the asteroid field," Data reported without turning from his station. Having reprogrammed his own console in order to interface with both ops and conn functionality, the android was now using one hand each to control both operations. "Disengaging impulse drive and activating maneuvering thrusters."
On the main viewscreen, the effects of the radiation given off by the asteroids were beginning to assert themselves. The usually crisp display rendered by the viewer's imaging processor was now grainy and filled with static, jumping and wavering as lines crisscrossed the screen.
"Mr. La Forge," Picard said, "what is the status of your sensor modifications?"
Behind him on the bridge's upper level, the engineer replied, "Still working on it, Captain. The radiation levels are increasing at a faster rate than we anticipated, and it's overloading some of our sensor relays. I may have to reroute power from nonessential systems to compensate."
"At your discretion, Commander."
Beyond the haze of interference on the screen, the boundary of the asteroid field was now visible. Uncounted masses of rock, varying in size and shape, now dominated the image on the screen. Some of the asteroids appeared small enough to fit comfortably within the confines of the Enterprise bridge, while still others could themselves be small moons.
Then the image on the viewer cleared, and all the captain could see was a single, massive asteroid filling the screen.
"Data!" he snapped.
The android was already reacting to the looming threat faster than any living being could, his fingers a literal blur across the ops panel. On the viewscreen, the mammoth chunk of rock lurched to the left as the Enterprise swerved to starboard, shifting on its axis to avoid collision. Though Picard knew the ship's inertial dampening fields would guard against him being tossed about during the evasive maneuvers, he still gripped the armrests of his chair in an instinctive effort to hold on.
As the giant asteroid slipped away along the ship's port side, Picard wondered if the expression on his own face matched the look of relief on Riker's.
"No offense, sir," the first officer said, attempting to muster some of his trademark good-natured bravado, "but I'm really glad you let Data take the helm this time around."
* * *
True to his word, Data took just under nine hours to guide the Enterprise through the vast asteroid field, using the ship's maneuvering thrusters to alternate between their maximum speed and a slow crawl. Rather than subject himself to the tension merely watching the crossing would engender, Picard had instead opted for the solitude of his ready room. While he was able to relax somewhat within the room's soothing confines, attempting to read or even catch an hour or two of sleep had proven impossible. He was actually thankful when the call finally came.
"Data to Captain Picard," the android's voice said over the intercom, "we are nearing the inner boundary of the asteroid field."
"Thank you, Commander," Picard replied. As he exited his ready room a few moments later, he noted that Riker and the majority of the alpha-shift bridge crew had returned to their duty stations as well.
"Despite a few more close calls," Riker reported, "it looks like we made it through without any problems."
"Excellent work, Mr. Data," Picard said as he took his seat in the command chair. "Mr. La Forge, have you had any further success with the sensors?" He noted as he asked that the image on the main viewer had improved dramatically since he had last been on the bridge. While there was still static around the edges of the screen, the center of the picture was reasonably clear as it depicted the asteroid field now surrounding the ship.
"We're better off than we were, Captain," the engineer replied, "but still not one hundred percent. The radiation put out by the asteroids is too much for us to filter completely. As long as we're in the system, we'll have trouble with sensors and shields, as well as the phasers and the tractor beam and even the transporters. I've got my people working on it, but there's only so much we'll be able to do."
Picard nodded, unhappy with the report yet knowing that La Forge and his engineering staff were doing their level best to find solutions to the problems caused by the asteroid field.
"Captain," Lieutenant Vale called out from the tactical station, "our sensors are picking up low-level power readings from multiple sources. I'm attempting to ascertain locations now."
"Ships?" Picard asked.
"I'm not sure, sir," the security chief replied, "but if I had to guess, I'd say no. The power readings are inconsistent with any propulsion system I'm familiar with."
Riker turned in his seat to face the tactical station. "What about life signs?"
"Our scans are still being blocked to a large degree," Vale replied, "but we're detecting faint readings. Looks like somebody's home somewhere, sir."
Picard felt a surge of excitement at that. Someone was alive out here among the rocks. Were they descendants of the Dokaalan survivors, or merely others who had found the mineral-rich asteroid field to be of value?
"Mr. Data," he said, "coordinate with Lieutenant Vale and plot a course to investigate the power readings she's detected. Let's start in that fashion while we familiarize ourselves with the area."
"Captain," Vale suddenly called out, "I'm picking up a signal. It's on a very low frequency, and it's so weak I almost missed it."
"Is it being directed toward us?" Riker asked.
The lieutenant shook her head. "I don't think so, sir. I'm processing it through the universal translator now." Without further prompting, she keyed in another set of instructions, and static erupted from the intercom system. Picard flinched at the abrupt explosion of noise, but he thought he could hear words spread intermittently among the racket. Vale adjusted the volume so that it was tolerable, and several seconds passed as she worked to clear the channel and enhance the message.
Her efforts were rewarded moments later as the static abated and a male voice broke through. The audio was distorted, but the message was clear.
"This is Outpost Takir. Help us!"
## Chapter Twelve
PICARD ROSE from his chair, stepping forward until he stood directly behind the conn and ops consoles, as though the movement might bring him closer to the person pleading for aid.
"Our reactor coolant tank has ruptured, and our environmental system has failed. Send any available transports for evacuation!"
Picard's eyes locked on the viewscreen and the uncounted asteroids drifting all around the ship, as if he might locate the caller by sight alone. Somewhere out there, among all the tumbling and drifting rock, someone needed their help. Turning to Vale, he asked, "Can you locate them?"
The security chief did not look up as she replied, "Triangulating now, sir." After several moments spent adjusting and studying her console, she added, "I think I've isolated the source of the transmission. I'm reading a concentration of life-forms approximately three thousand kilometers from our present position."
"Relay that information to Commander Data's station," Picard ordered. "Data, lay in an intercept course and engage at our fastest safe speed."
Data keyed the instructions into his console and said, "Course laid in, Captain. Estimated time to rendezvous is four point seven minutes."
"Sensor readings are clearing, sir," Vale said. "The signal is coming from what looks like a sizable outpost constructed on the surface of a large asteroid. I'm picking up nearly four hundred life-forms there."
Digesting this new information, Picard asked, "Can you determine the extent of the damage they've suffered?"
"There are power fluctuations in what appears to be a fusion reactor core, consistent with a breach or leak. It might have been caused by a structural failure of some kind."
That meant the possibility of radiation-related injuries, Picard knew. "Notify Dr. Crusher so her team can prepare. We'll transport all survivors to the cargo bays for initial triage." Even if every single person on the mining outpost was in need of medical attention, the ship's cargo storage areas would provide more than sufficient room to accommodate them all, at least for the time being.
At the engineering station, La Forge said, "From what I can tell, Captain, they've got maybe a few hours, if that."
With preparations to receive the outpost victims under way, the captain could feel the energy of the people around him as they set to work, an almost palpable tingle on his skin. It was infectious, for he felt his own pulse beginning to quicken in anticipation of the task that lay ahead and the idea that after so many weeks of monotonous travel, they were finally going to do something useful.
Still, he knew that actually getting any victims to the ship still presented a bit of a problem. "What's the status of the transporters?"
The engineer turned from his console with a resigned expression, a feeling even seemingly communicated by the man's artificial eyes. "Sorry, Captain, but we're still having trouble tuning them to filter out the ambient radiation. Even with portable pattern enhancers, using them to transport people would be very risky."
It was not what he wanted to hear, but Picard also knew that it was useless to waste any more time concerning himself with an option currently unavailable to him.
Moving to the upper deck and the rear bridge stations, Riker said, "Geordi, could we maneuver close enough with shuttles to dock with an airlock or some other form of entry to the outpost?"
He watched the engineer scroll through screens of sensor data before freezing the image on one display monitor. As he moved closer to Riker and La Forge and studied the screen, Picard saw what looked to be a cylindrical protrusion extending from one rectangular section of the outpost structure.
"This is an external access point," La Forge said, "probably a docking port, the only one I can find. Our own airlocks won't match up perfectly, but we might be able to erect forcefields around the entrance." Turning in his chair, he added, "Captain, the radiation will affect any focused energy source we activate outside the ship. Even a forcefield will be risky."
"Is there any way you can compensate?" Picard asked.
The engineer shrugged. "If we move close enough to extend our shields to cover that section of the outpost, it might provide some additional protection. But the shields will already be compromised by the radiation before we extend them. Maintaining shield integrity could cause them to overload."
"We'll have to coordinate maneuvering shuttles to and from that docking port," Riker said, shaking his head. "And even then we can only take a handful of people at a time."
"Moving all those people is going to take a hell of a lot longer than a few hours," La Forge replied, "and that's if we even have that long."
Listening to his people, Picard was already ruling out the option of relying on shuttles. With only four fullsized shuttlecraft and eight smaller shuttlepods aboard, even using the new captain's yacht to assist in the evacuation would take entirely too long.
"Can we move the Enterprise herself close enough to link up?" he asked.
"We can do it using one of the docking ports along deck ten, sir," the engineer said, "but we'd have the same potential problems with our forcefields."
Picard nodded. "Continue your scans, Geordi. See if you can determine whether we can shut down the reactor." To Riker he said, "We'll move the Enterprise into position for direct docking. Number One, coordinate with Lieutenant Vale to handle security concerns for getting evacuees to the cargo bays."
Riker nodded. "Aye, sir."
As the first officer moved to put a hasty evacuation plan into motion, Picard returned to the bridge's lower level. "Lieutenant Vale, open a channel to the mining outpost."
When the security chief nodded to him and reported that the frequency was open, he said to the intercom, "This is Captain Jean-Luc Picard of the Federation Starship Enterprise. We have received your distress call and are moving to assist you. Please acknowledge if you are able."
There was a pause, and Picard flinched at the sharp crackle of static bursting through the com-system speakers before a bewildered male voice responded. "Hello? Who is this? Where are you?" To Picard, it sounded like the same person who had been transmitting the original distress message.
He said, "We are strangers here, but we are moving to help you. Please stand by."
"You mean . . . you mean you're not from the colony? Then where did you . . . ?"
Trying to keep the situation under some semblance of control, Picard cut him off. "We will be happy to answer all your questions once you are safely evacuated. Our ship is moving to link up with one of your external docking ports, and we will move you all to our ship. Are you able to organize your people for the transfer?"
Rather than a direct response, his ears were assaulted by multiple voices, all yelling within range of the audio pickup and all of them panicked.
"It's coming toward us!"
"Look at it!"
"Dokaa has damned us!"
"It's huge!"
Gesturing for the audio to be muted, Picard turned to Riker. "Number One, we need to act before the situation over there deteriorates any further. Are you ready?"
Looking up from where he and Vale were coordinating their plans, the first officer nodded. "I think so captain. We can at least get started, and adapt as necessary."
Picard nodded in approval. "Make it so."
* * *
This is almost too easy, Christine Vale warned herself. Not that I'm complaining.
Trying hard not to contemplate the narrow, utilitarian tunnel that was all that protected her from the vacuum of space, Vale instead focused her attention on the evacuation that was now well under way. That was fine with her, for the faster they could get the rest of the beleaguered miners off this godforsaken rock and safely aboard the Enterprise, the happier she would be.
Her duties had not given her the opportunity to inspect much beyond the airlock access passageway, but even a quick look at that had been enough to give her the basic lay of the land. The Dokaalan level of technology looked equivalent to Earth's during the late twenty-first century at the advent of the first long-duration colonies on the moon and Mars. The corridors here were cold, most likely due to insufficient insulation, and the air was stale thanks to the outpost's inoperative life-support system. The gravity also was lighter, only one-sixth that of Earth. Vale and her team were able to move about easily enough, but it required an extra bit of attention to keep from bounding around, so the lesser gravity wouldn't take them by surprise.
The tunnel and the chamber beyond were surprisingly clean and appeared well maintained. Vale had expected more clutter or other evidence of a people who had lived for an extended period of time within the confines of a habitat not intended for such use. This told the security chief that the Dokaalan had adapted to their situation with remarkable success and composure. These people would have amazing stories to tell, she knew, and Vale was looking forward to hearing them.
What do you say we get them out of here first?
Her thoughts were interrupted by the signal of her combadge followed by the voice of Lieutenant Jim Peart, her deputy chief of security. "Group three is aboard, Lieutenant." Static still corrupted the communications link, even though the two officers were separated at most by a hundred meters. "So far the forcefield is holding. Want to send another group?"
"Absolutely," Vale replied. "I'm sending them over now, Jim. Stand by to receive." Nodding to Melorr, the Bolian ensign she had placed in charge of the team at the docking-port hatch, she gave him the signal to commence transferring the fourth group of evacuees to the Enterprise. In response, Melorr opened the hatch to the access tunnel that connected to the rest of the complex and began to usher members of the next group forward. Vale had insisted on keeping the hatch closed in the event the forcefield protecting the airlock failed.
No sense taking any chances, she thought. Not now.
It had been a masterly feat of flying, as was usual for Data, to maneuver the mammoth starship into position to link up with the damaged mining outpost via its lone external docking port. That accomplished, Commander La Forge and his group of engineers had next rigged a supplementary power supply to the emergency forcefield generator for the airlock now connecting the ship to the mining outpost.
Even though the two hatches could not connect, owing to variations in their design, the forcefield acted to create a seal around the gap. La Forge had also taken the extra precaution of setting up a portable generator on the outpost's side of the airlock to augment the energy barrier. Though not entirely comfortable with these little feats of mechanical wizardry, Vale figured she could deal with them long enough to accomplish her current task.
"Thank you," a female Dokaalan said to her as she passed, part of the fourth group of evacuees being transferred to the ship. "You are a gift from Dokaa."
Understandably panicked by their situation, the Dokaalan miners had expressed only momentary concern upon meeting the strange beings who had come to their rescue. There was also the possibility that they were still a bit cowed by the appearance of the Enterprise beyond the windows of the outpost. Vale idly wondered if any of them might be fearful of a superior alien force coming to conquer their civilization.
Commander Riker had handled the initial contact procedures, where it had been learned that the people living both here and elsewhere within the asteroid field were indeed descendants of those who had survived the catastrophe that had claimed the Dokaalan's home planet generations ago. According to the miner who had acted as spokesperson for the group inhabiting the damaged outpost, there were even survivors of the original disaster still living among the population.
Vale's first thought at the revelation was that this race must have an incredibly prolonged life span, rivaling even other long-lived races like the Vulcans and perhaps even the Trill symbionts. The amazing trials they would have faced in the aftermath of such colossal tragedy boggled the security chief's mind.
Riker had done his best to put the miners at ease, his experience in such matters far exceeding Vale's. That addressed, the first officer had escorted the person in charge of the miners back to the ship, where he would meet with Captain Picard—after Dr. Crusher had examined him, of course. That left Vale and her security team in charge of the remainder of the operation.
Things had been made much easier thanks to the Dokaalan themselves. While she was sure these people would have countless questions, most of them at least had the presence of mind to hold them until the evacuation could be completed.
They can't be strangers to adversity, she reminded herself, or the need to react quickly to a situation.
Just like the image of First Minister Zahanzei from the centuries-old probe's recorded distress message, the Dokaalan Vale and her team found on the outpost were essentially humanoid in appearance. Their light blue skin was several shades lighter than the first minister as depicted on the visual recording, undoubtedly an effect of having lived for years inside cramped artificial structures and insulated from the natural light of the Dokaalan sun. Still, their skin and lack of hair made them look vaguely Bolian in appearance, but it was there that the resemblance ended. They were much taller and slight of build, and their skulls were shaped differently. Vale had to wonder how such large, lanky frames lent themselves to the rigors of subsurface mining.
That's probably the least of their worries, she thought. Descendants of those who escaped the disaster that had claimed their home planet, these people seemed to have tackled the challenge of surviving for centuries out here among the asteroids. Judging by the evidence all around her, the Dokaalan had hammered out an existence from the very lifeless rock that at one time had most likely been viewed as nothing more than a massive storehouse of resources. Now, that same rock had evolved to be all that separated these people from possible oblivion.
"Lieutenant Vale," Peart's voice called out over her combadge, "group four is evacuating now. No problems so far."
"Acknowledged," she replied, nodding in satisfaction. Yes, she thought, nice and easy. I could get used to this.
## Chapter Thirteen
"DR. CRUSHER? Dr. Crusher?"
Beverly Crusher turned away from the prostrate form before her and looked for the source of the voice calling her name from somewhere in the depths of cargo bay four.
"Over here!" she called out.
"Another group is coming," the voice replied, which Crusher now recognized as belonging to Alyssa Ogawa, her typically unshakable head nurse and a valued member of the Enterprise medical staff for more than a decade. Still, even she sounded as though she might be rattled at the prospect of more injured boarding the starship.
Sighing, Crusher shook her head at the news. The cargo bay had been turned into an emergency field hospital, helping to screen roughly one hundred Dokaalan requiring varying degrees of treatment. However, the evacuees were coming at a rate that she knew threatened to overwhelm the ship's medical personnel, or at least overrun the physical space of the large room. Other cargo bays were being converted and would be ready soon, but that did not aid her immediate situation.
There's nothing you can do about that, she reminded herself. So worry about the problems you can fix.
Brushing a lock of red hair from her face, Crusher moved to the next emergency treatment bed and activated its array of diagnostic sensors. The Dokaalan lying on the small bed was having difficulty breathing and was holding his abdomen, though there did not appear to be a great deal of blood. An internal injury, most likely.
"Temperature is 29.4 degrees Celsius," she said. "Is that even normal for you?" She was not surprised when the Dokaalan merely looked at her in confusion, and she patted him gently on the arm. "Don't worry," she offered in her best bedside-manner voice, "we're going to take good care of you."
"Dr. Crusher," Ogawa called out again. "The next group is arriving."
Without looking up from her work, Crusher replied, "Resume triage protocols and I'll be right there." Ogawa and the rest of the medical staff were more than capable of assessing injuries and quickly assigning treatment priorities in emergencies, even while under attack. Still, coordinating triage involving beings heretofore unknown to Federation medical science would have tested the mettle of even Starfleet's best physicians.
Using the peripheral scanner from her medical tricorder to examine the young man—she assumed he was young, anyway—Crusher compared the unit's readings with those of the dozens of patients she had already treated. This was most definitely not the way she preferred to practice medicine, knowing that everything they were doing to help these people was, for the moment at least, based purely on instinct.
While she and the rest of the medical staff continued their efforts down here, data about Dokaalan physiology was streaming constantly into the ship's computer with each patient they examined. Once the analysis of that data started to yield results, she would be able to determine what pharmaceuticals might be medically effective in stabilizing her new patients and easing their pain. For the moment, however, she was depending entirely on her own abilities, experience gleaned from years of treating new and exotic alien species, and a generous helping of good luck.
I guess it was too much to ask that the probe carried data files on Dokaalan anatomy and physiology.
Studying her tricorder's readings, Crusher now knew that her initial diagnosis of the wounded Dokaalan was correct. The sound of the patient's labored breathing was unmistakable. A lung had collapsed and what looked to be the equivalent of the spleen in a human had been lacerated. Those, at least, were injuries she understood and which could be treated quickly, here and now.
Retrieving a hypospray from her medikit, she set it to deliver a mild sedative that would let the Dokaalan sleep through his pain. The effects were immediate as she saw her patient's pale blue features relax.
He struggled to speak. "Th-th . . . thank . . . youuu . . . ."
"Of course," she said, leaning in as the Dokaalan closed his eyes again. "Be still, now."
Crusher gave silent thanks for the only advantage she truly enjoyed at this moment: a crumbling communications barrier. The Dokaalan probe's recording and other data files stored in its small onboard computer had provided enough of a language sample that Federation linguists were able to construct a competent protocol for the ship's universal-translation subroutines. Those programs were getting a workout now and being given the opportunity to improve with each passing moment as they sifted though the reedy, nasal tones of Dokaalan vocalizations and extrapolated them into a semblance of Federation Standard.
She did not need any of that, however, as she saw the smile on the Dokaalan's face before he slipped into unconsciousness, his anxieties eased at least a small bit at the realization that he was among friends.
As she gave the necessary treatment instructions to an assisting medic, she grabbed her gear and made her way toward the triage operation's makeshift staging area. Stepping past the small line of cargo containers that had been arranged to mark off the staging area, Crusher felt a sudden tug on her entire body, her legs wobbling in momentary disorientation.
Forgot about that, she realized as her legs took the extra second to reacquaint themselves to carrying her full weight. To accommodate the recovering Dokaalan, artificial gravity throughout the main section of the cargo bay's triage area had been reconfigured for one-sixth that of Earth, while remaining normal in the staging area so as not to disrupt the workings of the rescue teams and medical staff. Therefore, transitioning to and from the separate gravity fields always came as a bit of a shock.
At least we didn't have to change the air mix, too.
As she steadied herself and resumed her pace to the entrance of the bay, she saw the first of what appeared to be dozens of Dokaalan shuffling through the hatch, some not under their own power. As they entered the bay, they passed through a series of arches that had been jury-rigged to act as emergency bioscanners. The sensors were in turn providing preliminary readings that aided the medics with their initial diagnoses.
Denizens of the outpost seemed so far to be adults of two genders, Crusher noted, with none of them appearing particularly youthful or elderly. By their attire and demeanor, it was obvious that these people were used to living in nothing resembling the lap of luxury.
"Anything unusual?" Crusher asked Ogawa, who was busily tapping information into a padd.
The nurse's normally well-groomed hair was disheveled. She looked up and shook her head. "A few injuries, but unless someone's keeping something from us, these are all greens."
Following triage guidelines, medics were grouping the Dokaalan by the extent of their injuries and coding them by color: green for evacuees needing no treatment and who could be quickly moved to temporary berthing areas, yellow for those who suffered from injuries that did not threaten their lives, red for those who would die without immediate treatment—and black. Crusher had coded three Dokaalan as black so far, and that was three too many so far as she was concerned.
"Sounds great, Alyssa," Crusher said. "We could use the break. Make sure you get some rest and something to drink before the next group comes. You look like you need it."
"We all may need it," Ogawa said over her shoulder as she started toward the row of emergency bioscanner arches. "According to Lieutenant Vale and Commander Riker, we've only seen about a third of the Dokaalan on the outpost."
Crusher turned away to hide her grimace. It would not do for her subordinates to see her frustration at the current situation. Instead they had to see that she was in control and would continue to work no matter the difficulties that lay ahead. The Dokaalan were counting on them, after all.
She was moving from the reception area to inspect the status of their medical supplies when she saw Dr. Tropp, one of her three fellow physicians on board the Enterprise. "Hello, Doctor," she offered as he approached.
"Dr. Crusher," the Denobulan replied, holding up a dermal regenerator. "While treating our guests I have discovered that our regenerators aren't working as efficiently as I would like. I am trying to take advantage of our slight lull to see if I can recalibrate one of them, but I admit to having little success."
Since his arrival on the Enterprise, Tropp had shown an unwavering drive in his practice of medicine, and she quickly had come to appreciate his opinions and diagnoses. Additionally, he had demonstrated a keen interest in working with the younger and newer members of her team. Tropp seemed to enjoy functioning as the Enterprise medical staff's own continuing-education program, something that she welcomed considering that his people had served as biologists and healers even on the earliest of Earth's deep-space exploration vessels.
"I appreciate what you're trying to do, Tropp," she said, "but it might not even be possible to accelerate their healing. Let's hold off on that now, and focus instead on stabilizing the wounded."
"Oh, I heartily agree, Doctor," Tropp replied. "I'm just trying to anticipate what we might see later, given the circum—"
"Hey! We need some help here!"
Both doctors turned at the sound of the voice. Craning to see past the lines of Dokaalan at the bioscanning arches, Crusher spotted a pair of Starfleet crewmen ferrying between them what appeared to be a tarp—supporting a body. As the two physicians sprinted across the deck toward the new arrivals, she caught sight of another such makeshift stretcher, this one carried by a Dokaalan and an Enterprise crewman. Crusher peered into the tarp and saw that just what Tropp had anticipated was starting to come to pass.
"What happened?" Crusher asked as she activated her tricorder.
"Coolant pipes ruptured," said one of the rescuers. "These two got doused with the stuff. There were others, but . . ."
"I understand," Crusher said as she got a better look at the extent of the victims' burns. Swaths of their pale blue skin had turned a pallid gray. Wounds that should have been bleeding were cauterized. One of the Dokaalan was shuddering noiselessly, while the other was deathly still.
Tropp appeared at Crusher's side with the steering pads for an antigrav gurney in each hand. "Use these," he instructed as he passed the pads to a pair of medics. "It will help ease the pain from the burns." As the two victims were maneuvered onto the gurneys, the Denobulan produced his own tricorder and scooped out its handheld scanner.
"I cannot tell whether these are chemical burns or scaldings," he said as waved the scanner over one of the Dokaalan. "They may be both. Are there open beds in the red area?"
"Forget that," Crusher said. "We can't handle this down here." She tapped her combadge. "Crusher to sickbay. Activate emergency medical hologram."
A second later, a cool, reserved voice responded through her communicator. "Please state the nature of the medical emergency."
"This is Dr. Crusher," she said as she tapped commands into her tricorder. "I'm in cargo bay four leading a triage team, and I'm transferring the medical information for two patients that are being taken to you now. I need you to prepare sickbay for use as a burn unit. I need . . ."
"Wouldn't it be simpler to beam them directly to sickbay?" the hologram asked.
"Transporters are not cleared for use," she said. "Please just listen and don't second-guess me."
"Affirmative," came the hologram's crisp reply.
"Thank you," she snapped, trying to remind herself that the EMH was a valuable asset in situations such as this, when time was of the essence. The holographic doctor could instantly access the ship's medical database and retrieve all the information on the Dokaalan, allowing him to begin work immediately. Further, he would be able to work indefinitely without the need for rest, a unique advantage considering the extensive and likely time-consuming treatment he was about to provide to the three inbound patients.
Unlike many starship medical officers, who had opted for more advanced versions of the emergency medical hologram, Crusher had decided to keep the Mark I model EMH program after a test period to evaluate its successor. Though the newer Mark II version was unquestionably a superior product of computer software engineering, she had grown accustomed to the Mark I's personality and felt it better served her as well as her medical staff and, ultimately, the rest of the Enterprise crew.
That's not to say its bedside-manner subroutines still couldn't stand some additional adjustments, she thought.
"I need you to prepare beds as dermaline gel baths for burn treatment. Attune the support frames to monitor for signs of infection and also to continuously cycle the gel for debriding." She paused, unsure that the course of treatment even would work on the lanky beings.
"I am aware of the protocols, Doctor," said the EMH. "Is there anything else?"
"Yes, you can reduce the gravity in sickbay to one-sixth normal," Crusher said. "Dr. Tropp and a nursing team are on their way with the patients. I want you to make their stay as comfortable as possible." She actually thought she heard the EMH huff before responding.
"I'm a doctor, not a concierge."
Crusher bit her lip to stay an equally terse reply, then said, "I know you'll do your best. Crusher out."
As she helped a pair of nurses maneuver the gurneys toward the closest turbolift, Crusher's attention was drawn back to the scene of organized chaos unfolding around her. Seeing the steadily growing number of Dokaalan patients as well as Enterprise medical staff as every other crew member who had heeded her call for extra assistance working to maintain order and continue to the triage process, she could not help the silent plea that screamed in her mind.
Now, if we can just do our best . . . .
## Chapter Fourteen
GEORDI LA FORGE HAD WORKED on a variety of machinery over the years, from the latest in Starfleet engineering concepts to unique specimens of alien technology. Thanks to a bizarre set of circumstances, he had even traveled through time to the twenty-first century and assisted the great Zefram Cochrane in preparing the man's prototype warp-capable vessel for its maiden voyage. Given his wide range of experiences, it was a rare occasion when the Enterprise's chief engineer encountered a problem he could not solve eventually.
And it was those instances, such as the one he faced right now, that tended to frustrate him.
"What a mess," he said aloud, though there was no one else around to hear him. "We'd be better off jettisoning the whole thing and building a new reactor from scratch." Shaking his head, La Forge deactivated his tricorder and returned the unit to the holster on his waist, wiping sweat from his brow as he did so. It was hot down here, a by-product of the overworked reactor and its malfunctioning coolant system.
The engineer took another look about the cramped room, the control center for the mining outpost's main power reactor situated in a sealed chamber hundreds of meters below the surface of the asteroid upon which the complex had been constructed. He was seeking any clue, any hint that he might have missed which could help him and his team to bring the malfunctioning reactor under control.
Like the rest of the outpost, the control room was sparse in its construction and crammed from deck to ceiling with all manner of control consoles, tool lockers, and storage containers. Its most prominent feature was the large electronic status board mounted to the wall at the room's far end, which reminded La Forge of the large master situation monitor in the Enterprise's engineering section.
As for the remainder of the room, the bulkheads were composed of metal plating riveted and welded together, and La Forge could see crude join lines and other indicators of hasty repairs completed without the luxury of always having the correct replacement component or even the proper tool for the job.
The reactor itself, while possessing key differences from others he had seen, appeared to La Forge to be similar enough to those used to power the first manned interplanetary spacecraft from Earth in the early twenty-first century. Those power systems had been based on the concept of fusing deuterium and tritium with helium to create high-energy plasma that was in turn channeled by electromagnetic coils to generate thrust. The principle employed by the Dokaalan was similar, at least in this system's original design, though it appeared to have been adapted to work using minerals found in abundance among the asteroids. Even more remarkable was that the Dokaalan engineers had apparently devised a process that was free from potentially harmful residual waste such as neutron radiation, a dangerous by-product of the early Earth fusion reactors. All in all, it was an impressive piece of technical craftsmanship.
Not unexpected, La Forge conceded, considering the only tools and materials these people have are what they can fashion for themselves. Under the circumstances, the overall maintenance of the equipment he had inspected since arriving on the outpost was well above what he had expected to find.
Hearing footsteps behind him, La Forge turned to see Lieutenant Taurik and one of the Dokaalan specialists, a short yet stocky specimen named Rysatam, approaching the control center from the reactor room's main floor. As with the rest of the engineers sent from the Enterprise, the Vulcan was dressed in a tan utility jumpsuit ideal for the type of climbing and crawling activities the away team could be expected to perform during their investigation of the outpost's power center.
"What have you got, Taurik?" La Forge asked.
Holding up his tricorder, the junior engineer replied, "According to my analysis, Commander, the reactor's cooling system can be repaired, but I do not believe we can do so in the time remaining to us."
Frowning at the report, La Forge said, "Maybe we can rig up some kind of bypass and hook in a substitute cooling unit." The Enterprise stored such devices, which normally were used to regulate the operating temperature of mobile power generators employed by temporary settlements on newly established colonies. He judged that one or two of those would be more than sufficient to handle the cooling needs of the ailing Dokaalan reactor.
"That is not all," Taurik continued. "My scans show that several of the reactor's key components have melted or malfunctioned due to the excessive internal heat. If left alone, the reactor will continue to generate energy at uncontrolled levels until it overheats and explodes."
"What about switching to backup systems?" La Forge asked.
Standing next to Taurik, Rysatam replied, "The systems that allow us to switch from main to secondary power are among those damaged. Our automated connections are severed and the manual overrides are fused."
The chief engineer shook his head. "So there's no way to shut it off." He had arrived at a comparable conclusion after his initial inspection of the reactor systems, but he was hoping that one of the Dokaalan engineers or a member of his own team might provide another option after a more thorough examination of the problem.
"I am afraid not," Rysatam replied, his expression sullen. Like the other Dokaalan workers the away team had met upon entering the outpost, he had quickly over-come any anxiety at meeting visitors from space and eagerly embraced the Enterprise engineers, hopeful that the new arrivals might offer a solution to their problem that was beyond their own technical expertise.
Sorry to disappoint you, friend, La Forge mused, the thought laced with frustration at his team's apparent inability to provide that magical solution. Well, this certainly didn't take long.
Turning to Rysatam, Taurik said, "There is nothing more to be done here. Prepare your people for evacuation to the upper level. You will be escorted to our ship with the rest of the outpost residents."
The Dokaalan nodded gratefully. "Very well." Looking to La Forge once more, he added, "Do not feel bad, my friend. The situation was dire well before your arrival. We will adjust to the loss of equipment and matériel as we have in the past, but because you are here, many people will be saved who would have certainly perished without your assistance."
Not wishing to spoil Rysatam's goodwill, La Forge smiled as he wiped more perspiration from his brow. "I suppose you're right. That is the most important thing, after all."
As Rysatam turned to gather his people for the move back to the outpost's main level and Taurik notified the rest of the away team to gather their gear and head out, the chief engineer tapped his combadge. "La Forge to Vale."
"Vale here," the voice of the security chief replied a moment later. "What's the story down there, Commander?"
"The reactor's a hopeless case," La Forge replied. "With the coolant gone, some of the key mechanisms have melted, including the ones that would have let us shut the damn thing down. There's nothing we can do to keep it from overheating." The temperature in the room was continuing to climb, another sign that the situation was worsening, at least if the sweat running down his back was any indication.
"How much time do we have?" Vale asked. La Forge knew she was in the midst of coordinating the evacuation of all four hundred colonists from the out-post, so any information he could provide her would be helpful.
At his prompting, Taurik replied, "Approximately thirty-six point four minutes, Lieutenant."
"We might be able to bleed off some of the pressure that's building," La Forge added, "but we'd only be delaying the inevitable. We need to get those people out of here, Christine."
"We're working on it, Commander. Vale out." The connection severed, leaving the two Enterprise engineers alone in the sweltering reactor control room. Looking around, La Forge realized that the temperature of the reactor had risen to the point that his ocular implants could pick up the waves of heat emanating from its outer shell. They did not have much time, he knew.
"I guess that's all we can do, Taurik," La Forge said. "Let's get our people and head back topside."
"Commander, a moment if I may," the lieutenant said. Pausing a moment, as if to insure that no one else could overhear them, Taurik activated his tricorder and tapped a command sequence into the unit's small control pad. "During my analysis of the reactor I discovered an anomaly." He held the tricorder so that La Forge could see its compact display screen. "I detected evidence of structural fatigue in this control valve on the coolant system's flow regulator, but according to my scans, that is inconsistent with the age of the component in question."
"A faulty part, maybe?" La Forge offered. "Wouldn't be the first time a replacement part was defective, here or anywhere else."
Shaking his head, Taurik replied, "Were it the single valve I might be tempted to agree. However, I discovered similar indications in three other valves, each of which is an integral component in its respective part of the overall system. Further, the signs of fatigue would appear to be older than the valves themselves."
"That might still be explained by a defect in manufacturing," the chief engineer countered, but even as he said the words they rang hollow in his ears. What Taurik had shown him simply made no sense, given their surroundings. Like everything else he had seen in the mining out-post, evidence of meticulous care was visible everywhere, from the lack of dirt and grime on the surface of equipment to the cleanliness of the floors and walls and the absence of trash or detritus that might be expected to accumulate over a lengthy period. The Dokaalan obviously had learned early on that with only themselves to rely upon, the need for proper maintenance and diligence was essential, particularly with those systems charged with keeping them alive.
So what had happened to the coolant system?
His thoughts were interrupted by the sound of an alarm wailing outside the control center. It was quickly followed by several indicators on the room's main status board, all of them illuminating an attention-grabbing crimson red.
"Uh-oh," La Forge said as, one after another, more of the indicators flared to life. "I think we've got another problem."
Closing out the communication with Commander La Forge, Vale exhaled audibly.
Nothing's ever easy, is it?
Working with his team of engineers as well as a few Dokaalan technical specialists, La Forge had hoped to bring the rapidly overheating power generator under control. The outpost engineers had argued it as an impossible task, but La Forge wanted to take a shot at the problem himself with the equipment and technology at his disposal, which far exceeded that of the Dokaalan.
It had not been enough, apparently.
Thirty-eight minutes remained to them, according to Taurik's estimate. That was probably right on the money, considering the Vulcan's predilection for accuracy. It should be plenty of time, barring any unforeseen circumstances.
Most of the fourth group of evacuees had made the move to the Enterprise, with the fifth complement already standing by and awaiting their turn. Her security detachment had organized the miners into eight groups of fifty, with the most seriously injured to be transferred first. Those requiring immediate medical attention were already being treated by Dr. Crusher and her medical teams. To this point, Vale's quickly developed evacuation plan had worked just as she had hoped.
From what she could see now, though, things were no longer proceeding as smoothly as they had been only moments earlier. Ensign Melorr and his team looked to be working harder to keep the miners orderly and positioned for their transfer.
"What's the problem here?" she asked in her most authoritative security chief voice, mindful once again of the lower gravity as well as the need to keep herself beyond the reach of any of the miners as she stepped closer.
"This is taking too long," replied one Dokaalan. "The reactor will overload soon. Why are you keeping us here?"
Vale noted that the miner sounded more fearful than angry, and she briefly considered trying to explain the effects of the radiation emitted by the very minerals these people extracted from the asteroids. She figured they might comprehend the basic concept of forcefields, tractor beams, and perhaps even transporters, but she had no desire to stand on a ticking bomb discussing the details of current Federation technology or the problems it was experiencing here. There would be time enough for that later.
She hoped.
"There are safety concerns with evacuating so many of you," she said, hoping the simple explanation would be enough. "We can't do this without your cooperation, so I'm going to ask that you maintain your places and wait for instructions from my people. Rest assured that all of you will be evacuated to our ship and have your injuries tended to."
It was too much to hope that her words would completely ease the miners' worries, but Vale was pleasantly surprised when the anxious Dokaalan appeared to relax somewhat.
"The probes," someone else said from behind her, and Vale turned to see a female Dokaalan regarding her with what the security chief believed to be a quizzical expression. "You found one of our probes, did you not?"
Smiling, Vale nodded. "Two of them, actually, though many, many years passed between finding the first and the second." She caught herself before saying too much. After all, she didn't want to incite any more negative feelings by revealing that centuries had passed before Starfleet or the Federation had decided to send a ship to investigate the Dokaalan's plea for help.
That'd sure make them feel better, wouldn't it?
"Melorr," she called out, "get ready to send the next group." Tapping her combadge, she said, "Vale to Peart. We're sending the next . . ."
The rest of the sentence died in her throat as she felt the metal deck plating shudder beneath her feet.
"What the hell was that?" Melorr asked. There was no mistaking the nervousness in the Bolian's voice, and his emotion was mirrored in the faces of the Dokaalan miners. Some of them were moving from the orderly lines established by the security team and were pressing toward the airlock and the tunnel leading to the Enterprise.
The answer came from her combadge in the voice of the ship's chief engineer. "La Forge to Vale. The reactor cooling system is shot. Get those people out of here now!"
"What happened?" Vale asked, at the same time giving Melorr the signal to start moving the remaining miners out.
"It was cycling nothing but air after the coolant tank ruptured," La Forge replied, "and I couldn't bleed off enough pressure. According to our calculations, the reactor will go in about ten minutes. The chamber it's in might be enough to contain the explosion, but I don't know what it might do to the surrounding rock. I'd rather not stick around to find out."
Vale heard the engineer breathing hard as he talked, as though he was running. More than likely he and his team were scrambling to get back here. Turning around, she saw that her security people were frantically ushering the miners through the airlock and into the tunnel. By her count there were still more than two hundred people left to evacuate.
"Let's keep it moving," she called out, trying to keep her voice steady and confident. "We don't have much time."
Then time ran out as somewhere below her, too far away to see yet close enough for her to feel the effect, something exploded.
Vale threw out her arms, desperately grabbing for any kind of handhold as the deck pitched and disappeared from beneath her feet. Her hands closed around empty air and she slammed into the nearby bulkhead. Even with the reduced gravity, the impact was enough to make stars erupt in her vision and force the air from her lungs.
Groaning in pain as she slid to the floor, Vale realized the deck was still shaking underneath her. She was bounced along the unforgiving metal plating as she scrambled for something to grasp, finally clutching a safety railing mounted to the bulkhead. All around her, Dokaalan miners and the members of her security team were in similar straits, having been tossed about by the force of the explosion erupting from the depths of the outpost. Then the lights went out, only to be replaced seconds later by dimmer emergency lighting spaced at regular intervals down the length of the passageway.
The reactor, she thought, but had it overloaded faster than Commander La Forge had predicted? Had he and his team been able to make it out in time?
Before she could reach for her combadge in an attempt to contact the engineer, the corridor trembled around her once more. This time the motion was accompanied by an alarm klaxon wailing in the confined passageway.
"Breach!" someone yelled before Vale recognized the sound of air escaping through what could only be a tear in the metal plating forming the corridor around them. Where was it coming from?
Then the hiss became a howl as, less than ten meters away, the tunnel leading to the Enterprise disappeared along with the twenty or more Dokaalan who had been standing in it.
## Chapter Fifteen
"DETACH from the airlock! Now!"
The order came too late as, despite the Enterprise's inertial dampening field, Picard felt the starship roll with the asteroid. The massive hunk of rock shifted on its axis in response to the outpost reactor's detonation, taking the mining outpost and anything attached with it. While he was sure his ship could handle the stress of the sudden movement, the same could not be said for the more primitive structure of the outpost, let alone the fragile conduit connecting them.
His worst fear was realized an instant later as, displayed on the main viewer for all to see, the transfer tunnel sheared away, ripped from its moorings as easily as a banana might be peeled of its skin.
"The outpost has sustained a massive breach," Data reported from the ops position. "They are suffering atmospheric decompression."
The damned reactor had overloaded faster than anticipated, Picard realized. What had happened to cause the accelerated results? Where were La Forge and the rest of the away team?
Then there was no more time for such thoughts as something on the main viewer caught the captain's attention. Horrified, he watched as the metal cylinder that had been the tunnel spiraled away from the mining outpost. Falling apart as it did so, its disintegration revealed dozens of bodies flailing in the vacuum, people who had been in the tunnel when disaster struck. At least one appeared to be wearing a Starfleet uniform.
"Picard to transporter room one," Picard said as he tapped his combadge, "lock transporters on the people outside the ship and beam them to cargo bay four." He knew that Commander Riker was coordinating the influx of new arrivals from there, and that Dr. Crusher and her medical team were already on site, treating the wounded Dokaalan miners who had safely made the evacuation from the outpost.
"Captain," said the voice of T'Bonz, the transporter chief currently on duty, "that will require our shields to be lowered, and transporters are still being recalibrated by the engineering staff. They have not been certified for humanoid transport."
"I'm aware of the risks, Chief," Picard snapped. What choice did he have? Those people were dead if he stood by and did nothing. "Lock on and transport, now."
"Aye, sir," came the Vulcan's cool reply. "Energizing."
Knowing the interval of time required for a successful transporter cycle to complete, Picard silently counted off the seconds before prompting, "Bridge to cargo bay four. What is the status of the new arrivals?"
The lack of an immediate response filled his heart with dread, a feeling cemented a moment later when the voice of Commander Riker came through the intercom.
"Twenty-seven people have just materialized here, sir." There was another distressing pause before the first officer continued, and when he did Picard could hear the barely controlled trembling in his voice. "I'm afraid none of them survived."
Silence engulfed the bridge, broken only by the sounds of control consoles and computer interfaces dutifully processing their various instructions. Picard could only close his eyes and shake his head in momentary despair.
He had gambled, and lost.
It was not the first time he had given orders that resulted in the deaths of others, be they enemy combatants, members of his own crew or, on rare and horrifying occasions, even innocent bystanders. In all of those instances he was able, sooner or later, to divorce personal feelings from his command responsibilities. He knew that, after a time, even the pain he was feeling now would also pass.
Soon, he knew, but not now, and deservedly so.
"Thank you, Number One," he said after a moment, struggling to keep his own voice level. "Please keep me apprised of any new developments." As the connection severed, he stared at the viewscreen and the rapidly expanding cloud of debris cast off from the ruptured outpost airlock.
"Captain," he heard Troi say from behind him. Her voice trailed off, but he could tell from the inflection behind the single word that she wanted to say something to him about the tragedy that had just occurred.
That he had caused.
"Not now, Counselor." There would be time enough to examine and criticize his incorrect decision later. Now, somewhere beyond that turmoil depicted with cold indifference on the bridge's main viewscreen, people were still in danger. His people.
"Open a channel to the away team," he said. He had to know what was happening over there.
* * *
Still holding the guardrail, Vale managed to wrap her left arm around it and clasp her hands together before she felt herself pulled off her feet as the rapidly escaping atmosphere dragged at her body. Screams of terror echoed in the corridor as people were dragged through the air toward the jagged metal maw which was all that remained of the transfer tunnel on the other side of the airlock.
Hanging on for dear life, she had been powerless to do anything except watch as Ensign Melorr succeeded in securing his own hold on the airlock hatch's control lever, only to be struck by the flailing body of a Dokaalan miner. Both of them vanished through the open hatch, swallowed by the dark airless void.
They had been so close! Fewer than half of the miners remained to be evacuated when the tunnel had ruptured. Some of them had been lost to the hull breach but many were still here, holding on to anything that would support them.
The air was still rushing to flee the confines of the corridor, telling Vale that no emergency hatches or bulk-heads had closed deeper inside the complex. How much time did they have before this entire section of the out-post was completely without oxygen? No more than a minute, she guessed. Probably less.
"Enterprise to away team!" the voice of Captain Picard called from her combadge, but even his commanding tone was nearly lost amid the screaming wind. "Lieutenant Vale, are you all right?"
Vale ignored the call as she decided on a course of action. Her eyes already ached, the moisture in them beginning to freeze from the rapidly dropping temperature inside the corridor. Her pulse pounded in her ears and her lungs cried out for more oxygen. She had at most a handful of seconds left, and for certain only a single chance.
The hatch.
Twisting herself around so that she was now facing headfirst toward the open airlock, Vale released her hold on the guardrail. She immediately felt herself pushed toward the hatch by the force of the rushing atmosphere. Darkness beckoned beyond the open doorway, but she focused instead on the section of bulkhead just to the left of the hatchway. That, and the lever which would seal the hatch shut, the same lever that Melorr had grasped in a frantic yet futile bid for survival.
She felt the fingers of her left hand swipe across the cold metal of the bulkhead plating, sliding along its surface until they contacted the rough metal of the lever. Closing her grip around the protrusion, Vale swung her body back toward the wall, this time absorbing the impact with the soles of her boots. Now she was anchored to the bulkhead by a two-handed death grip on the control lever.
Already growing fatigued from the lack of oxygen, Vale ignored her increasingly blurry vision. She drew one final deep breath from the dwindling atmosphere around her before heaving down on the lever with all her remaining strength.
The lever slid down, and her effort was rewarded with the whine of the motors controlling the hatch as the reinforced metal door cycled shut. Only once it had closed completely, stopping the frantic flight of air from the corridor, did Vale release her grip on the lever and allow the outpost's reduced gravity to pull her to the deck.
Okay, let's hope we don't have to do that again anytime soon.
"Is everyone okay?" she called out, hearing her own raspy voice and realizing for the first time that her throat was parched, another effect of the sudden decompression. Voices shouted from farther down the corridor, and only then did Vale realize that someone had opened the other hatch, the one leading back into the main part of the outpost. Looking in that direction, Vale was happy to see so many faces, mentally patting herself on the head for her decision to keep that door closed during the evacuation process. With the exception of those nearest to the airlock when the tunnel had breached, it looked as though most of the remaining Dokaalan miners had survived.
The lucky ones, she mused.
"Enterprise to away team," Captain Picard's voice called out again from her combadge. "Report your status if you are able. Do you require medical assistance?"
The security chief tapped her communicator. "Vale here, Captain. I need a minute, sir. We're still picking ourselves up off the deck over here." Turning to look back up the corridor, she called out, "Alpha team, report."
A male human and a female Andorian wearing Starfleet uniforms, two of her four-person team, emerged from around the corner at the corridor intersection. Both of them looked haggard, no doubt as beat up and relieved to still be alive as she.
"We're missing six of the miners, Lieutenant," Ensign Zelev th'Chun reported, pausing a moment to wipe blood from a cut along her forehead. "The others have a variety of bruises and lacerations, along with a few broken bones. Nothing serious, though."
Standing next to Zelev, Ensign McPherson regarded Vale with an expression of dread. "What about Melorr . . . and Graham?"
"I saw Melorr fall through the airlock," Vale replied. "Graham was escorting the last group of evacuees to the ship when everything went to hell." She shook her head. "I don't see how he could have . . . I'm sorry."
McPherson and Graham had been teammates since the former's arrival aboard the Enterprise nearly five months earlier. Vale had paired them after it had become apparent during training exercises that the two worked exceedingly well together. Such cohesiveness and trust were vital components in developing an effective security team, but they also meant that the pain ran even deeper than normal when a member of that team was lost.
Placing a hand on the young ensign's shoulder, she said, "It's hard, I know. We'll pay our respects to Melorr and Graham when the time's appropriate, but right now we've still got the rest of these evacuees to get to safety."
She indicated the remaining Dokaalan miners who stood quietly a discreet distance down the corridor, regarding the Starfleet officers with expressions of pain and empathy. These people also had just lost friends and perhaps family members, but Vale was sure this was not the first time they had faced tragedy.
Maybe our being here will bring them some unexpected joy, Vale thought grimly as her people turned their attentions back to the task at hand, but so far we haven't given them much to be thankful for.
## Chapter Sixteen
WITH THE RESCUE and recovery operation now in the cleanup stages, Picard allowed himself a moment of respite. Dr. Crusher already was providing preliminary reports that with the exception of a handful of cases, most of the wounded Dokaalan miners would recover from their injuries.
Leaving Data in charge on the bridge until Commander Riker's return, the captain retreated to the sanctuary of his ready room. He waited until the doors closed before dropping onto the small sofa positioned across from his desk. Here, tucked away from the uncounted details that required his attention, he closed his eyes and finally tried to release the frustration he had been keeping at bay. Only now could he purge the emotions he had contained while standing before those he commanded.
His solitude was short-lived, however, interrupted by the subdued melody of the door chime.
"Come," he said, suspecting who would be there. His suspicion was confirmed as the doors parted to reveal Deanna Troi.
"Captain, we need to talk."
Picard scowled in response. "This is hardly the time, Counselor."
Standing before him, her hands on her hips and studying him with dark eyes that had always seen so effectively through his reserved veneer, Troi waited in silence. Picard knew she would do so until he acquiesced to her wishes—or the star in this system went nova, whichever came first.
"Please, sit down," he said finally, offering her the other half of the sofa. For a moment he said nothing else, instead closing his eyes and trying to lose himself in the soothing, ever-present hum of the Enterprise's engines.
When that failed him, he opened his eyes, realizing that Troi had spent that time studying his face before saying anything. "I sense your anger at what happened. Anger, guilt, and uncertainty that you acted correctly."
"You're damned right I'm angry," Picard replied, more harshly than he had intended. In a softer voice he continued, "I knew the transporters were a risk, but I gave the order anyway. Those people would have died if I hadn't tried, but there's a part of me that's already questioning the decision. Did I act too quickly? Was there another option I could have considered?"
"And was there?"
Picard shook his head. "No. Anything else would have taken too much time. Still, twenty-seven people died and I can't help second-guessing myself."
"I think we both know that your feelings are misplaced," Troi said after a moment. "By doing nothing, you would have automatically sentenced those people to death, and it's not in your nature to simply stand by and allow something like that to happen. You were compelled to act, and in a split second you made a life-or-death decision."
Exhaling audibly, Picard replied, "There's nothing grand about deciding on the only course of action available to you, Counselor."
"No, but it takes courage to actually take that action, especially when you know that you might fail. Anyone can make easy choices, Captain, but it's the true leaders who act on the difficult ones."
Picard smiled at that. It was not a verbatim quote from one of the many leadership texts he had read while a student at Starfleet Academy, but it was close enough. He had no doubt that those same words, in some fashion or another, appeared in one or more of the volumes Troi had been required to study during her own training. After all, it made sense that a counselor would have to be familiar with the many factors that molded a leader if he or she was to provide thoughtful counsel to such individuals, did it not?
"However," she continued, "I've seen you make hard decisions many times before, even when it entailed loss of life. Now, though, I sense something deeper about the frustration you're feeling."
Nodding, Picard smiled grimly. "Observant as always, Counselor." Rising from the sofa, the captain moved to the replicator set into the wall on the other side of the room. "Tea, Earl Grey, hot." When Troi shook her head at the offer of something to drink, he retrieved the cup and saucer that materialized before him and returned to his seat. Troi sat in silence, patiently waiting as he stirred the steaming beverage and took a tentative first sip. He knew that she would give him all the time he needed to reveal what was on his mind.
"It's important to me that this mission be successful in every way," he said finally. "Not for my own sake, mind you, but for that of the ship and the crew. Starfleet needs to see that they've made a mistake, and not because they elected to send us all the way out here. After all, contacting new civilizations is why I joined Starfleet in the first place. There's no shame in being assigned a mission such as this, but I need for those in charge to understand that treating it as a punishment is wrong."
"Admiral Nechayev doesn't feel that way," Troi countered. "She sees this as an opportunity for us to redeem ourselves in the eyes of Starfleet."
"And that's precisely the problem," Picard said, setting his cup down on the table next to the sofa, the tea having abruptly lost its taste for him. "The crew shouldn't have to redeem themselves for anything." Sighing, he continued, "But there's nothing to be done about that now. All that's left is to make sure that the crew carries out this assignment, and the ones after it, in their usual exemplary manner. That includes me, and I can't afford to make mistakes like the one I did today."
He saw Troi opening her mouth to respond and held up a hand to stop her. "I know we've already discussed that, Counselor, and I will get past today's events in time, but so many people are questioning whether I'm still capable of making the correct decision at the right time. On top of that, they've got me questioning myself."
"Captain, it's perfectly normal to question any decision, particularly the difficult ones," Troi replied. "Leaders especially are obligated to examine their choices. In my opinion, it's no different from what you've always done. That's a good thing."
Deep down, Picard knew that to be true, but it was still gratifying to hear such thoughts voiced by another. It went a long way toward easing the frustration and remorse he carried, as well as returning his focus to the mission that still lay before him.
* * *
If there was one thing Christine Vale hated more than a mission that had gone bad, it was the debriefing session that took place afterward.
"We were unable to retrieve the people caught in the decompression when the hull breached," Captain Picard said from where he sat at the head of the table in the observation lounge. "Twenty-five of the Dokaalan died as a result of exposure." Looking to Vale, he added, "Ensign Melorr and Ensign Graham were also lost. I'm sorry, Lieutenant."
Vale had prepared herself for the worst even after hearing that the Enterprise had attempted to recover everyone blown into space from the outpost airlock. The grim news was still painful to hear, especially considering everything the away team had been through. It had not taken long for word to get around about Captain Picard's daring yet disastrous attempt to rescue the decompression victims. Vale believed the captain had acted decisively and correctly, despite the results.
"Still," Picard continued, "you and your team did an exceptional job under very trying circumstances. Well done, Lieutenant."
After working his way back to the airlock, La Forge had coordinated with engineers on the Enterprise to reestablish a forcefield-protected conduit between the ship and the mining outpost. Thought not as stable as the original setup the chief engineer had devised, thanks to the damaged section of tunnel leading from the outpost, the jury-rigging had held long enough for Vale and her team to evacuate the remaining miners. They were all in the capable hands of Dr. Crusher and her medical staff, being treated in one of the seven cargo bays that had been reconfigured to provide the Dokaalan's reduced gravity requirements.
"The surviving Dokaalan have asked that we accommodate their request for a gathering in accordance with their beliefs," Picard said. "They have invited us to attend and wish to include a memorial for Ensign Melorr and Ensign Graham as well, to honor their sacrifice."
That made Vale smile a bit. Despite the dreadful circumstances surrounding their first meeting, the Dokaalan were making the effort to show gratitude for the efforts of the Enterprise crew on their behalf.
Seated to Picard's right at the table, Riker said, "In the meantime, we've sent a message to their main colony and center of authority with word that we've rescued their people. They haven't responded to our hail, but sensors show three small ships navigating the asteroid field in our direction."
"Any weapons?" Vale asked.
Leaning forward in his chair, La Forge replied, "Nothing our sensors picked up. Their technology is about two centuries behind us in most respects, even farther back in others. Unless they've got old-style nuclear warheads strapped to their ships and they somehow manage to fire one through our shields, I'd say we're pretty safe."
Vale nodded in relief at the report, noting as she did so that the engineer's right hand still was encased in a portable dermal regenerator. The device was working to restore skin tissue he had lost after inadvertently grabbing on to a pipe routing hot water through one of the mining outpost's lowermost sections. Like Vale herself, La Forge had managed to convince Dr. Crusher not to keep them in sickbay if at all possible. With so many things happening aboard the ship at the moment, neither the head of security nor the chief engineer could afford to be out of action for any longer than was absolutely necessary.
"Mr. La Forge," Picard said, "were you able to determine a cause for the reactor's malfunction?"
La Forge replied, "To be honest, I'm confused, Captain, for several reasons. First, the condition of several of the reactor's key components suggests that it was due to improper maintenance or maybe even negligence."
Waving one hand in the direction of the lounge windows and the asteroid field beyond, Riker countered, "They've been living out here among these asteroids for over two hundred years. Maybe the reactor was just old and they'd run out of spare parts to keep it running properly? It could have just been a matter of time before the thing blew."
"That could be," the engineer said, "but compared to the rest of the place, it just doesn't make sense. That out-post was as well maintained as any starbase I've seen. There's something else, too. Based on the condition of the reactor when we found it and after figuring out the rate of heat and pressure buildup, Taurik was able to calculate how much time we had left before it overloaded, but it went early. Almost seven minutes early. While I don't doubt that I could have made a mistake with those calculations, I don't think Taurik could."
Vale agreed. After all, Vulcans possessed far greater mental discipline than humans, particularly in the areas of mathematics and the memorization and recall of a wealth of information. Computing complex formulas without benefit of computer assistance presented as much difficulty to the typical Vulcan as remembering her security access code was for Vale.
Okay, bad example.
"Was there some sort of other systems failure you hadn't anticipated?" Picard asked.
"Nothing we detected, Captain. So far as we know, we had enough time to get the rest of those people off safely."
Her brow creasing in concern and not liking where her gut was taking her, Vale asked, "Are you suggesting this wasn't an accident, Commander?"
Sighing, the engineer frowned and shook his head. "I really don't know what to think. If these people have been out here all this time, then the only way they could've made it this far is by working together and trusting each other."
"There may be internal political or other machinations at work within this community of which we are not aware," Picard said. "For all we know, they may have splintered into factions and are openly at war with one another. We'll have to proceed with due caution until we make contact with their representatives of authority and learn more."
Nodding in agreement, Picard turned his attention back to Vale. "Lieutenant, have your people reported any problems with the Dokaalan miners we rescued?"
"No, sir," Vale replied. "So far everything's been uneventful. The Dokaalan have been surprisingly receptive, both to the care provided by Dr. Crusher and her team as well as to us, in general, I mean."
She had not participated in many first-contact situations, but on each of those rare occasions the party being contacted had always expressed wonder and, yes, even awe at meeting a race of beings from another world. While the Dokaalan miners had responded with some of that same amazement, relief at being rescued had quickly eclipsed those initial reactions.
Now that they were safe aboard ship, however, the miners' questions were starting to spill forth about who their benefactors were, where they came from, how far they had traveled, and so on. It was actually quite uplifting to see the happiness on the faces of the Dokaalan. She hoped the rest of the community would be as receptive to the Enterprise's arrival as this group had been.
"Bridge to Captain Picard," Data's voice interrupted the conference via the ship's intercom, "the three Dokaalan vessels are approaching our position. Estimated time to rendezvous is three point six minutes."
"Thank you, Commander," Picard replied as he rose from his chair. "I'm on my way." To the officers assembled around the conference table he said, "Meeting adjourned. Thank you all. Number One and Lieutenant Vale with me, please."
Here we go, Vale thought as she fell in behind Commander Riker and headed for the bridge. As she moved to her tactical station, she looked to the main viewscreen and saw three ships arranged in a tight triangular formation with each of the vessels on the same horizontal plane. She guessed the configuration to be effective for navigating the asteroid field.
As for the ships themselves, they were spare and utilitarian in design, essentially rectangular in shape with a pair of engine bells mounted at their rear. With the viewer's current magnification and resolution Vale could actually see the rivets holding the hull plates together. What looked to be a cockpit was the most prominent feature of each vessel's front, and she could also see people moving inside the transparent canopies.
"Hail them, Lieutenant," Picard ordered.
Vale entered the necessary commands and replied, "Channel open, sir."
A moment later, the image on the viewer changed from the three ships to that of an aged Dokaalan. Standing stoop-shouldered, his withered and pale blue skin etched with uncounted wrinkles, he was dressed in regal robes, richly colored in maroon and gold, which hung loosely from his emaciated frame.
"My name is Jean-Luc Picard," the captain said, "of the Federation Starship Enterprise. We come in peace on a mission of exploration."
The Dokaalan's features brightened at the introduction. "So it is true then. Our message from long ago has at last been answered." Bowing formally to Picard, he added, "Greetings. I am Hjatyn, first minister to the people of Dokaa."
## Chapter Seventeen
**Translated from the personal journal of Hjatyn:**
FOR THE FIRST TIME in many years, my hand is shaking as I write this. I am actually nervous!
I know that my upcoming inauguration as first minister should be a time of celebration, not discomfort. Were Beeliq here, she would surely tell me the same thing.
While I have served the people of Dokaal in many capacities during my life, this is by far the most important position I have ever entered. In another time and place, a first minister would have commanded prestige and even celebrity, but those times are long gone. Now it is above all else a position of immense trust and, perhaps more importantly, of hope.
As I have written in these pages before, I did not set out to be a leader, at least not in any official capacity. I realize that my role as a teacher placed me in a position of leadership, but that was in the context of molding young minds with the knowledge they would need to succeed in their own lives. Though I had always believed that to be a noble goal, I never held any illusions that my influence would extend much beyond those few precious hours in the classroom.
That all changed when Dokaal was destroyed, of course. One of the first things realized by those of us who escaped the tragedy was that in almost every way, life as we knew it had ended just as it had for those we were forced to leave behind. If we were to have any chance of survival, we would be required to examine every aspect of our existence and make whatever alterations were required for the greater good.
As for myself, I have my wife to thank for my change in thinking.
The constant growth and change within the colonies brought with it all manner of challenges. New communities formed among the different settlements, some based on the various nation-states that once comprised Dokaal as well as other factions created out of the necessity to share resources and facilities. Beeliq wasted no time wading into the quagmire that was to become the new guiding force of our people, taking on the role of liaison for our group. Her former position as assistant to our colony's administrator gave her a voice already known to those bearing the mantle of leadership, and she used it to great advantage. Every day, she and her peers worked to insure that the citizens and their concerns did not become lost in the ongoing shuffle merely to survive out here. She took the concerns of the people she represented directly to the seats of power, lobbying for better living conditions and better use of our resources.
When colony procedures called for the selection of new group liaisons, my wife was chosen time and again, usually as the result of a nearly unanimous vote. Even when she contracted her illness and her health began to deteriorate, she refused to step down from the position I and others had entrusted to her. I tried to help her as best I could by assisting her in carrying out her responsibilities, and along the way I managed to learn the ins and outs of the constantly evolving politics of our new society while earning the confidence of those my wife represented.
It was a confidence that was sorely tested when Beeliq's illness finally took her from me. Though she had left a void that could never be filled, not only in my life but in our community as well, many felt it appropriate for me to carry on in my wife's stead. I was hesitant, unconvinced that I would be able to perform at the same level as she had, but the faith of those she had once led ultimately overcame my uncertainty.
I am grateful for that support, which has remained resolute over the years as I found myself taking on even more duties and rising to higher levels in the new government. Without that trust and confidence, I would never have been able to advance from representative to a member of the Zahanzei Council, to say nothing of the office I am about to enter today.
Were she here, I have no doubt that Beeliq would be the one about to assume this most awesome of responsibilities. Fate has conspired to prevent that from happening, instead leaving me to take on the work for which my wife seemed destined. I can only hope that, as I pledge to exercise my new authority to the best of my ability and with the well-being of all my fellow Dokaalan as my foremost priority, her strength and passion will continue to guide me.
## Chapter Eighteen
WATCHING THE ELDER Dokaalan wander the full course of sickbay for what must have been his tenth time, Beverly Crusher felt a bit of a vicarious thrill. She had experienced a similar rush decades ago when a layover at a space station or planet allowed her to turn her young son loose in a toy store. She could not help but smile with some pride as her visitor puzzled over a diagnostic bed, turned a hypospray over and over in his long blue fingers, or showed a flash of utter amazement over the variety of equipment at her disposal.
He had made his way around her domain for the better part of an hour, checking on her—now their—handful of Dokaalan patients, and only occasionally breaking the silence with a question. Crusher stood by, keeping a professional distance while letting him silently drink in as much of the environment as he desired. The Dokaalan healer's reactions were not unlike her first inspection of a starship's medical facilities, and she let herself just enjoy this experience enough for both of them.
In response to the toll the Enterprise's normal gravity would have taken on the Dokaalan's body, Crusher had asked engineering to provide her with an antigravity work sled. Designed for use by maintenance workers operating within the ship's network of turboshafts, the chair was capable of carrying a person and an extensive toolkit. It also made for a more than passable wheel-chair, which the Dokaalan healer had quickly learned to operate before spending the ensuing hour driving around sickbay.
"Dr. Crusher?"
Looking up from the diagnostic monitor positioned above the patient she was examining, she replied, "Yes, Healer Nentafa?"
The tall, hairless Dokaalan moved the antigrav chair closer. "Forgive me, I must seem a nuisance to you."
Crusher waved the notion away. "Hardly," she said, still very thankful that a physician had been among the Dokaalan delegation that greeted the Enterprise following their rescue mission to the mining outpost. Within an hour of his arrival, Nentafa had assessed her diagnoses on more than three dozen of the wounded and even corrected her on a few of them. Advising her staff, he had helped to make short work of cases that had stumped Crusher, ones that she feared would turn for the worse despite her best efforts. Thanks to him, the bulk of the outpost survivors had already been released from treatment and sent back to the cargo bays to await transfer to the Dokaalan's central habitat and the Enterprise's sickbay had seen its patient numbers dwindle down to the five Dokaalan currently occupying beds, those most seriously burned or otherwise injured.
"You are most gracious, Doctor," Nentafa said. "I was wondering how you are insuring my people get the nutrients they need while they are unconscious."
Before she could respond, a medical scanner monitoring one of the Dokaalan beeped for Crusher's attention. Walking over to the patient's bed, she tapped the unit's keypad to silence the alert.
"We administer a nutritional supplement by hypospray on a regular schedule," she said a moment later. "Our computer analysis of your people's physiology helped us determine what vitamins and compounds needed to be replenished each day, so we formulated the supplement accordingly." Studying her patient's diagnostic readout, she noted that he was slightly feverish and adjusted the Dokaalan's antibiotic dosage and fluid intake accordingly.
"Ah . . . of course," Nentafa said, hesitating as if lost in thought. "I cannot keep from thinking that had this situation been reversed and our people had been your rescuers, our resources would not have enabled us to be so helpful so rapidly. Allow me to be a bit . . . overwhelmed by it all."
"No need to explain," the doctor replied. "You're not the first to get a crash course in Federation technology like this. And, if I may, your people strike me as very resourceful and capable given your way of life. From what I understand, the Dokaalan have a lot to be proud of."
Nentafa smiled and said, "We do our best."
She followed as he turned his chair and made his way to another diagnostic bed, hoping to ease any concern he might have for the patients' recovery. While Crusher had three fellow physicians on board as well as a complement of medical technicians and nurses on whom to rely, she sensed that Nentafa thought himself as alone in his responsibility for the more than four hundred Dokaalan displaced from the outpost.
After helping Enterprise engineers to reconfigure the cargo bays as living quarters for the Dokaalan temporarily residing in them, and even suggesting changes in food replicator programs to better meet their dietary needs, Nentafa continued to move back and forth between the cargo areas and sickbay, almost hovering over his patients. Crusher could not fault the Dokaalan healer for his diligence, as she knew she would act in the same manner if she faced similar circumstances. She hoped the Dokaalan healer would be more at ease upon their arrival at his people's central habitat complex, situated well within the asteroid field the Enterprise now traversed.
Nentafa leaned over the bed, peering closely at burns and wounds covering the limbs of an unconscious Dokaalan suspended and bathed in dermaline gel. The gel's pinkish hue lent the patient's skin an unnatural color and tended to mute the unsightly nature of the injured flesh beneath it. "This is miraculous, Doctor. Her skin appears to be mending at an unbelievable rate, and I see no evidence of residual scar tissue."
"Dermaline is a wonderful aid to the healing process," Crusher replied, "and we've been having better luck with everyone's dermal regeneration sessions than we hoped initially. They seem to be progressing very well, and no, there should be no scarring when we're done." Examining the patient's wounds, she was satisfied that their healing was progressing normally. After checking the diagnostic readout above the patient's head, she added, "There's been some problem with fever and other lingering aftereffects, but nothing we can't treat easily enough."
"Well, all I can say is . . . praise Dokaa," the elder healer said. "There is no doubt in my mind that you were led to us by providence. For visitors to chance across us is indeed astonishing, but for someone with the knowledge and ability to come and save our people at a time of crisis is nothing short of divine."
"We're glad to be of service," she said, more than a bit uncomfortable at the gushing praise. "Besides, you haven't seen anything yet. If you get the chance to travel back with us, I'm sure the entire Federation will be ready to welcome you with open arms."
"I am so intrigued by the idea of your Federation," Nentafa replied, his voice seeming to shed some of its earlier weariness. "It includes how many races?"
"More than one hundred fifty planets and societies have allied with the Federation over the course of two centuries," Crusher said. "And we've made contact with hundreds of other races who are not members."
"I would think that everyone would like to be a member of your Federation," the Dokaalan said.
"You'd be surprised, then," Crusher said, smiling knowingly. "There are strict requirements that a society must meet to become a member as well, and it's not so amicable a galaxy we live in beyond the asteroids."
"Ah . . ." Nentafa's words trailed off for moment as he considered her words. "Our people learned quickly to set aside squabbles. It was necessary for our survival. We also learned to compromise, to make the best of every situation, to use every resource to its fullest and waste nothing, to follow direction and to make choices that sometimes seemed impossible."
"You became fighters," Crusher offered. "You learned how to battle against incredible odds. That's apparent in this sickbay today, Nentafa."
"You flatter us, Doctor," he said. "In our lives, we have known no other way."
She noticed Nentafa reaching up to massage the side of his head, closing his eyes as he did so. It was obvious to Crusher that the healer was feeling the effects of fatigue. Putting her hand on the healer's shoulder, she said, "Why don't you get some rest? My staff can monitor your people and report to you as often as you like."
"Rest?" Nentafa seemed to laugh at the notion. "How can I rest when I have such an unparalleled opportunity to learn right here before me?"
Almost as if on cue, the doors to sickbay slid open to admit Dr. Tropp and, two steps back, Data, each at a brisk pace. The Denobulan nodded curtly at the pair as he made his way to a supply cabinet. Data, seeming to do his best to appear courteous, mimicked the physician's head movement precisely, eliciting a quiet laugh from Crusher.
"Your interests are well timed, Nentafa," Crusher said, raising her voice enough to be heard by Tropp, "as our best instructor in all things medicinal just walked through the door."
She saw Tropp stop at the cabinet, his chin sinking to his chest with a sigh. "I appreciate your show of confidence in my abilities, Doctor." Indicating Data, he added, "But being in charge of this . . . er, student . . . while performing my other duties is taxing enough."
Wide-eyed to the point of seeming almost peppy, Data turned to speak to Crusher. "Dr. Tropp has been indulging my interests in learning more about the Dokaalan. He has allowed me to follow him and observe his treatment procedures, and I have asked my questions while he works."
"Many questions," Tropp said, nodding and using a polite smile to cover what Crusher imagined was a set of gritted teeth. "So if I might defer a discussion with Healer Nentafa to a time when I could devote my undivided attention to him?"
"Absolutely, Doctor," Crusher said as a thought crossed her mind. "In fact . . . maybe guiding Healer Nentafa would be a task better suited to Mr. Data."
"It would?" the android asked.
"Oh, my, it would," Tropp practically shouted. "I think that's a tremendous idea!"
"Yes, Data," Crusher said, trying not to fumble her effort to give Tropp the break he obviously sought. "Nentafa has expressed a great deal of curiosity about the Federation, our level of technology, and the known races of our galaxy. Given your level of knowledge on all those topics, I think you would make the perfect tour guide."
"I would be happy to assist the healer in his research," the android replied, cocking his head a bit as he considered the offer, "if there is no objection from Doctor . . ."
Data turned to address the Denobulan, whose foot Crusher glimpsed in the corridor for an instant as the door to sickbay closed behind him.
". . . Tropp?" Data finished.
"He seemed to be in quite a hurry, Data," Crusher said. For a moment, she worried that Tropp's departure might offend the android in some way before remembering that for the first time in years, he no longer had a sense of pride to bruise.
Lucky him.
"So," she said, "would you like to help Nentafa in his studies? Along the way, he could tell you more about his people, so you'd be helping each other out."
"Certainly, Doctor." Turning to Nentafa, the android said, "Sir, would you care to begin in our stellar cartography department? I could plot out the worlds of the Federation for discussion in the order of their admission. Or, perhaps you might be interested in a visit to one of our holodecks, where I could show you reenactments of milestones in the history of the Federation. If that does not appeal to you, I could set up a comprehensive data-base review of known races, their physiological characteristics, and their important contributions to technology and culture."
It was a physical effort for Crusher not to laugh openly as she watched Nentafa's jaw drop and he tried to sort out the myriad of educational options being made available to him. Data was definitely cruising at his usual warp nine today, she decided, and the poor Dokaalan healer was about get the ride of his life.
"Partaking in all of that would seem to require a great effort," the healer said after a moment. "How in the name of Dokaa do you have time enough to manage it all?"
Stepping forward, Crusher said, "Data is a unique being, Nentafa. He's an android, and one of the most so-phisticated examples of technology you're bound to encounter."
The Dokaalan drew a breath, his jaw open as he maneuvered the antigrav chair toward Data. Slowly, he reached out with one long-fingered hand to stroke the android's cheek, pressing two fingertips to it. "You are a machine?"
His head tilting to the right in his usual inquisitive manner, Data answered, "That is correct."
Nentafa's brow furrowed as he studied Data's face. "A sentient machine?" he asked.
"Yes," Data said. "I was created forty-three years ago by Dr. Noonien Soong at the Omicron Theta colony approximately eight thousand, two hundred and fifty-five light-years from our current position."
"Ah," Nentafa said, pulling his hand back. With a smile he added, "You, sir, will take some getting used to."
Data nodded. "Then, we have a lot to teach each other. Where would you like to begin?"
As the pair departed, Crusher noted the corners of Data's mouth curl upward into the beginnings of a smile as he studied the Dokaalan with the same scrutiny that was being focused on him. Was it curiosity, maybe even fascination? Despite the lack of his emotion chip, the android seemed to possess a spark of seemingly human interest that he had not exhibited for years, she realized.
It was a side of her friend she admitted to missing after all this time.
This may do them both a world of good, Crusher thought as she watched them go.
"Dr. Crusher?" she heard Nurse Ogawa say from behind her, and turned to see the other woman standing next to one of the Dokaalan patients.
"What is it, Alyssa?"
Pointing to the diagnostic panel above the patient's head, Ogawa replied, "Her pulse is rapid and her temperature's rising again."
Crusher frowned at that. Again? It was the third time in four hours such a change in one of the patients' condition had occurred. On the previous three occasions, she had prescribed a mild sedative as treatment, which had resulted in correction of their symptoms.
"Check the others again," she said.
"Could it be an allergic reaction?" Ogawa asked.
The doctor shrugged. "Either that or an infection of some kind. We'll need to run some more tests to be sure, though." None of the previous tests had indicated the Dokaalan might react negatively to any medicines she might administer while treating their injuries. Had she missed something? In order to be sure, she would need to have the Enterprise computer evaluate all the medical data gathered about their guests from the beginning.
What did we miss? she wondered. And what if their conditions get worse?
## Chapter Nineteen
PICARD HAD NEVER been prone to discomfort in low- or zero-gravity conditions. In fact, he always had enjoyed the feeling of weightlessness, taking to zero-g combat training at Starfleet Academy like a newborn horta to a granite quarry. So it was with no sense of apprehension whatsoever that the captain, accompanied by Commander Riker and Counselor Troi, stepped into the observation lounge's reduced gravity, which had been lowered for their guests' life-support requirements.
His spirits were also buoyed by the knowledge that what had begun as nothing more than a make-work assignment had, in less than a day, evolved into a wondrous opportunity to establish first contact with a new species. For a fleeting moment, Picard wished he could be a fly on the wall of Admiral Nechayev's office when she relayed his report to her peers. He smiled at the thought of the reactions it was likely to engender within the halls of Starfleet Command.
A group of five Dokaalan waited for them in the observation lounge, seated around the conference table. Hjatyn sat at the table's far end, flanked on each side by two companions dressed in robes similar to their leader's though somewhat less ornate than those he wore.
"First Minister Hjatyn," Picard began, nodding formally to the elderly Dokaalan who stood at the front of the five-person delegation, "I am Captain Picard. It is my privilege to welcome you aboard the U.S.S. Enterprise. Allow me to introduce my first officer, Commander William Riker, and my ship's counselor, Commander Deanna Troi. It was our intention to meet with you in your offices or some other location of your choosing, but we are honored that you traveled here to meet with us."
The Dokaalan replied, "This momentous occasion warrants more than our limited amenities can provide, Captain, as you will soon see for yourselves. In the meantime, it is our honor to visit such a magnificent ship. When I was informed of your arrival and your efforts to rescue my people, I knew I had to thank you personally. This is a tremendous day for all of my people."
It was praise that still felt undeserved to Picard, despite his earlier talk with Counselor Troi. "First Minister," he said, "though most of your people who were injured have been treated and released, my chief medical officer and her team are still monitoring a few whose injuries were more severe. However, I must offer my sincere apologies for the loss of your people during our rescue attempt. I regret the circumstances surrounding their deaths."
Bowing his head for a moment, when Hjatyn returned his gaze to Picard a small smile graced the Dokaalan's features, and there was also moisture in the corners of his eyes. "While we mourn their loss," the minister said, "many more would have shared their fate if not for your actions. I also understand that two of your people were killed. We will honor their sacrifice in the same manner that we commemorate those of our people who have given their lives in the defense of others."
Nodding in agreement, Picard directed Riker and Troi to take a seat before moving to his customary place at the head of the conference table. "I have been informed that we will arrive at your colony's central complex within the hour," he said. After docking with the Enterprise to allow Hjatyn and his party to board, the minister's vessel remained linked with the starship as it navigated a new course through the asteroid field to the heart of the Dokaalan colonies. "In the meantime, I imagine that you have numerous questions for us, just as we have many for you."
His smile widening, Hjatyn replied, "Indeed we do, Captain, beginning with the obvious one: Where are you from, and how far have you traveled to find us?"
Picard did not doubt the Dokaalan would comprehend the staggering distances involved in traveling from the Federation to this area of space, or even in understanding the basic concept of the technology employed to make the journey, but there would be a time where discussing all of that would be more appropriate.
"We have come here on behalf of the United Federation of Planets," he said, "a shared society of many cultures from many different worlds who have joined together in the spirit of mutual cooperation." He indicated Troi. "Counselor Troi was born on a different planet than Commander Riker and myself, and my crew is comprised of representatives of many other member worlds, as well."
He noticed Hjatyn's warm expression falter a bit as the minister said, "While my enthusiasm at your arrival is unbridled, Captain, I also hope you will understand my need to be cautious. Several of my aides advised against this meeting, offering instead the need to be suspicious of your motives." He held out his thin arms, indicating the conference room and, by extension, the rest of the Enterprise. "One look at this vessel is enough to tell me that, were you so inclined, you could conquer our people with minimal effort. Therefore, I must ask what your intentions are now that you are here."
Picard recalled the reports submitted by Lieutenant Vale and Dr. Crusher regarding some Dokaalan's reactions to learning the identities of their unexpected bene-factors. While some of the miners rescued by the Enterprise were most receptive to their new visitors, many more had expressed doubt, suspicion, and even fear.
With that in mind, he replied, "Some of the people we rescued from your outpost have expressed concern that we may be here as invaders, and I hope that I can put that worry quickly to rest. We have traveled a great distance to see what is here, and we do so in peace. There is much more here than we expected or even hoped to find, and my crew and I are most anxious to learn all that you can teach us. However, should you ask us to leave and never return, then we will do just that."
Noting the palpable silence as Hjatyn seemed to ponder his words, Picard glanced to Riker and saw the subtle change in his first officer's expression. He too was worried that everything that had come so far had happened for naught. The look in Counselor Troi's eyes seemed to mirror Riker's but Picard could not be sure. Was she sensing Hjatyn's unease?
He forced his own features to remain fixed as he waited for the Dokaalan's response. In truth, the Enterprise already had completed the mission as set out by Admiral Nechayev. Still, he would be saddened if understandable yet misplaced xenophobia guided the first minister's decision and prevented him and his crew from making the most of this opportunity.
Thankfully, it did not come to that.
"It seems to me, Captain," Hjatyn said after a moment, "that given the resources at your command, were you of a mind to harm us you would have done so already, and not bothered with the compassionate action of rescuing my people. My instincts tell me that you are telling the truth." Smiling, he added, "Besides, did we not invite you here, after a fashion? I am told that you discovered two of the three unmanned space vessels my people dispatched prior to our world's destruction."
Picard nodded. "Yes we did, though the story surrounding their separate discoveries is a lengthy one. Suffice it to say that the first probe was found long ago, but it was determined that the available technology and resources were insufficient to reach your planet in time." Choosing his next words as carefully as possible, he added, "With that in mind, those in positions of leader-ship at the time deemed other priorities to be in greater need of attention. Several events, some with long-lasting repercussions that were both positive and negative, transpired in the period soon after the probe's discovery. I'm afraid to say that the matter was soon forgotten, at least until the second probe was found only a short time ago."
"I think I understand what you mean, Captain," Hjatyn replied. "To be honest, I am not even sure if anyone involved with the probes' construction or their launch from Dokaal survived the catastrophe. Most people today have either forgotten about the probes or never learned about them. As you said, other concerns became more important after a time."
It's certainly understandable, Picard thought. From the reports Vale and Crusher had given, most of the miners rescued from the outpost possessed no knowledge of the probes. Perhaps the story had been relegated to myth, or simply forgotten in the face of struggling for mere survival.
"What is amazing," Hjatyn said, "is that someone has found one of the devices only now, after all this time. Even more astonishing is that it was still in a condition which allowed you to hear the plea of our people." Smiling, he added, "I think I am beginning to appreciate just how far you have come to find us, Captain."
"It seems that your people already had an appreciation for the vastness of space before your world was destroyed," Troi said. "After all, the probes were equipped with engines that allowed them to travel faster than light. Did you have a space exploration program in development prior to the disaster?"
Hjatyn replied, "Of a sort, yes, though it never progressed to the point of manned flights beyond the boundaries of our solar system. Several science and engineering specialists who escaped the catastrophe tried to re-create and even build upon the technology lost with our planet, but their attempts were unsuccessful. Oh, they were able to develop a prototype engine, two actually, and a plan was even put in motion to send two ships away from our system in search of other life. They were launched on separate trajectories and each succeeded in leaving our system.
"According to messages we received, tragically, the crews of both ships died during their flight from unknown causes. At the time, our scientists theorized that traveling faster than light was somehow harmful to living beings, and the technology was abandoned." Indicating the Enterprise officers with open arms, the minister added, "Obviously, that was a mistaken conclusion, or perhaps it is only correct with respect to the Dokaalan. Either way, it is unfortunate for us." The elderly leader smiled at that, and Picard found himself warmed by the expression of emotion. Yes, he decided, despite the earlier tragedy, a good thing had happened here today.
Leaning forward in his seat, Riker said, "I imagine you had your hands full as it was. According to some of the people we rescued, you've had to make do with what are essentially temporary facilities since your planet was destroyed. That you've managed to survive this long is remarkable."
"Necessity has always proven to be a fine motivator, Commander Riker," Hjatyn replied. "When Dokaal exploded, we were faced with sustaining not only the existing mining contingents but several thousand evacuees as well. We had to reallocate our limited resources to accommodate our increased numbers. Many of our original outposts still exist, though they have been pressed into service for far longer than their original designers ever intended. They are in constant need of repair, and many lives have been lost due to accidents or structural failure. Such incidents have become more common in recent years, which is why there has been a concerted effort to construct new facilities, such as the central habitat and control complex that now serves as the heart of our community." Shrugging, the aged Dokaalan added, "Though our level of technology is primitive compared to yours, I think you will be most impressed by the ingenuity of my people."
"Of that I have no doubt, First Minister," Picard said. According to the analysis provided by Data and La Forge, Dokaalan technology in many respects was on par with that of Earth during the late twenty-first century. Had they continued with their research into faster-than-light travel, or perhaps been inspired by the presence of an extraterrestrial race as humans had once been, that comparison might have even been closer. "In my travels I have learned that there is always something to be learned. Also, once I notify the Federation of your situation here, I'm sure there will be no trouble obtaining aid for your people."
To the captain's surprise, Hjatyn seemed for a fleeting moment to be troubled by the proposition. It was only a flicker in the elderly leader's eyes, one which he covered quickly enough. "We have always been a self-sufficient people, Captain, even before our planet was destroyed. I am not sure the idea of long-term outside assistance will be palatable to them."
Before Picard could further any debate, the minister held up a frail hand. "However, there will be time enough to discuss such a kind and intriguing offer." The captain and his officers stood in deference to the leader as he rose from his own chair. "Forgive me, Captain, but at my age I grow fatigued easily. With your permission, I will return to my vessel. There are still many preparations required to give you and your crew a proper reception, after all."
"As you wish, First Minister," Picard said, putting on his best diplomatic smile to cover the momentary unease he had felt. "We can meet again at your convenience."
"Excellent," Hjatyn replied. "I am so looking forward to introducing you to the rest of my people, Captain. I hope that you will want to meet them and see all that they have accomplished, just as I hope to see more of this breathtaking vessel and meet your crew."
"I'm sure we can see to that," Picard replied.
The Dokaalan leader nodded in satisfaction. "Though we must certainly pause to remember those who have fallen, this will still be a wondrous occasion for celebration."
After asking Commander Riker to escort the Dokaalan delegation back to their ship, Picard waited until the doors to the lounge had closed and he was alone with Troi before turning to her. "Counselor, would I be mistaken if I said I thought Hjatyn seemed a bit uncomfortable during the meeting? Did you sense any duplicity or deliberate withholding of information on his part?"
Troi nodded. "His mind is incredibly focused, Captain, but he was holding back something. He could simply be acting with caution, as I did sense his relief when you accepted his request to end the meeting. It's possible he still views us as a threat, but that type of reaction is normal in first-contact situations. Such an event is often unsettling, after all, even when the exchange is welcomed by the contacted party. I've detected similar anxiety in some of the miners we rescued, though many more are enthusiastic at meeting us."
Frowning, Picard considered the counselor's words. He had participated in enough first-contact missions to be familiar with the type of trepidation she described, but that did not soothe the gut feeling he had experienced while observing Hjatyn during the meeting. Was there something more than simple fear there?
"These people haven't had the benefit of a normal civilization for a long time," he said, still trying to rationalize his own misgivings. "After being on their own for so many years and succeeding in marvelous fashion despite the odds against them, it seems natural to me that they would apprehensive with any change in their routine, be it good or bad." Picard knew from practical experience that feelings such as the Dokaalan seemed to be displaying, justified or not, could injure relations with a new species to such an extent that years might be required to repair the damage.
I certainly did not travel this far for that to happen, he thought.
"Considering how long it took us to get here," he said, "I am not in a terrible rush to leave just yet. With that in mind, we will simply have to work that much harder to alleviate their worries."
As he rose from his chair and headed back to the bridge, however, Picard could not shake the feeling that there was something more going on here.
Getting paranoid in your old age, Captain?
The thought teased him. Could some sort of residual bitterness, brought about by the circumstances that had brought them here in the first place, be making him overly cautious and causing him to second-guess every action? Perhaps.
Then again, perhaps not.
## Chapter Twenty
AS IT HAD for more than a day, the image on the bridge's main viewer featured uncounted asteroids drifting past the screen's edges. It also depicted the two Dokaalan ships that had accompanied Hjatyn's vessel to the Enterprise, guiding the starship through the dense field.
Picard noticed that the screen's resolution appeared to be sharper than it had been for most of the time since their arrival. Much of the static and grain that had become almost a fixture of the system's visual imaging was gone. "Mr. La Forge, I take it that your attempts to improve our sensor readings have been successful?"
"To varying degrees, Captain," the engineer replied from his console at the rear of the bridge. "We don't have the range we're used to, but up close I've managed to filter out most of the interference. We might still have some problems if we get too close to a large source of radiation, like one of the bigger asteroids, but we'd have to be a lot closer than I think either one of us would want to be."
"According to my readings," Vale said from the tactical station, "that might be just what we're in for. I'm picking up a massive asteroid that appears to be along the course we're navigating, and if this is right, I'm also detecting more than sixty thousand life signs there."
"Sixty thousand?" Riker repeated. "That has to be one hell of a big rock."
Vale replied, "Initial measurements show the asteroid as being fourteen point eight kilometers across at its widest point."
"Considering the level of their technology," the first officer said, "that's a pretty bold achievement. It took nearly a century before that many people were living on our first lunar colony."
"And these people didn't have the Vulcans looking over their shoulders the whole time, either," La Forge added. "Today we've got more than fifty million people living on the moon. Imagine where the Dokaalan might be after the same period of time."
Though Picard knew the chief engineer made the comment in jest, it was true that much of humanity's drive to succeed in the decades following first contact with the Vulcans was due in no small part to a desire to show their mysterious benefactors what human ambition and ingenuity could accomplish simply if given the chance. As a student of history born and living in the twenty-fourth century, he benefited from the hindsight of those who had recorded the events for posterity. He understood the Vulcans' reasons for not interfering in Earth's development and maturation into a peaceful society. Things were markedly different for the people living during those tumultuous years, however, trying to forge a better world from the ashes of the one their ancestors had nearly succeeded in destroying. Long after enthusiasm and determination had been exhausted, feelings of resentment and frustration toward the Vulcans often fueled the passion of those who laid the groundwork for the society enjoyed by Federation citizens today.
He imagined a similar attitude taking hold among the Dokaalan people. Although engendered more by a basic survival instincts rather than the influence of an outside party, the results would be the same. Facing bitter defeat, the Dokaalan had banded together and raised a collective fist in defiance of the universe itself, proclaiming that they would thrive regardless of the obstacles laid before them.
Picard was only beginning to smile at the rousing image the thought conjured when one equally awe-inspiring appeared on the main viewer.
"Would you look at that," La Forge said from behind him.
Dominating the image was what at first appeared to be a gigantic asteroid, dwarfing every other mass of rock visible on the screen. Despite its rough surface, which was peppered with craggy peaks and dark chasms, Picard thought he recognized a sort of symmetry to the massive body. In addition to its natural terrain features, he also noted the network of artificial constructs crisscrossing the surface. Large buildings sprouted from the rock, linked by a maze of connecting tunnels that wove around, over, and sometimes through the rolling mountains that formed the asteroid's topography.
"Wow," he heard La Forge say, and turned in response.
"What is it, Geordi?" Picard asked as he walked to the rear of the bridge, and the engineer waited that interval before continuing.
"You're not going to believe this," he said, indicating the upper right monitor at his station. "That isn't a single asteroid, Captain, but a whole bunch of them that have been brought together."
"What?" Riker said as he rose from his chair. "You mean they've actually pushed asteroids together to make one big rock?"
Turning in his seat at the ops station, Data said, "Theoretically, it is possible, Commander. Many hypotheses have been put forth examining the benefits of such a venture. In the late twentieth and early twenty-first centuries on Earth, several such plans were conceived that would utilize the asteroid belt between Mars and Jupiter, but it was ultimately deemed to be too dangerous and cost-prohibitive an undertaking, particularly when it was determined that the sum total of available material would equal less usable land mass than Earth's moon. Outposts were constructed in the belt in much the same way that the Dokaalan have done here, but plans to create a planet from the asteroid belt eventually were discarded altogether."
"Well, this is no theory," La Forge said. One of the engineering station's monitors depicted a computerized schematic of the asteroid, and the engineer pointed to a series of colored areas he had highlighted. "These are magnetic interlocks, embedded into different asteroids so that they're concealed as the rocks come together. Though the technology is much more primitive, it's not really that different than the system connecting the Enterprise's saucer section with the secondary hull."
Turning back to the main viewer, now close enough that the ship's sensor readings were providing much more detail on the mammoth construct, Picard could plainly see the web of fissures spread out across the face of the rock. It would have been easy to dismiss them as nothing more than cracks, but now he could distinguish the lines of different asteroids, of all shapes and sizes, that had been brought together, the crevices between them looking like the outlines of individual pieces all working together to create a colossal three-dimensional puzzle.
"We've used asteroids as the foundation for starbases and observation outposts for centuries," he said, "and there have been several instances where a space vessel was fashioned within the hollowed-out interior of an asteroid, but the sheer audacity it must have taken to realize a project like this is amazing." Even though he was not skilled or knowledgeable in any of the technical disciplines required to create such a structure, Picard found himself anticipating the opportunity to inspect the colony habitat and to see just how these people had managed such a staggering feat of engineering.
Already envisioning how this development would look in his next report to Starfleet, the captain could not help being amused at the questions it likely would raise. Would there be second-guessing over the decision made two centuries ago not to send a ship to investigate the origin of that first Dokaalan probe, the one discovered by the Vulcan vessel? Picard figured the question was all too easy to answer. The assorted bickering and other minutiae that composed the livelihood of politicians and others constantly working to remain in power would overshadow the true story worth telling here: that of the Dokaalan people and their valiant struggle against the tremendous adversity Fate had seen fit to pit against them.
Just one more reason, he reminded himself, to avoid politics altogether.
* * *
The Dokaalan wasted no time transmitting boarding procedures to the Enterprise, after which Picard, accompanied by Data and Troi, transferred to the central habitat via shuttlecraft. While there had been assurances that the starship itself could safely link up with one of the complex's external docking ports, the captain had opted to keep the vessel mobile for the time being. His conversation with Troi following the first meeting with Hjatyn and his people was not forgotten, after all.
"Welcome to our home, Captain," Hjatyn said as Picard and his team stepped through the airlock. In the chamber beyond, the first minister waited with a contingent of eight Dokaalan, each dressed in robes similar to his own. "I present to you the Zahanzei Council, the duly elected ruling body of our society and named after the first minister who oversaw our people up until the time of our world's destruction."
After introducing the eight council members, Hjatyn indicated the chamber with outspread arms. "As you can see, we possess little, but everything we have we offer to you, our distinguished guests."
Like everything else Picard had seen of the mining colonies to this point, this facility appeared to be constructed in the same sparse manner and without any embellishments. Even though this was supposed to be the area of the station where the colony's government was headquartered, the chamber offered no decorative or frivolous accoutrements whatsoever. The bulkheads appeared to be of the same material as those used throughout the other mining outposts, with cylindrical tubing running near the ceiling that presumably protected wiring as well as water and coolant transferal. Everything in the room, from the furniture and computer workstations to the various storage containers arrayed around the perimeter of the room, spoke to the no-frills nature of Dokaalan existence.
"The pleasure is ours, First Minister," Picard replied before introducing Data to the Dokaalan delegation. "This is a most impressive facility." He opted not to make mention of the definite stale tang lacing the air, no doubt a by-product of the colony's life-support recycling process.
Nodding, the Dokaalan leader said. "It is the result of many years of joint effort on the part of my people."
"Minister Hjatyn," Data began, "I have spent some time with one of your medical specialists, Nentafa. He told me about the construction of this habitat, but was unable to offer any information about the technical aspects of the project. According to our analysis, such a venture would have proven quite a challenge, given your present level of technology. I am therefore very curious as to how you went about it."
Picard thought the android's request, phrased in his usual straightforward manner and without any conscious attempt to insult, might still be interpreted as offensive by the Dokaalan. He was relieved when Hjatyn smiled warmly in response.
"It was indeed a test of our resolve, Commander Data. Building this new home pushed us to the limits of our resources and technical acumen, to say nothing of our resolve. I admit to being skeptical about the concept when it was first proposed, but the project turned out to be a defining moment for our people. It gave us a singular goal, a unified purpose if you will, of making life better for all of us. The costs were great, both in matériel and in the number of people who lost their lives during the course of construction, but the completed habitat is itself a memorial to everyone who sacrificed for the greater good."
"It is a marvelous accomplishment," Picard replied, "my engineers are most eager to learn more about it. I have to confess to being drawn in somewhat by their enthusiasm."
Hjatyn smiled again. "Of course, Captain. We will do our best to accommodate that curiosity, but something tells me your engineering staff will have no trouble comprehending our work. As it happens, our most learned minds have envisioned a future for us that is even grander in its scope." Gesturing for the Enterprise officers to follow him, he said, "Come, my friends, and be the first outsiders to see what awaits the Dokaalan people."
Data followed as the first minister shuffled his way across the room and toward one of three doors set into the chamber's rearmost bulkhead, but as Picard started after them he felt a gentle touch on his arm. He turned to see Troi glancing toward the Dokaalan delegation, obviously waiting for them to move out of earshot before speaking.
"What is it, Counselor?" he asked, continuing to walk slowly so as not to attract too much attention from their hosts.
"Something I sensed from Hjatyn," Troi replied. "He doesn't appear as guarded as before, but I still get the feeling he's hiding something. It's almost as though he's aware that we're suspicious and he's trying to overcompensate. He wants to appear more hospitable than he's comfortable with, hoping to put us at ease. Some of the council members have similar feelings, as well as the expected mix of hesitation and excitement provoked by a first-contact situation."
"But you're still not sensing any sort of threat or danger from them?" Picard asked.
"No, sir. As I said before, I think some of them, Hjatyn included, feel we are more a threat to them than the other way around."
"Very well, Counselor. Continue your observations."
Hastening their pace to catch up with the others, Picard and Troi entered the room beyond the reception chamber, which the captain recognized as some form of command center. Computer consoles and maps lined the walls, and workstations were situated in such a way that they faced a central large screen at the room's far end. The image on the screen was divided into two sections. One of the sections displayed a view of a planet as seen from low orbit, while the other showed scrolling series of computer code, including what the captain took to be complex mathematical equations.
Hjatyn pointed to the divided display. "What you are seeing is Ijuuka, the fifth planet of our system and one-time neighbor to Dokaal. While it is approximately the same size as our former planet, like the other worlds in our system its atmosphere is unable to sustain our people and possesses poisonous vegetation and no animal life. We learned all of this in the early days of our space-exploration program, long before Dokaal was destroyed, when we sent unmanned reconnaissance probes to the other planets."
"First Minister," Data said, "have you considered constructing habitats similar to those you have here on one or more of the other planets?"
The Dokaalan leader nodded. "For a time after the loss of our world, we considered building such facilities and transplanting our community to one of the planets, but to what end? We would still be living within a contained environment, relying on an artificial world to protect us from the dangers that lay beyond the metal walls."
Turning from the screen to face the Enterprise officers, Hjatyn spread his arms. "While we have been successful at carving out a serviceable existence for ourselves, what my people lack is a true home, a world where they can roam freely, secure in the knowledge that the air they breathe is not the product of a machine requiring constant maintenance and repair." He indicated the image on the central screen once more. "We have decided that if such a world is not readily available to us, then we will make one."
The enormity of what he thought the minister was proposing actually made Picard's jaw drop. "Are you suggesting that . . .?"
"Yes, Captain," Hjatyn said, cutting Picard off. "Ijuuka is the one planet in our system with the potential to provide that home to my people. We are therefore recreating it in Dokaal's image."
## Chapter Twenty-one
**Translated from the personal journal of Hjatyn:**
THERE WAS ANOTHER accident yesterday.
Of all the duties I have had to perform since being elected first minister, notifying a family that a loved one has been lost remains the most painful. That I will have to carry out such a heartrending obligation fifteen times before the day is out weighs even heavier on my soul.
It is a responsibility I could entrust to one of my aides or perhaps one of the other council members, but I have never been one for delegating the unpleasant aspects of my position. I have always felt it important to remain in close contact with the people of our community, whether we are rejoicing in joint celebration or grieving in shared sorrow.
The number of accidental deaths during construction and repair operations around the colonies has been on the rise. This time it was due to a ruptured bulkhead while a maintenance crew was working inside one of our factory complexes. The explosive decompression caused by the structural failure also inflicted extensive damage to the delicate equipment housed in that section.
It feels wrong to even contemplate the harm to machinery, mere equipment that can be replaced, at the same time I am mourning the dreadful loss of life, but that way of thinking is also a necessary responsibility I bear. In addition to lamenting those who have been taken from us, I must also consider the well-being of those left behind. It is my duty to find out what happened and apply that knowledge in such a manner that it reduces the likelihood of such an incident happening again. To do anything less is to insure that those who sacrificed their lives did so in vain.
My engineering consultants have told me repeatedly that as our facilities age, despite our best efforts to maintain them, the likelihood of breakdowns or structural failures will continue to increase. It was based on their recommendations that I approved plans to construct new outpost buildings for use as habitation areas as well as for maintenance and support services.
There is no shortage of raw materials, thanks to the vast asteroid belt, but there is always the risk of injury or death to those workers subjecting themselves to the harsh environment of space with only their hardened excursion suits to protect them. That much has proven apparent on occasions too numerous to recount here.
Additionally, there is the inescapable fact that once the work is complete, we are really no better off than we were before. We will still be living inside artificial constructs, metal containers created to keep us alive but not designed in any way that allows us to truly live. Our efforts have gone toward building better cans in which to pack ourselves, hiding from the unforgiving environs of the space that surrounds us.
However, there are those who have strived for something more. The most gifted minds among us have proposed one bold idea after another in a constant quest to improve life for the entire community. I recall listening in both astonishment and skepticism as the first plans for the central habitat were presented to the council. The very idea of using our spacecraft to push asteroids together so that they might form one larger body seemed preposterous, regardless of the confidence the engineers held for the data supporting their theory. While even my limited grasp of the sciences was enough to tell me that the idea itself was hypothetically possible, my concerns for the safety of workers and our limited fleet of spaceships gave me pause.
Despite my misgivings, I soon became aware of the effect the intrepid scheme was having on the overall morale of the community. No longer satisfied to merely exist within the confines of the mining facilities, the people were energized by the idea of crafting a grand new home from the very rocks that had been their safe haven for so long. The sustained effort would provide a focal point of united purpose that went beyond simple survival. As their leader, I had no choice but to set aside my own uncertainty and allow the project to commence.
And what a glorious achievement it was! Though to this day I do not understand very much about the inter-magnetic systems used to hold the asteroids together, I was able to appreciate the opportunities the magnificent accomplishment provided for us. The complex constructed upon this new asteroid was capable of housing nearly every member of the community, helping us to alleviate the strain on the mining outposts. This in turn gave us the opportunity to begin a more aggressive schedule of upgrading and replacing the existing facilities.
From a morale standpoint, I was finally able to relax the mandates restricting the growth in the colony's population. Until now a prime concern as we worked to find a balance between the conservation of our resources and the need to allow families to propagate, the creation of the central habitat saw the first newborns brought into our tiny world for nearly a generation, guaranteeing that the descendants of Dokaa would continue on even through these times of adversity.
As the years have passed, however, I and others have realized that even the central habitat is not enough. At its heart it is still a box, an artificial world made of metal and composite materials obtained from the rocks. It exists merely to serve us, possessing no heart or soul of its own. My people crave still more.
Those who were born here among the asteroids feel the yearning despite lacking a frame of reference with which to compare their desires. They are unable to give voice to their longings, but I and others who are old enough to have lived on our home planet can well sympathize with such feelings. I also miss the sensation of grass beneath my feet, of sunlight on my face, and breathing rich, full air that has not been recycled through an atmospheric regenerator. For a time I believed that such joys were long behind us, lost forever along with the world I had once called home.
None of the planets in our system are capable of providing such things, however, and our attempts to re-create the technology which allowed our spacecraft to travel faster than light have met with failure. There is nowhere else for us to go. Of that I have always been certain.
That is, until today.
I am still somewhat in awe of the sheer audacity of the latest proposal offered by our science ministry during the council's morning session. Creij, the leader of the ministry and our most revered scientific mind, has put forth the idea that one of the other planets can be transformed in such a manner that it will be capable of supporting our species. Needless to say, her presentation was at first met with stunned silence before the council chamber dissolved into a flurry of animated discussion.
I will admit freely that my first reaction to the idea was that it was preposterous at best and perhaps even an affront to Dokaa herself at worst. After all, is the creation or remaking of an entire world to suit our needs not on par with the acts performed by divine beings?
Still, Creij is confident of its chances for success. While she tried to describe her idea of designing and creating machinery that could mimic the actions of plant life, transforming the harsh, poisonous atmosphere of the target planet into one capable of sustaining us, I confess that even her simplified explanations left me confused. When she began to explain the concepts of introducing genetically engineered algae, lichens, and other chemical compounds to enrich the soil for the cultivation of vegetation including, eventually, the planting of various crops for food, my mind was hopelessly muddled.
And yet, I am fascinated by the idea.
Creij, in her usual affable manner, tried to put the matter into humorous perspective by reminding us that we would not have Dokaa's resources at our disposal. For such a feat to be accomplished by simple mortals, it is a strategy that will take generations and require the development of technology that does not yet exist. It would be an endeavor that far surpasses any other in the history of the Dokaalan.
Though I would almost certainly not live long enough to see the completion of such a mammoth undertaking, I am inspired by its potential. Later today I intend to put before the council a proposition that will allow Creij to perform the range of experiments she has requested to determine the viability of this concept. Even those will take years to conduct and, if they are successful, at that time we will be faced with an even larger choice.
I am sure that there are those who will doubt the feasibility of such a bold scheme and condemn it as a fool-hardy waste of resources, but I am equally confident that it is an idea that will stir renewed hope and purpose in the majority of my people. I have no illusions that it will be an easy choice to make. Offering uncertainty in the face of that which is familiar has always been laced with risk.
Still, for the first time in generations we have been given a chance for real, lasting change that will give us new life. This project, if completed successfully, would usher in the rebirth of Dokaalan society on a level never before envisioned. How will such a choice weigh on our convictions?
Are we committed to a better life for ourselves and our progeny, or have we resigned ourselves to the existence we have shared these many years, content to remain occupants in a prison we created?
## Chapter Twenty-two
"IT WAS A MANDATE of the council that the world selected for this project be completely devoid of life," said Creij, the Dokaalan introduced to the Enterprise officers as Hjatyn's science minister. Also the current director of the massive effort to transform the planet Ijuuka from an inhospitable world into a new home for the Dokaalan people, she had been tasked with explaining the endeavor to their visitors.
Like Hjatyn, Creij looked to be quite old to Picard, perhaps even close enough in age to have survived the destruction of Dokaal generations ago. That thought also made the Enterprise captain wonder about normal Dokaalan life spans, which seemed to be even greater than that of Vulcans.
Time enough to learn about that later, he reminded himself.
"This narrowed our choices to two candidates," Creij continued, "after which it was determined that Ijuuka was the better option. With our planet selected, we began the process of erecting massive atmospheric processors at fifty-six key locations around the planet. Just as we predicted, the process of converting the planet's atmosphere is a long and laborious one. It will be well into the next generation of our people before the air is fit to breathe. Still, preparations are under way for the next phases of the project, so that we can be ready when the time finally arrives."
"The Federation has been involved in several projects very similar to what you are attempting," Data said as Creij concluded her presentation. "From what I have seen, your level of achievement to this point is extraordinary, particularly given the limitations that you face."
Nodding, Creij replied, "It has produced a variety of ancillary benefits, as well. Developing new technology for the project has also resulted in the creation of many new tools, skills, and chemical compounds, to name but a few, that have found uses throughout the colony. Our standard of living has improved markedly in many other areas because of the work necessary to culminate this vision of ours."
Picard had listened with increasing admiration to the science minister's presentation. The atmospheric processors, already in place and operating for decades, had taken years to design and build. What had been accomplished so far was a stunning achievement, to say the least, and yet it would pale in comparison when the Dokaalan's ultimate goal was reached. The determination of these people, as personified by their leaders, was nothing less than inspiring.
"I am also impressed by your commitment to insuring that no innocent life is placed at risk by this effort," Picard said. "In doing so, you've already circumvented one of the larger issues taken into consideration when the Federation contemplates any terraforming effort."
"We have always been a people that attempted to live in harmony with our surroundings, Captain," Hjatyn said. "Though we did utilize the natural resources of our planet to aid in our progression as a civilization, we always endeavored to minimize the impact to the rest of the environment. In time we learned that a balance with nature could be achieved if only we made the effort to do so."
Picard nodded. "It is a belief we hold dear, as well." Of course, such awareness had not come easily. Humanity had instead taken generations to reach that level of understanding toward their own world, but the rewards that had come as a result of that realization were, to Picard at least, incalculable.
"I take it that a pursuit such as ours is commonplace in your society, Captain?" Creij asked.
"We have had some experience with the concept," the captain replied, "but I would not consider it a common practice, no." Though he was aware of the current effort to terraform the planet Venus in his own solar system, Picard knew of no other such projects currently under way.
Not intimately familiar with the concept of terraforming himself, the captain had read enough that he was able to hold his own in conversations on the subject. From what he did know, there had been several such projects completed just in the last few decades. Despite these successes, terraforming was still a significant undertaking even by the standards of twenty-fourth century Federation technology, and that was only if one measured the effort's technical aspects. "Long ago," he continued, "the Federation established the Terraform Command, which is charged with overseeing all such projects and insuring that they are properly conducted."
He recalled the project on Velara III that had ended in near disaster almost fifteen years ago. The circumstances surrounding that incident had provided an unequivocal justification for the need to monitor such projects with a relentless scrutiny. In that instance, the supposedly uninhabited world had in fact been the home to a race of crystalline life-forms dwelling beneath the planet's surface. When the project called for raising the water table, that action threatened the existence of the planet's indigenous inhabitants.
Going forward at that point would have been devastating enough had it been done in ignorance, but the larger crime was that the project's director had known about the life-forms and yet elected to proceed anyway. Fortunately, Picard and his people had discovered the truth about Velara III and averted disaster, after which the project was abandoned and the planet quarantined by the Federation.
Though no one would ever openly admit it, Terraform Command had been established in the wake of the most formidable example of planetary reformation technology ever devised, Project Genesis. Even the name assigned to that astounding venture was still among the most closely guarded Federation secrets, and with good reason. Created more than a century ago, Genesis had been and still was the ultimate realization of transforming an uninhabitable planet into one capable of sustaining life, reducing the time needed to complete such a process from decades to mere hours.
It had taken little time for the usefulness of Genesis as a tool of aggression to become apparent. The notion that an enemy could pervert the promise of Genesis into a weapon of catastrophic and unmatched offensive power was one that had persisted for decades after the original designers' initial experiments. It was also a threat that had come to horrible fruition only recently, with the effects of the awesome technology still being felt across hundreds of worlds in one sector of the Alpha Quadrant.
Yet another example of our innovation getting ahead of our wisdom, Picard mused. It was because of incidents such as Velara III and the Genesis Wave that the Federation took a very hard stance on terraforming. While there could be no arguing the benefits of such technology if employed properly, there would always have to be defenses in place to guard against its misuse.
"First Minister," Picard said, "now that we are aware of your situation here, I would be more than happy to submit a report to my superiors detailing your efforts as well as my recommendation that we provide whatever assistance you may need, up to and including relocation. Starfleet can dispatch transport vessels capable of evacuating all of your people and transferring them to a planet ideally suited to your species. There are hundreds of worlds throughout the Federation where you would be welcomed, or we can find one that is uninhabited that you can settle on and make your own."
Hjatyn did not say anything immediately, apparently considering the suggestion for a moment before returning his gaze to Picard. "It is an interesting idea and a most generous offer, Captain. When we first learned that our world was doomed, the idea of attempting a large-scale evacuation was put forth. Our limited space-travel capabilities made that impossible, of course. Since then we have made our way as best we can despite the obstacles laid before us. The topic of relocation has been raised occasionally at council meetings, usually in the context of a miraculous rescue by visitors from another world." Smiling as he spoke the words, the Dokaalan added, "You must understand that those discussions were held with the belief that such circumstances would never actually occur. In any event, it is felt by many among my people that we should remain here and continue our attempts to make a new home as well as we are able."
"Captain," Data said, "I am sure that Terraform Command would be most interested in learning about the Dokaalan's efforts here." Turning to Hjatyn, he added, "They may even be able to suggest alternatives to your current methods that would take less time to complete."
Picard had no doubt that Terraform Command would take great interest in the Dokaalan's efforts here. Given their current state of technology, their goal of remaking Ijuuka to suit their needs was indeed formidable, if not impossible. Surely Hjatyn understood that, just as he had to recognize the extraordinary value of accepting Federation assistance.
To Picard's surprise, the aged leader held up a staying hand at that proposition, as well. "I have no doubt you could teach us about a great many things, Commander. However, it is important to our people that we complete this task ourselves."
"First Minister," Troi said, "your conviction is inspirational, as is that of your people, but there is no reason for you to continue this endeavor yourselves. The Federation will almost certainly be willing to help in any way you require while respecting your wishes."
Indicating the large display screen with its images of the Dokaalan's hoped-for new world, Hjatyn said, "Ijuuka will be as much a memorial to the millions lost when our world was destroyed as it will be a home for those of us left behind. For such an effort to have true meaning, it will have to be completed solely by us, and with the resources and skills we are able to fashion for ourselves."
A noble goal, Picard conceded, to say nothing of a remarkable demonstration of these people's character.
"I admire your principles, First Minister," he said, "and have no wish to intrude on them in any way. Please know that we stand ready to assist you should you change your mind."
Bowing his head respectfully, the Dokaalan leader replied, "For now, I think it best to continue as we have. I will not claim that what we are doing here is universally accepted. There are many who feel that the effort is insurmountable, given our requirement literally to envision and create the necessary technology at every turn. They believe that simply surviving out here on the colonies is difficult enough without expending resources remaking an entire world. Some have even gone so far as to accuse us of committing deliberate acts of aggression in order to frighten people into supporting the project."
"Such as the reactor explosion on the colony outpost," Data said. "Do they believe that to be a deliberate act of sabotage on the part of your government?"
Hjatyn replied, "We have received preliminary reports that suggest this, yes."
"Surely they don't have grounds for such accusations?" Picard asked.
His expression one of disapproval, Hjatyn replied, "Certainly not. I could never condone such action. In truth, it has always been our intention that anyone who wishes to stay here on the colonies be welcome to do so. After all, we will still have need of the resources mined from the asteroids even after the bulk of the population moves to Ijuuka." Shaking his head, he added, "However, it is very possible that an underground effort may be responsible for some of the incidents that have occurred recently, including the outpost accident."
The doors to the command center opened and Picard turned to see a Dokaalan, dressed in a simple beige-colored jumpsuit, enter and proceed directly toward Hjatyn, carrying a metallic rectangle perhaps twice the size of a standard Starfleet padd. The new arrival handed the object to the first minister. Picard noted with curiosity that the Dokaalan glanced twice in his direction, each time with what the captain regarded as a look of nervousness clouding his pale blue features.
Hjatyn studied the device for a moment before returning his attention to the Enterprise officers. "I am sorry, Captain, but the council and I have some business to address. Perhaps we can continue our conversation over dinner? We would be honored to have you and your staff as our guests this evening."
After following one of Hjatyn's assistants from the command center, Data said to Picard, "Captain, with your permission I would like to continue my research on the Dokaalan's terraforming efforts. Though they have refused our offer of assistance, we may still be able to provide suggestions for accelerating their processes using resources at their disposal."
The captain nodded. "Excellent idea, Mr. Data. Make it so."
As the android headed back for the docking port and the shuttlecraft they had used to travel from the Enterprise, Picard turned to Troi. "Anything new to report, Counselor?"
"While I believe they are sincere in wanting to finish the project for themselves, Hjatyn seemed unnerved by your suggestion of Federation assistance with the terraforming of Ijuuka. He was also uncomfortable discussing the possibility of sabotage within the colonies."
The captain frowned at that. "Do you think he or any of the others still harbor uncertainty about our motives?"
"It's possible," Troi replied. "There's definitely more to what's going on here than they've shared with us, but I can't say for certain that their intentions are malevolent."
Picard wanted to believe that Hjatyn was simply suffering from the pressures of his office. Guiding these people through such trying times would be a challenge for even the most gifted leader, after all. A situation almost surely complicated by the arrival of visitors from another world, he mused.
Still, he had learned long ago not to discount Counselor Troi's observations. Her ability to tap into the emotional state of an enemy had given him a tactical advantage on more occasions than he could count, and it gave him pause now. If there was something sinister taking place here, just out of their sight, Picard was certain they would discover it soon enough.
And that was what worried him.
## Chapter Twenty-three
ALONG WITH HJATYN and the other seven council members, Creij took her place at the large table that was the most significant feature of the ruling body's meeting chamber.
As did nearly everything else in the room, the table's design reflected function rather than form. The bulk-heads were bare metal plating just like every other wall in the colony, uncluttered for the most part by artwork or other embellishments for the sake of the room's occupants. Even the chairs used by the council members, salvaged from a passenger transport long since retired from service, were in need of new upholstery. Hjatyn, as always, had deferred such priorities in favor of focusing on the council's real responsibilities.
The chamber's sole capitulation to decoration was a painting that portrayed a sunrise as seen from Egiun, the botanical gardens that had once graced the center of Dokaal's capital city of Wyjaed. Rendered by one of the elder citizens who had survived the planet's destruction, it had been presented to the council as a gift upon the completion of the central habitat. Creij herself had always been enamored with the painting, for some reason seeking comfort in the tranquillity it depicted. Even though she had been born after the disaster, it was as though the scene reached out to her and offered a tenuous link to a world she had never known.
At the moment, however, even the painting could not soothe her anxiety.
"My friends," Hjatyn began as he settled himself into his seat, "this is a wondrous time for us, even without our new guests. Our people are counting on us for confidence and leadership, particularly now. We cannot afford to lapse in our duties, either together or as individuals. I am looking to each of you to continue displaying the same calm and poise you have demonstrated to this point. Do you not agree that this is the best course of action, for all our sakes?"
The other council members all voiced their approval, Creij included, but the anxiety she already felt only deepened when Hjatyn turned his attention to her.
"Creij," the first minister said, "you have been troubled of late, my friend. How can we help?"
It was true that she was worried, about Hjatyn. Creij was sure something was wrong with the first minister, though it was nothing she could easily explain and there seemed to be nothing empirical on which to base her suspicions. At first, she had been hesitant to mention anything, wondering if perhaps Hjatyn simply was feeling the pressures of his enormous responsibilities. The first minister had always taken more work upon himself than normally was required for a person in his position, reluctant to delegate even the most mundane of tasks to other council members or his cadre of assistants. While this sometimes had the effect of aggravating his fellow leaders, it was one of the many qualities that endeared him to the rest of the Dokaalan people.
Even before ascending to the Zahanzei Council as science minister and becoming one of its longest-serving members, Creij had been a friend of Hjatyn's for nearly all of her adult life. Among the first children born here on the colonies after the loss of Dokaal, Creij was one of the many who had looked to the council for guidance. As an adult, she had discovered a way to return that gift, using her natural affinity for interacting with people in order to help them find the strength to carry on with the Dokaalan's makeshift existence. It was a function she continued to perform even as she moved into public office, providing support and assurance for the citizens as well as fellow members of the council, including the first minister himself.
More than anyone, Creij believed she knew Hjatyn best, which was why she had finally decided to confront her friend with her concerns at the earliest opportunity.
She had just not expected that chance to come now.
As if sensing Creij's unease, Hjatyn asked, "Come now, surely you can unburden yourself to us. After all the times we have come to you for your wisdom and strength, it is only fair that we return the favor."
Nodding, Creij said, "I have sensed some things that worry me, yes. While I was at first fearful of these visitors, I now believe that they truly wish to help us. Many of the people feel the same way, but many more are expressing uneasiness, even distrust, toward the visitors. Those feelings are being reflected here among the council, and I fear that our divided positions will only serve to make matters worse."
"Come now," said Nidan, minister of security, another senior member who had served nearly as long as Creij himself, "are you suggesting we cast aside all thoughts of caution and welcome these newcomers with open arms? We cannot possibly know or understand their true motives after such a short time."
To Creij's right, Council Member Ryndai said, "As the first minister has already pointed out, if they are seeking something then they hardly need to engage in deception, to say nothing of making the effort to rescue the miners on Outpost Takir."
Nodding enthusiastically at her friend's words, Creij was heartened to hear someone else echo her feelings. She knew that others on the council felt the same way, and hoped that they would take advantage of this forum to air their views, as well.
Of course, not everyone felt the same way.
"Twenty-five people did die in the attempt," Nidan said.
"As did two of their own," Ryndai countered. "Are you suggesting they would sacrifice their own people to gain our trust as part of some elaborate ruse? I think you spend too much of your free time reading those mystery stories." The comment prompted several chuckles around the table, and even Nidan joined in.
"The point I am laboring to make," Nidan replied, "is that we know nothing about these people. We do not know what they are capable of, or how they value life. It may be commonplace for them to execute subordinates for the most inane of reasons. Obviously I hope that is not true, and that they are who they claim to be. I have seen how uplifting their arrival has been for the populace, but I am saying we should remain cautious until we learn more about them. Is that so unreasonable?"
Creij said, "Of course we should be careful, but not to the point where we begin to alienate them. They have traveled a great distance to find us, and now that they are here they have offered to help us realize our greatest goal since we were forced to make a life here for ourselves. Should we not at least consider what they can provide for us?"
She was convinced that what they had seen of the Enterprise was but a tantalizing preview of the vessel's remarkable capabilities, and she could not wait to see them for herself. Though Captain Picard had graciously allowed a schedule of guided tours of his vessel to anyone who might be interested, Creij had not yet had the opportunity to act on the gesture. Soon enough, she promised herself.
"But what is the price of that aid, Creij?" Hjatyn asked. "Suppose we accept their help. What will they ask for in return? Will we be willing or even able to give whatever that might be? What if they present us with an ultimatum? Perhaps they have powerful weapons on that ship of theirs, just waiting to be used should we refuse their demands."
Ryndai said, "With all respect, First Minister, what could we possibly have that they could not take by force? We have seen enough of their technology to know that they can destroy us without a second thought if they so desire."
"There is something else to consider," Hjatyn said. "What about our commitment to honor those lost on Dokaal by creating our new home on our own?"
Shaking her head, Creij replied, "When we made that pledge, did any of us truly consider the possibility of a ship visiting us from the stars with the ability to help us in ways we could scarcely dare to imagine? I know that I did not, but they are here now. With their aid we would have a much better chance of completing the project successfully, and perhaps even faster than we originally planned."
At their present rate of progress, Creij knew that despite the best efforts of everyone on her reformation team, the conversion of Ijuuka into a habitable world would not be completed in her lifetime. With Federation assistance, there was the distinct possibility that, for the first time in her life, she would be able to walk on the surface of a real planet and breathe nonrecycled air with the rays of their sun warming her skin. Was it selfish of her to want that for herself? She did not believe that allowing Captain Picard and his people to contribute to the project would somehow cheapen what the Dokaalan were trying to accomplish here.
Her comments sparked several moments of debate, with the members doing their best to outtalk one another as they debated the positives and the negatives, before Hjatyn called the council back to order.
"It is obvious that we will have much to discuss in the days ahead," he said. "There is no need to rush into any decision." Looking to Creij, he added, "You have given me much to think about, my friend. While I am not yet completely comfortable with our guests, I feel better about them now than I did before listening to you. Once again your guidance has proven invaluable."
After determining that there was no further council business, Hjatyn adjourned the meeting. As the members moved to file out of the chamber and return to their various duties, Creij felt a hand on her shoulder. She turned to see Ryndai smiling at her.
"Do not worry, Creij," her friend said. "They will come around, but they must do so on their own. Hjatyn has always done what is best for us regardless of his own feelings. Soon even he will realize that these Federation people are a blessing from Dokaa." Taking a deep, satisfied breath, he added, "Just think, we may yet walk on Ijuuka."
"I hope you are right," Creij replied. "I understand his caution, but it is not normal for Hjatyn to be so resistant to any new idea. His open-mindedness has always been his hallmark as a leader."
Ryndai chuckled. "Do not judge him too harshly. After all, how many times has his leadership been tested in this manner?"
Unable to help herself, Creij returned the laughter as the pair began to make their way toward the door. Before they could exit the council chamber, however, she heard another voice from behind her.
"Creij, Ryndai." It was Nidan, and Creij saw from the look on his face that the security minister was evidently unhappy about something. "A moment if you please."
His own features clouding with concern, Ryndai asked, "What is it, Nidan? Are you still troubled?"
"I have a delicate matter to discuss with both of you," Nidan replied. Looking about the room as if afraid he might be overheard, Nidan gestured toward another door with his hand. "Perhaps it would be better if we speak in my office."
Creij exchanged confused looks with Ryndai. What was this about? Was there some pressing security situation that required their attention? Even if that were so, such matters were almost always discussed with the rest of the council.
They followed the security minister through the door separating the council chamber from the small room he used for his office. Like Nidan himself, the workspace was a picture of order and efficiency.
The only things that seemed out of place were the two security officers waiting in the room as the two council members stepped through the door.
"What is this about?" Creij asked as Nidan entered the room behind them and pressed a control that closed the door.
Instead of replying to her, the security minister instead turned to his two subordinates.
"Dispose of them quietly."
## Chapter Twenty-four
"I'VE BEEN WATCHING their vital signs for six hours now, Jean-Luc. Any change we can induce with medication lasts thirty to forty minutes at most before their symptoms resurface. Damn."
Sitting behind her desk in her office, Beverly Crusher rubbed her brow in frustration. In her other hand she held her padd, which displayed the latest status report for the five remaining Dokaalan patients. According to the report, just like its predecessors, the patients' condition was worsening.
On her computer screen, the image of Captain Picard peered out at her from his ready room. "But their physical injuries seem to be healing well?"
"Our treatment of their burns, shrapnel wounds, bone breaks, and assorted bruises is all progressing as expected," Crusher replied. "Still, my people and I have been working nonstop trying to find some medicine or other therapy that will combat these persistent symptoms." She shook her head. "I have no idea what is going on."
Thanks to Nentafa, as well as the battery of initial scans and tests conducted during the prolonged triage effort following the evacuation of the mining outpost, the Enterprise computer had been able to analyze a whole host of medical information pertaining to her patients. Even with all of that, however, there was no denying the most current status report.
In addition to accelerated heart rate and heightened body temperature, metabolic rates were wildly inconsistent, cell reproduction had dropped, and neural activity throughout the body had become spastic. Readings that had been stable when the patients arrived in sickbay were showing signs of failure even though the areas of trauma were healing. It simply made no sense to her, and studying the figures over and over did not bring her any closer to an answer.
"From what you've told me," Picard said, "the symptoms would seem to point to an allergic reaction or infection of some kind."
Crusher nodded. "That's what we thought at first, too." She had made that determination with the help of Dr. Tropp and the Emergency Medical Hologram. They had tried every treatment regimen for such maladies that she could think of, exhausting the Enterprise medical files and her own comprehensive experience in the process. Nothing had worked. "We've even consulted with the Dokaalan medical specialists, but they're at a loss about this, too."
Now, she was running out of ideas.
Movement in the doorway to her office caught her attention and she looked up to see the EMH wave to her before returning to the patient he was overseeing. "I have to go now, Captain," she said to the image of Picard on her terminal. "I'll update you if there's any change in their condition."
"Good luck, Doctor," Picard said before the terminal went blank.
Emerging from her office, Crusher made her way across sickbay to where the five Dokaalan were being treated within the confines of a containment forcefield, erected to shield the patients from anything that might prove to be a contaminant to their internal systems. As she drew closer to the isolated area, she saw the EMH apply a hypospray to the neck of one of the two burn victims, the female named Jipta.
The hologram had agreed with her theory that some form of allergy was at work here. After suggesting that the duplication of the Dokaalan's natural environment in sickbay might offer some insight into their condition, he had configured the atmosphere in the isolated area to match precisely the Dokaalan's native environment as well as altered the gravity to equal that of their asteroid home. So far, none of the measures had produced any change in the patients' condition.
"What's up?" she asked as she stopped short of making contact with the containment field.
Without looking up from his patient, the EMH replied, "Cortical monitor readings showed that Jipta was starting to seize again. I administered another dose of melorazine to counter the seizure's effects, as well as a tri-ox compound to aid her breathing." Finished with his current task, he turned to face Crusher. "Other than the fact that their symptoms present themselves so quickly, their condition is very similar to that of someone suffering the final stages of Iverson's disease."
"All five of them?" she asked. That did not make sense. A rare chronic degeneration of muscular function, Iverson's disease was incurable and fatal to humans. To suggest that such a rare disease would manifest itself in a nonhuman was reason enough for alarm. But the idea that five such beings would fall prey to the same rare human ailment—at an extremely accelerated rate, no less—was just absurd.
Got any better ideas?
"Are you suggesting we begin enzymatic therapy?" she asked.
The EMH shook his head. "I am merely comparing her readings to those of Iverson's patients available in our records. She is the worst off so far, but I'm afraid the rest of them appear to be following the same trends."
Despite being enthusiastic at the potential for the EMH program and being the one responsible for its initial funding during her tenure at Starfleet Medical, Crusher had never been able to place her complete faith in the concept of a computer-generated physician. Her original reservations had mellowed over the years as the Enterprise's EMH distinguished itself on several note-worthy occasions, including one emergency that had required life-or-death surgery despite the patient's cultural restrictions against invasive medical procedures.
The hologram had simply adjusted the solidity of its hands and medical instruments, thereby enabling itself to pass through the body of the patient and operate on his damaged heart without actually cutting through the skin and muscle tissue. It had been an exceptional bit of innovation on the artificial doctor's part, one that would have been impossible with a flesh-and-blood physician, and had gone a long way toward solidifying her trust in the EMH concept.
So, why not trust him now?
"Okay," Crusher said, pausing a moment to consider a new course of action. "Let's go ahead and run an inner nuncial series and a neuromuscular scan. Depending on the readings, maybe some enzymatic treatments are a good idea at that."
The holographic physician smirked a bit and said, "I am capable of the occasional 'good idea,' Doctor."
Crusher allowed herself a smile at that before hearing the sound of the doors opening. She turned to see Dr. Tropp guiding Healer Nentafa's antigrav worksled into sickbay.
"Hello, Dr. Crusher," the Dokaalan physician offered as Tropp directed the chair toward her. Crusher noted that the healer looked as though he was even more fatigued than the last time she had seen him.
"Nentafa, are you all right?" she asked.
The healer nodded. "A lack of sleep, Doctor," he said. "Understandable, given the circumstances." Pointing to where the EMH worked behind the containment field. "Has there been any improvement in their condition?"
"I'm afraid not," Crusher replied. "At the moment we're working from a theory that they're reacting to something in our environment, so we've isolated them for the time being and attempted to duplicate the conditions on your colonies as closely as possible."
"Those are thoughtful measures, Doctor," Nentafa said. "You have taken reasonable actions."
Shaking her head, Crusher said. "But they haven't responded to any of it. Instead they're just wasting away."
Tropp stepped closer to the containment field, his attention on the patients lying immobile within its confines. "Perhaps they're reacting to something that's lacking in the environment."
From within the isolated area, the EMH turned and said, "We've compensated for everything: gravity, atmosphere, nutrients, all of it."
"No, it has to be something we're not looking for," Crusher said, trying to organize the sudden rush of halfformed ideas and suspicions flooding her mind. "It's almost as if they aren't getting a vitamin they need, or a chemical, or . . ."
"Something illicit?" Tropp offered when she paused.
The thought had not occurred to her, but it was worth considering. Medical scans of the Dokaalan treated during the triage operation had not identified anything resembling an intoxicating or psychoactive substance present within any of the patients. Even after her staff repeated the tests once the Enterprise data banks were augmented with as much Dokaalan medical information as Nentafa and other healers could offer, nothing untoward had been found.
Had they missed something there, as well?
"You're thinking withdrawal?" Crusher asked.
"It's not beyond the realm of possibility," the Denobulan said, turning his head to cast a curious look at Nentafa.
"Oh, I assure you that is not the case," the healer said. "Even in times of desperation, our people have never squandered our resources on any sort of recreational drug. Medical and pharmaceutical supplies are closely monitored in order to prevent such unlawful use." He paused as he said that, and Crusher watched as the healer slumped in his chair and reached for his forehead.
"Nentafa?" she asked as she crossed toward him. "Are you all right?"
The Dokaalan responded by pitching forward, falling unconscious from the antigrav chair as he crumpled in a disjointed heap to the floor.
Retrieving her tricorder from her pocket, Crusher waved the device over the fallen healer. "Temperature rising, pulse racing." His pale blue skin was warm to the touch, and Crusher looked up at Tropp in shock. "He's showing the same symptoms as the others."
How is this happening?
With the help of Tropp and the EMH, Crusher maneuvered the elderly Dokaalan to another of the treatment beds. As she and her fellow physicians began the task of tending to their newest patient, her mind sought out any clues this might offer toward solving the larger problem they still faced.
"It has to be something here," she said, shaking her head at the now familiar, and useless, information being relayed by the diagnostic monitor over Nentafa's head. "Nothing else makes sense."
From the other side of the bed, Tropp said, "Perhaps we should move them to one of their own hospitals."
"That would be the equivalent to sending a modernday heart patient to nineteenth-century Earth for transplant surgery," the EMH countered. "Their medical facilities are hopelessly primitive compared with ours."
"But even with our advanced technology," Tropp said, "we have been unable to treat them. If I understand Dr. Crusher correctly, removing them from the potentially dangerous environment of the Enterprise itself may have an effect on their condition."
Though he was nothing more than a highly sophisticated computer program, the EMH was now doing an exceptional imitation of an irate human being. "As I have already explained, we have duplicated their native environmental conditions to the smallest degree. It makes no sense that moving them would induce any change."
"It makes no sense that they're dying," the Denobulan doctor finally shouted, "but they are!"
Crusher stared openmouthed at the normally reserved physician, who was now glaring with unfettered hostility at the EMH, his jaw clenched, and breathing heavily through his nose. Elsewhere in the room, all of the medical staff had stopped whatever they were doing and turned toward the sound of the outburst.
"Gentlemen," Crusher said, her voice hard as she stepped forward to regain control of the situation, "moving them back to the colony probably won't be any more detrimental to their condition than leaving them here." She turned to Tropp. "Doctor, please coordinate the movement of the patients back to a medical facility of the Dokaalan's choosing. I'm going to have Captain Picard secure permission for me to remain with them and monitor their condition. If there's any change, I'll inform you immediately."
"And what should I be doing?" the EMH asked.
"Deactivating," Crusher snapped. "Computer, end EMH program."
The holographic doctor had no chance to say anything in rebuttal before he flickered and faded from existence, leaving Crusher and Tropp alone with their newest patient. Looking down at the prone form of the Dokaalan healer, Crusher shook her head. "I'm sorry, Nentafa," she whispered. "I feel like I've failed you."
Glancing around the isolation area, she grimaced at the sight of the patients in their weakened condition, with too many indicators on their medical monitors blinking warning red. Was she helping them—or forsaking them—by sending them back to their own hospital?
"Doctor," Tropp said, "it might be prudent for me to continue our research here. In the event we do find a new course of treatment to try, there would be nothing to stop us from administering it at the colony's hospital."
Crusher was unable to resist regarding the Denobulan with a look of mock suspicion. "A minute ago you said we were out of options and that there was no chance of finding anything new."
Shrugging, Tropp replied. "I was simply trying to get the EMH to shut up. Have I mentioned yet how much I despise those things?"
Despite all the frustration and tension and feelings of helplessness that had consumed her during the past several hours, Beverly Crusher allowed herself a welcome laugh.
Maybe we're not finished here just yet.
## Chapter Twenty-five
THOUGH HIS SMILE might say otherwise, Lieutenant Diix was not a happy person.
"And this is the matter-antimatter reaction assembly, or what we call the warp core," the Andorian engineer said, walking backward with his arms up and pointing with both hands toward the massive pulsing cylinder that was the dominant feature of the Enterprise's engineering section. "It is the very heart of the ship. In addition to being our primary source of propulsion for faster-thanlight travel, it also provides power for many of our other onboard systems."
While it was not a verbatim recap of information found in the ship's technical specifications, Diix knew it was more than enough for his audience. That it might take months if not years for these people to even begin grasping the concepts behind modern warp-drive technology did not seem to dampen their enthusiasm. The group of Dokaalan guests had listened with rapt attention from the moment they had stepped aboard the ship, all fifteen of them hanging on his every word.
Or was it twenty? Diix had not bothered to count. It was bad enough that he had been sentenced to the role of tour guide. Hall monitoring would simply rub salt in the wound.
And if that were not enough, he and the rest of the engineering staff had to deal with modified special life-support requirements in deference to the Dokaalan contingent. While some of the other engineers enjoyed bounding about the room in the reduced gravity, it was definitely not one of Diix's preferred pastimes. Why had he been picked for this task? There were other engineers on staff who were better suited to playing host for the delegation, and Commander La Forge knew that.
Perhaps he should be grateful for the assignment and consider that it, like everything else they had discovered since the Enterprise's arrival in the Dokaalan system, was actually an unexpected and welcome deviation from what many believed would be a tedious mission.
All that changed, of course, after the discovery of the Dokaalan mining outpost and the hundreds of people stranded there. The boring, pointless mission was gone now, replaced by a unique opportunity to learn about a group of incredibly resilient people. His admiration for the Dokaalan had only grown upon learning that they, working with a level of technical knowledge more than two centuries behind that of the Federation, had charged headlong into an endeavor as daunting as terraforming a planet. As an engineer, Diix could not wait for the chance to examine the technology they had literally invented out of necessity in order to realize such a grandiose dream.
He was disappointed that Commander La Forge had not selected him for the away team to Ijuuka on an inspection tour of the Dokaalan's atmospheric processors. There would be other opportunities, of course, but that did not help him right now, not as he was attempting to explain the inner workings of the Enterprise's warp drive.
I should be thankful, he decided as he finished glossing over the finer points of the propulsion system and his audience continued to regard him with silent wonderment. They could have spent the last hour asking all manner of inane questions.
He retracted the thought a moment later.
"What is antimatter?" asked one Dokaalan.
"How fast does your ship travel?" inquired another.
"What do your antennae do?"
It was a supreme act of willpower for Diix to retain his fixed smile. Taking a moment to insure that no anger would reveal itself through his voice, he said, "Ladies and gentlemen, this concludes our tour. I'm afraid my duties won't let me stay with you any longer, but the engineering staff will be happy to answer all of your questions. Thank you for your time."
Finished with his presentation, Diix turned and headed without preamble to the chief engineer's office. Even as he crossed the room toward the small alcove and the sanctuary it offered, he smiled as he watched the enthusiastic Dokaalan converge on those members of the engineering staff not fast enough to get out of sight before being cornered by one of their visitors.
His own respite would be short, however. With Commander La Forge off the ship, Diix was in charge of engineering until his return. That meant making sure the duty roster was up to date and that any assignments tasked for the current duty rotation were completed before the shift change.
The door to the office opened, but Diix stopped at the threshold as he realized that the room was not empty.
"Lieutenant Tyler?" he said to the young human woman seated behind the desk and working intently at the computer terminal. "What are you doing here?"
Tyler had flinched visibly at the sudden opening of the door. It was obvious that she was as surprised by Diix's arrival as the Andorian was to see her in the first place. For a fleeting second the human's expression almost seemed to be one of guilt, but for what reason?
"I'm preparing the deuterium consumption report," Tyler said, her eyes shifting to the computer console, which Diix noted had been turned from its customary position so that its face could not be seen from the door.
Surprised by the answer, Diix shook his head. "Commander La Forge told me to do that."
"I see," the other engineer replied. There was a slight pause where she said nothing else, instead tapping a command string into the computer terminal before rising from her seat. "I guess we have some kind of misunderstanding, then."
His eyes narrowing in suspicion, Diix stepped farther into the office, the door closing behind him. "I should say so. The assignments are clearly indicated on the duty roster. I was given the task of preparing the deuterium report, and you were supposed to be on the detail replacing that port nacelle power coupling. If there has been a change in the assignments for today, I have not been informed." He was not surprised when Tyler moved to block him from coming around the desk. Obviously she did not want to see whatever was displayed on the computer terminal.
Surprise did come, however, when the human calmly reached out and plucked Diix's combadge from his chest.
"What the hell are you doing?" he exclaimed. He instinctively reached to grab the communicator back, noticing for the first time that the other engineer was wearing a phaser. There was no time to ask why before Tyler drew the weapon and fired.
* * *
The orange beam enveloped the Andorian and his body disappeared.
Using a phaser on such a powerful setting would normally have registered with the ship's internal security sensors. Kalsha remembered this fact only the moment after deciding the Andorian would have to be killed in order to preserve the security of the mission. Thankfully, it had taken little effort to encode an override to the security grid capable of blinding the sensors to his weapon's use. He wondered if he would have time before leaving the ship to learn why these people insisted on storing weapons anywhere but a designated armory. Such information might prove useful during future operations.
It is a question for another time. Continue with your mission.
One positive aspect of killing the Andorian was that Kalsha would now be able to assume the form of the dead engineer. That at least was a less risky proposition than continuing on with his impersonation of the human. Moving so that he was not visible through the window, Kalsha reached for his left wrist and tapped it. The human woman's pinkish skin and the dark material of her uniform vanished, replaced by the metallic exoskeleton of his mimicking shroud.
The body-enveloping garment was a most-favored tool of those in his particular profession, having proven quite useful during many of his past assignments. Even in its natural state, the shroud provided effective camouflage for nighttime operations, but its true value lay in its array of built-in sensors and holographic emitters. When activated and used properly, they provided the shroud with the means to replicate nearly any humanoid form.
It had allowed him to assume the form of a Dokaalan visitor, blending in with the rest of the contingent as they were led through the Enterprise and allowed to inspect some of the ship's most sensitive areas, waiting for his chance to get to the chief engineer's office and the relative privacy he needed for the next phase of his mission. Clearly, the ship's crew did not believe these people might be engaged in any kind of suspicious activity. Such trust and complacency would yet prove to be their undoing.
Embedded in the garment's left arm was the shroud's control pad. Kalsha tapped a key and compact digital text began to scroll on the pad's miniaturized display screen. When he found what he wanted, he entered another command and the shroud's emitters came to life once more.
An effective technique imparted long ago by his instructors was always to keep the shroud's passive sensors activated in order to scan anyone he encountered while on assignment. After all, one never knew when it might be necessary to disable a subject and quickly assume that person's identity. Now, for example.
In response to his commands, the Starfleet uniform rematerialized. This time, however, his skin was blue, his hair white instead of black, and antennae jutted from the top of his head.
You make a fair Andorian, Kalsha decided as he reviewed his new appearance in the reflective surface of a deactivated monitor set into the office's rear wall. He had re-created the engineer down to the last external detail, with only one adjustment to make. Manipulating the control pad once more, he looked down at himself and watched as the image of the communicator badge on his chest disappeared. He nodded in satisfaction as he reached for the actual combadge he had taken from the Andorian and affixed it to his own tunic. So far as the Enterprise's computer and its network of internal sensors were concerned, the presence of the communicator was the same as tracking Lieutenant Diix.
A glance through the window separating the office from the rest of the engineering section confirmed that no one else had taken notice of anything happening in here. Though he had come perilously close to compromising the entire operation, the sigh he released was born more of disappointment than relief.
Unlike many of his peers, Kalsha had no passion for killing. There had been several occasions where he had killed without hesitation, his body and mind reacting in accordance with his training. In each of those instances he had done so because he was forced to conclude that assasination was the only option available to him.
This was one of those occasions.
It had been a risk assuming the form of the human woman, but it would have been even more hazardous had Kalsha chosen to mimic someone who would be recognized as not being part of the crew. Even with a complement as large as the one on this ship, the possibility of someone taking issue with a perceived stranger was too great too ignore.
He had not been comfortable with that choice, either, arguing with his superiors that someone might notice the irregularity of a person being in the main engineering section when they should have been elsewhere. The empty space occupied only seconds before by the Andorian had given credence to his suspicions.
How many more would have to die in order to preserve the secrecy of the operation? That the arrival of the Federation starship had introduced a complication into the carefully crafted plan was an understatement of enormous proportions. Given the Federation's predilection for interfering at the precise inopportune moment no matter the issue, he wondered if their training academies offered a curriculum to foster such talent.
As Kalsha had told his superiors at the pre-mission briefing, concealing their efforts from the Dokaalan was a simple task, yet doing so in the presence of the Starfleet captain and his crew was something else entirely. If left to their own devices, they would eventually surmise that something more than the Dokaalan's heroic yet futile efforts was in play here. Already they were sending specialists to inspect the massive planetary reformation operation currently under way on the fifth planet, and what if they should find something?
A moot point now, of course, Kalsha conceded regretfully. There was nothing for him to do now except carry on with his own assignment. Returning his phaser to its holster at his waist, he entered a new command string to the computer terminal, removing the coded override to the security grid. An additional few keystrokes succeeded in wiping away any trace that he had infiltrated the computer's labyrinthine operating system.
Despite its sophistication, Federation software technology possessed a variety of flaws that were ripe for exploitation by someone possessing the necessary skill. He thought such weaknesses would have been identified and remedied by now, especially given the number of times an enemy had taken advantage of a Starfleet computer system for one reason or another. In fact, Kalsha recalled with a smile, this crew had fallen victim to such attacks more than once.
Hard lessons always take the longest time to learn, he reminded himself.
With his new identity in place, Kalsha could now sit at the chief engineer's desk and work, secure in the knowledge that so far as the rest of the department was concerned, Diix was simply carrying out his assigned duties. He would need that time and freedom, for even though he had succeeded in infiltrating the ship's vast computer network to this point, that was child's play compared to the task that now lay before him.
The information he truly needed, that pertaining to the only member of the crew who was a true threat to their plans from an intellectual as well as a physical sense, was sure to be among the most closely protected data in the system. Penetrating the multiple levels of computer security without his efforts being detected would require every bit of his technical prowess.
Still, Kalsha would find it. There was no choice, not if their plans here were to have any chance at success.
## Chapter Twenty-six
"HAVE I MENTIONED how much I hate wearing these things?" Geordi La Forge asked, his voice echoing in the helmet of his environment suit.
To his right, Lieutenant Taurik replied, "Not today, though I do recall several instances during my first assignment to the Enterprise where you expressed similar displeasure. Shall I recount some of the more colorful descriptions you employed on those occasions?"
La Forge chuckled in spite of his discomfort, the laughter a welcome sound within the confines of his helmet. He had never enjoyed wearing the suit, or the "standard extra-vehicular work garment," as it was known in Starfleet-speak. It was true that the SEWGs had been modified and improved over the years, and the current model was far superior to the version he had worn once or twice during his first year after graduating from Starfleet Academy.
Come to think of it, he remembered, the ones we used at the Academy were even worse.
The engineer in him reminded himself that the current model of SEWG was the most advanced such garment created by Federation science, ideally suited for working in the harsh vacuum of space as well as the unforgiving environments of countless worlds on which Starfleet personnel might find themselves. If properly used, a SEWG was capable of supporting its wearer for several hours while drifting in open space. According to its technical specifications as well as the Starfleet Survival Guide, the suit was even capable of surviving planetfall in the most extreme of emergency scenarios.
None of which made La Forge feel any better whenever he found himself forced to don one of the suits in the course of carrying out an assignment. He had no plans to test that last claim, anyway, and secretly wondered if the person responsible for writing those specs possessed either a perverse sense of humor or perhaps just a death wish.
"I think I'm okay this time," he said. Looking over at Faeyahr, the Dokaalan engineer who was currently acting as their guide, he added, "Besides, any bad feelings I might have go away whenever I look at what you have to wear."
Unlike the clean and sleek environmental suits he and Taurik were wearing, Faeyahr was dressed in a getup cobbled together before their sojourn to the planet's surface. The suit itself was a bulky affair consisting of a heavily padded undersuit over which the Dokaalan wore a dull gray insulated coverall. His helmet was large and bulbous, a metal shell that housed a wide glass faceplate. La Forge could plainly see the squat tube running from the neck of the helmet to the Dokaalan's mouth, no doubt providing a source of water or whatever these people consumed to ward off dehydration.
"Such is the life of a laborer," the Dokaalan replied, the thin line of his mouth forming a smile. Despite the fact that he appeared to be a specimen of superior conditioning, if the muscled physique La Forge had seen earlier was any indication, he still bent slightly under the weight of the respirator tank he carried on his back. Unlike the Starfleet officers with their suits' atmospheric regeneration systems, the Dokaalan workers were forced to carry oxygen and other gases necessary for their survival with them into these cruel environs, including the arid, dusty, and quite poisonous atmosphere of Ijuuka. It was not unlike the methods used by humans on Earth during the dawn of their space age.
On top of everything else, the Dokaalan people were contending with gravity that, while still lower than Earthnormal, was still more than four times that which they had lived with among the asteroids for generations. Those personnel who had been assigned to work on Ijuuka had become accustomed to the conditions here, but La Forge could tell that Faeyahr was earning the steps he took.
Yeah, the engineer conceded, I don't have it so bad after all.
"We are almost there," Faeyahr said as the trio approached the processing plant and its main control center.
Rising several hundred meters out of the valley created between towering mountain peaks, the structure was a conglomeration of immense, rectangular buildings connected by a spider's web of conduits, funnels, and metallic grating. It reminded La Forge of the giant ore-processing facilities on Delta Vega, Janus VI, or any one of dozens of uninhabited worlds in the more remote regions of Federation space. The plant was large enough that it had been visible even from high orbit, and the energy readings it gave off as he navigated their shuttlecraft down through the atmosphere were on a level he had not seen except in larger power generators employed on some densely populated worlds, such as those used to power the massive planetary computer system on Bynaus.
Though he probably should have stayed on the Enterprise to oversee the reconfiguration of various systems affected by the asteroid field's background radiation, La Forge had been unable to resist the notion of inspecting the atmospheric processing plants for himself. With a smile of satisfaction, he reminded himself that his team of engineers had already done exceptional work to modify some of the ship's compromised systems. Tractor beams were now functional, though their range and power were limited. Transporters had been certified for nonliving matter, and tests were still under way to make them safe for humanoids. Phasers were still offline, but so far that had not presented a problem.
No, La Forge decided, my people are handling things just fine without me looking over their shoulder, which of course left him to marvel in what he was observing now.
"I said it before and I'll say it again," he offered as they passed through the plant's inner perimeter fence, "what you've done here is amazing, Faeyahr." Looking around at the mammoth processing complex, he nodded in sincere admiration. "I can honestly say I've never seen anything like it."
Regarding the Enterprise chief engineer, Faeyahr replied, "Considering what I have seen of your tools and ship, I find that surprising."
La Forge shrugged. "You shouldn't dismiss your own capabilities so easily. In fact, if we get the chance, I wouldn't mind a crack at flying one of those skiffs of yours."
The Dokaalan technical specialist had ferried over to the starship from one of his people's own vessels using a small craft he had called a "skiff," which turned out to be very similar in form and function to the standard workpods employed at Starfleet orbital dockyard facilities. According to sensors scans La Forge had taken while the ship was in flight, the tiny two-person ship was not only fast but also maneuverable, and would therefore seem ideal for navigating the asteroid field. For use at various exterior mining locations, the skiffs also featured remote-controlled maneuvering arms and even small laser drill emitters, making the craft quite versatile indeed.
As for the processing plants they were now touring, La Forge and Taurik had learned during their earlier visit to the first such facility that the power requirements for the network of fifty-six processing stations around Ijuuka were answered through the virtually inexhaustible geothermal energy siphoned directly from the molten depths of the planet itself. The scheme spoke volumes about Dokaalan ingenuity and skill, demonstrating that at least in this regard, they were actually more advanced than many societies with comparable levels of technology, progressing to the use of such efficient and environmentally friendly energy resources faster than a good number of their contemporaries.
"It has taken a great deal of time and effort to reach this point," Faeyahr said as they neared the airlock that would allow them access to the plant's control center, "but we still have a long way to go."
That much was true, La Forge knew. Even after decades spent cleansing the atmosphere, the network of processors was still a generation away, at minimum, from achieving its goal.
The engineer was familiar with the terraforming accomplishments of Kurt Mandl, Pascal Saadya, and the late Gideon Seyetik, of course, not to mention, he thought with a shiver, his personal experience with the notorious Project Genesis. While those efforts were examples of far more advanced techniques than what was occurring here, the Dokaalan's was still an efficient operation, one of the finest examples of planetary reformation La Forge had yet seen. Even landmark terraforming efforts, such as that on Acheron or Dr. Mandl's long-abandoned project on Velara III, had not operated in so fluid a manner despite benefiting from the most advanced facilities and techniques devised by Federation science.
His thoughts were interrupted as the trio proceeded deeper into the processing station. They passed several Dokaalan along the way, with many of the workers stopping their activities to get their first real look at their visitors.
"Welcome to our new home!" one greeter offered, smiling as he stepped forward. The muffling effect created by both his own suit helmet and La Forge's did nothing to diminish the man's fervor. The expression warming the Dokaalan's blue features showed not a hint of unease or distrust, and the engineer could not resist returning his infectious smile.
A similar welcome had been extended to them during their inspection of the other station earlier in the day. He saw that, as in the first plant, a good number of children were employed here, performing as apprentices alongside their adult mentors and demonstrating their own levels of enthusiasm. They hurled questions at a rapid-fire pace, and the Starfleet engineers were hard-pressed to even acknowledge them all, let alone provide answers.
Just as he had during that prior event, La Forge now noted a whole host of reactions to their arrival, ranging from animated greetings such as the one they had just received to others who simply stood back and watched with varying expressions of wonder and, in a few cases, suspicion.
It's going to take them a while to get used to us, he reminded himself, unable to blame any of the Dokaalan who might be a bit on edge given the circumstances. He held little doubt that their current multipronged predicament was not helping to ease the stress.
The Enterprise engineers followed as Faeyahr led them to an elevator that would take them up to the plant's main level and the control center. The elevator itself was little more than a metal cage with a lever used to control the car's movement through the vertical shaft extending from ground level up to the structure's highest point.
As had been indicated in the design schematics for the processing stations provided by Science Minister Creij, this facility was very similar in construction to the one they had visited earlier in the day. Just as starships and their interiors tended to evolve from the same basic template in order to reduce the acclimation time spent by Starfleet personnel when transferring from one duty assignment to another, the processing centers were designed in much the same manner. There were variations in the external configuration of the buildings to account for the differences in terrain, of course, but the interior details of the structures they had seen so far were practically identical to those at the first plant.
"You might be pleased to know," Faeyahr said as the elevator car ascended under the Dokaalan's control, "that this station currently holds the record for most consecutive work shifts without an accident. There has not been a single mishap here for nearly three hundred cycles."
In fact, La Forge was quite impressed. Given the immense power and maintenance requirements for each of the processing complexes, he simply assumed that work-related injuries or even deaths would be a normal occurrence. He was quite happy to be proven wrong. "That says a lot for your safety measures and leaders."
Nodding, the Dokaalan replied, "Most of the plants have excellent safety records, but a few have been plagued by misfortune, particularly in recent times. Our lead engineers believe that these malfunctions are symptoms of the atmospheric generators reaching the end of their operational lifetimes. Breakdowns are occurring more frequently, which is inevitable the longer we continue forward with the project, and all we can do is plan for those eventualities and minimize the risk to the workers. So far, our leaders are pleased that we can maintain a high standard of safety despite technical problems."
Taurik turned to La Forge. "Commander, it is possible that examination of the information we have gathered during these inspections may yield alternative procedures that can extend their equipment's life span while at the same time allowing for the increase of intervals between periodic maintenance."
Seeing the confused expression on Faeyahr's face, the chief engineer smiled. "That's his way of saying we might be able to help you."
Once the elevator had reached its destination at the plant's main level, the trio entered the airlock leading into the regulated environment of the facility's command center. La Forge would have loved to discard his EVA suit for a while, but they would only be here long enough to get an overview of the plant's operation and current progress before returning to the shuttlecraft.
Removing his helmet, he noted that the air had a definite metallic tinge to it, but La Forge still breathed a sigh of relief as he drew in his first lungful. At the moment, he welcomed any air that did not come from his own atmospheric regenerator.
Small favors, and all that.
"Greetings!" offered an elderly Dokaalan as he rose from his station at the front of the room. Bowing formally in the Enterprise officers' direction, he added, "We were told to expect visitors today. My name is Alerott, and I am the director of this facility."
After introductions were made, Alerott spent several minutes giving the Starfleet engineers his informal tour of the control room, pointing out the current status of the plant's atmospheric processing efforts. Just like its counterpart at the first plant, the control room here was a functional collection of computer consoles and banks of gauges, dials, and a variety of status indicators. La Forge was surprised to find that unlike the other facility's command center, where several of the consoles had been configured for automated monitoring, here most of them were being manned by workers.
Taurik noticed it, too. "Alerott, if I may ask a question: Is something unusual happening?"
The elderly director's expression turned to one of worry. "Not at all. Everything is operating well within normal parameters. Why do you ask?"
"From what we understand," the Vulcan replied, "these facilities are capable of functioning almost exclusively under automated controls overseen by their central computer system. With that in mind, there would seem to be an excessive number of personnel on duty here."
Alerott abruptly laughed in response to the query. "We like to do things a bit differently here, Lieutenant. I have worked at this facility since its activation, and even after all this time I have never been completely comfortable allowing a machine to do my work." Still smiling, he shook his head. "My daughter tells me that I should open my mind to new ideas, but I have always been rather slow in that regard. Besides, it keeps me active and at my age that cannot be a bad thing. Would you not agree?"
Sensing that Taurik might want to debate the illogic of not employing available automated measures, La Forge quickly replied, "I can't argue with that, sir." He grinned as he noticed the lieutenant's quizzical expression.
"Well," Alerott said, holding his arms out to indicate the control room, "what do you think of our remodeling effort?"
" 'Incredible' isn't too strong a word," La Forge answered. "We have people back home who are responsible for projects like this, and not only will they be interested in seeing what you've done here, I guarantee they'll be tripping over themselves to get out here and see it for themselves."
Nodding, Alerott replied, "I have heard of your captain's offer to assist us. While others might feel the need to decline such generosity, I have no such false pride. There is no shame in being shown a better way to do something, after all." A beeping tone from one of the consoles behind him caught the Dokaalan's attention, and he glanced at it before turning back to his visitors. "If you will excuse me a moment," he said with an almost paternal smile, "I must now go watch over my subordinate."
As he returned to his work, La Forge and Taurik found themselves allowed to wander the control room, spending the next ninety minutes or so overseeing the operation. It was obvious from the way the technicians carried out their responsibilities and communicated with one another that they were well versed in their roles. Even when a hydraulic failure was reported in one of the power generator's cooling plants, a repair crew was dispatched with nary a fluctuation in what was obviously a well-rehearsed routine. La Forge found himself impressed yet again with their hosts.
It was Taurik, however, who spoiled his good mood.
"Commander," he said as the engineers made their way back toward the airlock, "I was able to scan the computer system tasked with overseeing the main atmospheric processors, but I am confused by some of my readings."
"How so?" La Forge asked.
"As we have been told, the software protocols used by the computers at all of the plants are of a uniform nature, designed to keep the impact of the reformation process balanced across the entire planet. However, if my tricorder readings are correct, it would seem that the protocols in use at this facility are deviating from that norm."
His brow furrowing in concern, the chief engineer said, "Could it be a computer error?"
"I find that unlikely," Taurik replied. "None of the system's error-tracking programs appears to be registering anything out of the ordinary. From my preliminary readings, I suspect this deviation is deliberate. The changes being introduced by the new formulae are subtle, so minute as to avoid detection by any of the system's fault-discovery software." He paused, his right eyebrow rising as he considered his own words. "It is also possible that the oversight protocols themselves have been modified to allow these deviations to function undisturbed. I would need more time to test my hypothesis, however."
Turning the Vulcan's theory over in his mind, La Forge found himself not liking what he was coming up with on his own. "How long do you think this has been going on?"
"I cannot say for certain without a more thorough investigation of my findings," Taurik said, "but from my initial review I believe these changes are not meant to produce immediate results. Instead, they appear designed to introduce a cumulative effect over time. The changes to the software may have been in place for years."
From what La Forge had gleaned from Creij's design schematics, the vast array of complex mathematical calculations used to constantly monitor the processing stations' operation were designed to adapt to the ever-changing nature of the environment the Dokaalan were creating. Separate computer software was required to oversee the reformation protocols, constantly on the watch for errors that might introduce dangerous elements into the new atmosphere. The need for accuracy was far too great to think that a deviation such as Taurik was describing could be accidental or even the fault of computer error.
"If you're right," he said, "then that means we're talking about the work of an experienced software engineer. How many people among the Dokaalan population have that kind of skill, along with the opportunity to make their changes and keep an eye on things to see that no one else figures out what's going on?" It was a physical effort to keep from looking over his shoulder at any of the Dokaalan workers. Who among them, if any, might be a suspect?
Despite the misgivings held by many, La Forge was convinced that the very future of Dokaalan civilization would almost certainly reach a point where a project as bold as terraforming a planet would become critical to their survival. This was especially true if they were unwilling to relocate to another world. Still, he knew that many Dokaalan were against the idea, preferring instead to stay among the asteroids where they had at least come to terms with their situation and had devised ways to handle most of the difficulties.
But were any of them capable of sabotage to further their desires?
## Chapter Twenty-seven
ABLE TO USE the relative solitude offered by the chief engineer's office, Kalsha had plumbed the Enterprise's massive computer core, scouring its extensive databases for the information he sought. With each step, he deleted all traces of his search before the computer's security protocols even knew he was intruding, just as a fugitive on the run might brush his own tracks from a dusty path so as to stay hidden from his pursuers.
His work was meticulous and precise, but slower than he would have preferred. Still, he knew that to work in haste here and now was to invite discovery. The slightest misstep could bring an end to his mission—to everything they had been working toward. One tug on any loose thread he left behind could unravel the entire fabric of what he was attempting to accomplish.
Therefore, he sat at the workstation, slowly weaving his way through the computer's vast databases and using the opportunity to copy into his newly acquired Starfleet tricorder any and all information he thought would be useful against his unwitting hosts.
No reason to let all of this work go to waste.
After nearly two hours of careful searching, Kalsha finally had been able to forge access to the high-clearance portions of the computer's data banks. It had required every bit of his technical expertise to penetrate the security surrounding that area of the ship's main computer storage without alerting anyone else to his covert activities.
Despite the effort and the risk accompanying it, he had succeeded in finding the information he had been sent to obtain: the complete technical schematics for the Enterprise's android crew member, Lieutenant Commander Data.
While much information had been gathered about the android in the past, one of the key facts that had proven elusive was how to deactivate it. Kalsha had briefly considered trying to destroy Data outright, but that was far too drastic an action. The Enterprise crew would certainly exhaust every available resource trying to locate the responsible party, which would of course risk exposing the entire mission and was therefore out of the question.
As he scanned the schematics, it took little time for him to learn about the emergency manual control located on the android's back. If he could get to that switch, he would be able to disable Data easily. Unfortunately, that was only a temporary measure and one the Enterprise engineers would be able to diagnose easily. Further, it would only serve to ignite suspicion among the crew about who might have triggered the switch, and that was attention he did not need at this juncture, not when there was still so much to do.
There had to be another way, something more subtle. If he could devise a method to render the android inoperative in a manner that left it intact yet unable to function, such a mystery might turn the engineers' collective attention away from other duties and devote much time to determining the scope of the problem and finding a solution. Such a plan, if successful, would allow Kalsha even more freedom in which to operate.
A perusal of Data's maintenance and diagnostic logs revealed something promising. Apparently an incident had occurred that required the Enterprise's captain to deactivate the android when it began to malfunction. The chief engineer had modified a tricorder to emit a pulse of energy transmitted at a particular frequency, something called an "actuation servo," that resulted in a shutdown of Data's neural net and disabled him until such time as the ship's engineering crew was able to repair the android.
It stood to reason that such a pulse, modified properly, could fuse the circuitry of Data's positronic brain irreparably. The specifications for the actuation servo were recorded here in the diagnostic logs, providing Kalsha with everything he needed to devise a new protocol for his purposes.
His work completed, he reminded himself that in order to perpetuate his disguise, it would be necessary for him to risk doing what he had sought to avoid: interact with members of the ship's crew. It was an aspect of his assignment that he had quickly come to loathe. For one thing, he had discovered that humans, who made up a large portion of the Enterprise's crew, emitted a distasteful odor, one the ship's atmospheric systems seemed unable to remove from the air.
Resigning himself to the idea, he rose from the desk, pausing a moment to examine his reflection in the deactivated wall-mounted monitor and insure that his outward appearance of Lieutenant Diix was still in place.
He certainly had not meant to insinuate himself among the crew using such a conspicuous persona. In fact, his goal would have been better served had he remained in the role of a lesser officer, one with computer access but fewer responsibilities to others. Instead, his new position of leadership was an unanticipated result of being interrupted by the luckless Andorian.
Still, assuming the identity of Diix brought with it a new opportunity, something he slowly realized as he strode past other Starfleet engineers busying themselves with their various tasks. As Kalsha made his rounds, his "fellow officers" went out of their way to inform him about their progress toward their designated objectives; assignments the Andorian must have doled out before his demise. They also freely entered their personal computer-access codes in his presence, something they certainly would not have done had they realized that the open tricorder in his hand was attuned to capture those code sequences so he might make use of them later.
All about him, computer stations and monitors provided a wealth of information about the status of nearly every major shipboard system. The engines, environmental control, even the weapons and defensive systems were all observed here. On one monitor Kalsha even noted the current status of the ship's deflector shield energy modulation. An enemy would surely find that bit of intelligence invaluable during an attack, yet here it was for anyone to see. Did these people know nothing about operational security?
Of course, the officers had no reason to suspect that anything untoward might be going on here. There was nothing about him that appeared overtly out of place, let alone a threat to the ship. The mimicking shroud's advanced arrays made certain of that, yet Kalsha still harbored heightened senses of alert and vulnerability as he interacted with the crew. Occasionally he stopped to listen to another crew member's report, nodding silently with presumed interest or understanding before informing the unsuspecting engineer to carry on with their duties. He hoped his charade was enough. Acting out of character from his adopted persona could well draw attention, so he erred on the side of discretion, allowing the shroud's sensors to passively scan his surroundings and gather information.
Kalsha approached one of the consoles encircling the room's dominant feature, the warp core that was the heart of the starship's propulsion system. Towering overhead and extending twelve decks through the middle of the ship's secondary hull, it pulsated with life as it controlled the reaction of matter and antimatter to generate the massive energy required to propel the vessel at faster-than-light speeds. Unleashed, that energy carried the potential to obliterate the ship and its occupants in the blink of an eye.
And by their own design, here it stands . . . so vulnerable.
"Lieutenant?"
Turning quickly, he found himself facing a female alien dressed in a Starfleet uniform. She was blue-skinned and devoid of hair, and it took Kalsha a moment to remember that this was a Benzite. That in turn helped him to draw the officer's name from the list of engineers he had earlier committed to memory.
"Yes, Ensign Veldon?"
"I caught you," the officer said, smiling.
His eyes narrowing, Kalsha slowly drew a breath, preparing for what might come next. "I am not sure I understand."
"I caught you staring at the reactant flow," the Benzite said. "I get mesmerized by it myself, sometimes."
She was attempting to connect with him on some conversational level, Kalsha realized. He was not at all interested, but tried to feign it. At least she did not smell as bad as her human counterparts.
"We all get drawn to our jobs by something, I suppose," he said, smiling politely and stepping away from the warp core. "If you will excuse me, I need to get back to those status reports."
Veldon nodded knowingly. "Oh yes. Commander La Forge gets cranky when those reports are late."
Moving away from the ensign, Kalsha decided he had done enough interacting as he headed back to the relative safety of the chief engineer's office. Once there, he could begin testing a few of his newly acquired passcodes to see if they might yield access to other areas of the ship's computer.
He forgot all about that, however, when his quarry stepped onto the main engineering deck.
It was his first sighting of the gold-skinned android since boarding the vessel, but Kalsha's people had learned a great deal about Data's capabilities in the past. While he did not know many details about the mechanism itself, he knew enough not to let his wits down in its presence. He kept his stride, thinking it best to avoid the android altogether.
It, however, had other ideas.
"Excuse me, Lieutenant Diix," Data said. "I have been ordered by Captain Picard to research possible refinements of the Dokaalan terraforming procedures. I would like to gather some data in engineering, if I may."
"Certainly, sir," Kalsha replied. "I am sure you know your way around."
The android nodded. "Of course. Thank you," it said as it stepped around him toward a computer console. "I am attempting to gather information that we might compare with the findings of Commander La Forge upon his return to the Enterprise. We may be able to suggest options for accelerating the terraforming process in such a manner that we would still be able to respect their wishes of not interfering to any significant degree."
"That is interesting," Kalsha said, actually meaning it. The task of transforming the planet's atmosphere into an environment capable of sustaining life was a long one, even prior to his people's arrival. Unwilling to risk discovery by the Dokaalan, they had found it necessary to adapt to their own primitive terraforming techniques. If the Federation could offer less time-consuming alternatives, then so much the better.
He nodded politely. "I will leave you to your work, Commander," he said before turning and nonchalantly moving to another workstation.
This was a perfect opportunity to strike, he decided as he observed the android engrossed in its work. Deactivating it here and now would elicit immediate confusion among the other engineers, and they would certainly waste no time turning to the sudden problem in their midst. Further, there would be little time to suspect any one person, especially him, of being responsible for causing Data's abrupt malfunction.
Pretending to study the status displays on the computer terminal before him, Kalsha pulled his tricorder from the holster at his waist and activated it. He called up the actuation protocol he had created, verifying that it was ready to execute at his command. The pulse would be effective only within a small radius, no more than five meters, he suspected, but the workstation he currently occupied was within that distance.
Kalsha took one last look at the android, marveling once again at the speed at which it was able to input and extract information from the computer. Reports of its physical capabilities, he noted, had not been exaggerated. It would be a shame to lose such a valuable specimen of artificial intelligence, but it was a small price to pay in order to insure the success of their larger mission. Besides, with the technical specifications he had copied from the Enterprise's computer, it was entirely possible that, one day, a duplicate of Data could be made.
Slowly, he slid his thumb across the tricorder's face and over its recessed keypad, at the same time taking one last look around to verify that no one in the engineering section was paying attention to him.
"Lieutenant Diix," Data suddenly said, looking in Kalsha's direction at the exact instant he pressed the transmit key. "I wonder if I might—"
It stopped in midsentence, its mouth remaining open as if to pronounce the next word. Joints locked in mid-motion as the android was turning from its workstation, momentum carrying it off balance until it tipped over and fell like a rock to the carpeted deck.
"Commander Data!"
Kalsha heard the cry from behind him even as he moved from his own workstation, already assuming the role of concerned colleague. All around him, engineers were scrambling across the room toward their fallen comrade. Trying to appear as alarmed as everyone else, he knelt beside Data and held his tricorder over the android in an effort to appear useful. He took the opportunity to look at Data's face, looking into its yellow eyes and seeing no glimmer of activity.
"What happened?" asked a light-haired crewman whom he could not identify.
"I do not know," he replied. "He was just standing here and then he collapsed."
Suddenly Data blinked. Once, twice, then a dozen times before his eyes began to sweep from left to right.
What? How was this possible?
"I . . . I . . . I-I-I-I," it stammered, remaining motionless while emitting the sound but still causing one of the kneeling engineers to jump back.
Another crewman, an ensign he knew only as Leisner, said, "We should run a diagnostic." He looked to Kalsha, "What do you think, Diix?"
Kalsha, still trying to figure out what he had done wrong in trying to disable the android, scrambled for something to say that would not raise suspicion among the other engineers. His efforts were hampered as the human engineer, Leisner, knelt closer, the odor emitted by his body launching an all-out assault on Kalsha's nostrils.
"I have suffered . . . a catas . . . trophic failure of my . . . neural net," Data said, its voice sounding broken and digitized. "I must shut . . . down to run in . . . ternal diagnos . . . tics. Do not attempt . . . repair. Inform Command . . . er La Forge."
Kalsha struggled not to fidget in front of the other engineers. What if he had only inflicted minor, easily reparable damage? All his efforts might well have been wasted. Relieved that the engineers had in effect been instructed to leave Data alone for the time being, he nodded. "It is probably best to do as he suggests. His own diagnostic abilities can do more for him than we can until Commander La Forge returns."
Beside him, Ensign Leisner said, "It might help if we move him to his diagnostic alcove."
Nodding in agreement, Kalsha organized the engineers to raise Data from the deck, a task easier said than done owing to the android's weight, which was of course far greater than that of a living humanoid of comparable size.
As the other officers maneuvered Data into the alcove specially constructed for use by the Enterprise engineers when performing diagnostics and maintenance on the android, Kalsha could only puzzle over why the actuation servo he had programmed had failed to work properly. He activated his tricorder again and reviewed the unit's scan log from the point when he had triggered the pulse, frowning as the recorded data showed a deviation in the frequency and intensity he had selected.
How had that happened?
Something, another energy source, had interfered with the actuation protocol at the time of execution. What could be responsible for that, especially at such a close range? Then it struck him, and he nearly cursed aloud at the realization.
The mimicking shroud, with its own contained power source, had to be the culprit. In his haste, he had failed to modify the servo's frequency to compensate for the interference generated by the garment. Reports submitted by other operatives in the past had detailed malfunctions in weapons and equipment later attributed to the shroud's energy field. How could he have forgotten something like that?
He tried to shake off his frustration at his foolish error. In fact, he had been lucky indeed that the pulse had not caused an adverse affect on the shroud itself, something else he had failed to consider when devising his plan.
Fool! I need to exercise greater care, or I risk compromising everything.
With Data now ensconced in his diagnostic alcove, he watched as Ensign Leisner activated a control that locked a pair of metal bands in place across the android's chest.
Pointing to the Benzite ensign, the engineer said, "Veldon, set up a terminal to monitor the progress while Data runs his diagnostics. We'll use that to see if we can figure out what happened."
Kalsha regarded the android's immobile form with its frozen, impassive face and its yellow eyes staring blankly back. Had the actuation servo been enough to permanently incapacitate Data's neural net, or had he caused only slight damage that could be remedied in short order? If Data could be repaired, either through his own efforts or those of the other engineers, it was entirely possible that the android would be able to identify Kalsha, or Lieutenant Diix, rather, as the one responsible for the injury inflicted upon him.
"We need to report this to Commander Riker," Veldon said, looking uncertainly at Kalsha.
Kalsha nodded. "Of course." Doing so would expose him to contact with senior members of the ship's crew, but there was no avoiding that now. Having assumed the identity of the senior engineer on duty in the absence of Commander La Forge and Lieutenant Taurik, it was his responsibility to speak on behalf of the engineering section. All he could hope for was that the conversation that was sure to come would be as brief as possible.
Assuming what he hoped was a convincing air of worry, he tapped the combadge he had confiscated from the real Lieutenant Diix prior to killing him. "Engineering to bridge. Commander Riker, we have a serious problem down here."
## Chapter Twenty-eight
PERHAPS IT WAS just his imagination, but La Forge was sure that there was more of an edge to the attention he and his companions were receiving from the Dokaalan.
Not everyone, he thought, trying to soothe his rising anxiety. Quite a few of the workers they passed in the corridors of the processing plant's main level continued to exhibit the same type of curiosity and warmth toward the visitors as La Forge had seen all day.
Still, he had not mistaken the look of keen interest on the face of Alerott and his assistant as he and Taurik had left the command center, had he? Were his eyes playing tricks on him? Had Taurik's report touched off a streak of paranoia?
Perhaps, but it also was possible that something out of sorts just might be going on here. If an act of sabotage was under way, then lives could be in danger. He and Taurik had a responsibility at least to investigate the possibility.
When they were once more sealed inside their environment suits and making their way back down to the ground via the utility elevator, La Forge turned to Faeyahr. "I'd like to take a look around the main processing area, if that's all right with you. What do you say?" He forced himself not to glance at Taurik as he made the request, fearful that the engineers' Dokaalan guide might notice the action and get suspicious.
Suspicious of what? La Forge asked himself. He had no reason not to trust Faeyahr, after all. So far as he could tell, the Dokaalan had been entirely forthcoming about all aspects of the processing plants and his people in general. However, the very reason he could have been assigned as their escort might be to insure that the Starfleet engineers did not stumble across anything incriminating if indeed a scheme of some sort was under way. If that was the case, then who could they trust?
No one, La Forge decided. At least, not yet.
Until he was certain of what, if anything, was behind the strange readings Taurik had discovered, it seemed that the best course of action would be to avoid raising the suspicions of anyone, Faeyahr included.
Frowning, the Dokaalan replied, "I am not sure why that would be necessary, Commander. The machinery in use here is virtually identical to that at the plant we visited earlier today. I doubt you will learn anything new about it or any of its components."
It was a valid point, La Forge knew. Considering that all of the complexes across the planet were working toward the same goal, it seemed apparent that there would be little room for deviation from one location to the next. They had spent a great deal of the morning touring the various sections of the first plant, learning about its cycle of operation, performance record, safety and security systems, and so on. With all of that accomplished, there seemed very little need to repeat the process again at this location. Taurik's tricorder scans of the facility would provide more than enough insight to the entire process and would make for an interesting review once the engineers got back to the Enterprise.
Think fast, Geordi.
As it happened, Taurik bailed him out.
"We completed our tour of the facility so quickly that there was insufficient time to inspect everything with the detail we would have preferred," the Vulcan said, holding up his tricorder for emphasis. "If I were able to record scans of areas at this location that are comparable to those we reviewed this morning, I will have a complete record of a processing plant's cycle of operation."
La Forge had no idea just how lightly Taurik might be treading the line between truth and falsehood, but his explanation certainly sounded convincing. The chief engineer added, "Besides, since these guys operate their control center differently than the other plant, what with employing more people instead of relying on automation and all, they might have a few other differences in some of the other areas, too." He shrugged, trying to play up the role of intrigued fellow engineer as well as that of interested tourist. "And, the more information we have, the better our chances of being able to offer assistance in helping you speed things up."
Faeyahr considered the engineers' words for a moment before nodding. "When you put it that way, it is a sound suggestion." La Forge waited until the Dokaalan's attention was diverted before casting a relieved expression in Taurik's direction.
The elevator slowed to a stop and the trio emerged onto the plant's ground floor. Passing through another airlock, after which they could once again remove their suit helmets, they proceeded down another narrow corridor that in short order opened into the plant's massive, amphitheater-sized central area.
Just as La Forge had expected, the interior layout of this facility matched that of the first plant in most of the major details. The storage tanks and power generators used to drive the continuous cycle of transforming Ijuuka's inhospitable atmosphere occupied the bulk of the complex floor, situated in five rows of six units. Each of the individual generators was connected to a power distribution grid that in turn directed the energy created here to the suite of eight atmospheric processors occupying the facility's middle levels.
As the engineers and their guide moved farther into the facility, La Forge that saw in addition to the constant machinations contributing to the plant's normal processing operations, a good deal of maintenance was taking place. One Dokaalan was occupied with welding two pieces of metal railing together, for what, the Enterprise chief engineer could not tell. Others were involved with the repair of a storage tank, using a type of handheld, air-powered tool to replace the rivets holding the container's outer skin to its frame.
"The trouble with this type of work is that it is very labor-intensive," Faeyahr explained as they walked, "not only with the day-to-day tasks but also in the maintenance and repair aspects. I suppose it is yet another price to pay for our eventual success."
"That's pretty much how it is with anything worth doing," La Forge replied, smiling despite the unease he felt over what Taurik had shown him. "Of course, I'm sure you and your people learned that a long time ago."
"Agreed." The Dokaalan reached out and placed a blue hand on the engineer's shoulder. "We see many things in much the same way, my friend. The more time we spend together, the greater my belief that your arrival here is a gift from Dokaa. She has finally seen fit to deliver us from our trials and offer us salvation, but we must be willing to accept it from the hand of a stranger."
"Would she mind if you took the help from a friend?" La Forge asked. It had been easy to see past the idea of simply aiding the Dokaalan for the engineering exercise it presented and embracing the idea of doing whatever he and the rest of the Enterprise crew could do to offer these people a better life. After all they had been through and despite the success they had wrought through sheer audacity and their unyielding will to survive, the Dokaalan deserved a break.
And they were not the only ones who would benefit.
A seemingly unending string of crises, from the second Borg invasion to the long-lasting and still to be fully determined effects of the Genesis Wave, to say nothing of the Dominion War, had all conspired to take their toll on the Federation in recent years. Rebuilding or replacing all that had been lost, if indeed that was possible, would take years. Along the way, La Forge hoped that people would take a moment now and then to remember what had made everything they had fought for worthwhile in the first place.
And part of that rebuilding, he mused, means making a new friend once in a while.
The biggest question to be answered at the moment, however, was whether they had stumbled into the middle of a societal quarrel caused by the massive terraforming project. Any assistance the Enterprise and the Federation could provide might eventually do more harm than good if the grand plan to create a new home for the Dokaalan was already sowing strife among the people. By all accounts, the idea of abandoning the mining outposts, which despite their obvious limitations had been the only home many of these people had ever known, was obviously not sitting well with some segments of the populace.
His attention was drawn to Taurik as the lieutenant, tricorder in hand, approached them from around the side of a gargantuan support column. "Commander La Forge, there is something here I think you should see." He pointed to a collection of storage tanks, towering above them on the plant floor. "I am detecting a secondary power source operating in that vicinity. It is small and isolated, not connected to the facility's main power supply."
Despite the Vulcan's typically stoic demeanor, La Forge still recognized the hint of concern in his voice. "I don't suppose you're going to explain it as a portable power source for some of the workers' tools or something like that."
Taurik shook his head. "While it appears that the energy readings are emanating from a portable source, the readings themselves are inconsistent with anything the Dokaalan have at their disposal."
Frowning at that and not liking the possibilities the junior engineer's report was conjuring in his own imagination, La Forge said, "Let's take a look." He paused a moment, looking around the floor of the plant to see if they were being observed. No one seemed to be taking an overt interest in them, but that did not ease his apprehension. "But try to act casual about it."
He ignored Taurik's puzzled expression as the trio made their way without hurry toward the storage tanks. Doing his best to play the part of intrigued visitor, La Forge made a point to ask questions about the plant and its operations to Faeyahr for the benefit of the Dokaalan workers they passed. All the while he let his eyes play over the surface of the machinery, allowing his ocular implants to search for anything out of the ordinary that might provide a clue for Taurik's power readings.
Then he saw it.
"What is that?" he asked as his eyes found the small, oblong device hidden away within a mass of pipes jutting from the side of one tank. "Whatever it is, it looks like it's hooked into the flow system directing the different chemicals up to the atmospheric processors."
Leaning closer for his own look, Faeyahr shook his head. "I have never seen anything like that before."
"That is because it is not Dokaalan in origin," Taurik, keeping his voice low. He looked around him before adding, "Commander La Forge, my readings show that this is an improvised device, constructed from components likely salvaged from a variety of sources. Its outer casing is composed of cast rodinium. So far as we have been able to determine, that element is not indigenous to this region of space."
"Rodinium?" La Forge repeated. He knew that the substance, one of the hardest known to Federation science, was used by many races, most notably the Cardassians, in the building of their space vessels. Early Federation deep space outposts, specifically those erected on and beneath the surface of asteroids, were constructed with exterior hull sections crafted from the robust material. Ordinarily, it would make perfect sense for the Dokaalan to employ the substance in the creation of their own facilities. The only problem with that idea, if La Forge's quick calculations were correct, was that the nearest source of the mineral was dozens of years away in a Dokaalan spacecraft traveling barely above the warp-speed threshold.
So, where had it come from?
"An alien power source?" he said, remembering not to speak too loudly. "But whose? And what the hell is it doing here?"
Taurik held up his tricorder. "According to my scans, the device is designed to introduce subtle variations into the chemical composition of the storage tank's contents. The alterations are very minimal, nearly invisible except to an intensive scan. It is unlikely that any of the testing equipment available to the Dokaalan engineers would detect these deviations."
"Sort of like the software modifications you detected earlier," La Forge said. "Are they related?"
"It is possible," Taurik replied. "The device does contain a form of transceiver assembly that would allow it to receive instructions from a remote source."
Faeyahr stepped closer, his expression a mix of confusion and disbelief. "Are you saying that someone else like you has been doing something to our work here without our knowing about it?"
Shaking his head, La Forge replied, "We're not sure, Faeyahr, but it's beginning to look that way." To Taurik he said, "But if someone else were here, we should have been able to pick up some sign of them before now." The Enterprise had detected no sign of other spacecraft anywhere in the system, even before the ambient radiation from the asteroid field had begun to interfere with the ship's sensors.
"Could they have arrived after you," Faeyahr offered, "and kept their presence a secret?"
"Unlikely," Taurik said. "If my readings are correct, then like the software modifications I found earlier, the changes being introduced into this storage container are designed to do so over a lengthy period. If the incidents are related, then what we have found is a scheme that has been in operation for quite some time."
This situation was becoming more unpleasant with each passing second, La Forge decided. "I think the tour's over," he said. "We need to report this to Captain Picard." Unfortunately, that would take time. With the Enterprise still orbiting the Dokaalan central habitat among the asteroids, communications would be hopelessly scrambled by the field's background radiation. That meant flying back to the ship, which of course entailed getting back to the airlock and retrieving their suit helmets before making the walk across the open space to the landing field where their shuttlecraft waited.
Piece of cake, right?
Wrong, he decided, as they approached the service corridor leading to the airlock and found two large Dokaalan workers waiting for them.
Unlike everyone else working in the complex, these two were dressed in what La Forge took to be uniforms, single-piece green garments that contrasted sharply with their pale blue skin. They wore no insignia to offer clues as to rank or position, but the highly polished black belt and boots, to say nothing of the cylindrical object in a holster at each Dokaalan's waist, told the chief engineer that these were a variety of law-enforcement official.
"Commander La Forge?" one of them asked. "Forgive the intrusion, but the minister of security has asked us to find you. There is a situation that he feels requires your attention."
"What is the meaning of this?" Faeyahr asked, displaying irritation rather than concern toward the two new arrivals. "Is something wrong?"
Obviously annoyed at the direct question, the other Dokaalan replied, "Minister Nidan will explain everything when we arrive. He has asked us to escort you to the secondary control center." He held up an open hand to indicate back the way the trio had come.
For the first time since arriving in this system, La Forge wished for a working phaser. "We'd love to stay and chat, but my captain's expecting us back on our ship. Has this been cleared through him?"
"He is being notified as we speak," the first Dokaalan said.
The sales pitch might have worked if his companion had not chosen that particular moment to place his hand on the holster attached to his belt. He realized his mistake, too, but not before catching La Forge looking at him. The chief engineer's eyes locked with the Dokaalan's and in that instant, both men knew the ruse was over.
"Commander!"
La Forge heard Taurik's warning the heartbeat before the Dokaalan's hand cleared his holster with whatever weapon it contained. He caught a blur of motion as the Vulcan rushed forward, his right hand reaching to squeeze the juncture between the Dokaalan's neck and shoulder. The security officer's eyes rolled back in his head and he collapsed, falling like a broken doll to the floor.
To his credit, the man's companion did not freeze in reaction to Taurik's sudden preemptive strike. Instead he moved to his right and reached for his own holster, managing to clear the weapon and bring it up. La Forge saw light reflecting off metal before there was a flash of energy and something screamed past his shoulder. Then Taurik had closed the distance between himself and the Dokaalan, rendering him unconscious alongside his friend.
"What manner of weapon is this?" Faeyahr asked as he jumped forward, grabbing the security officers' fallen armaments. "Security officers carry stun batons, but they are a contact weapon. I have never seen anything like this before."
"Probably the same people who planted that power source on the storage tank," La Forge said as he took one of the weapons from Faeyahr, frowning as he got a closer look at it. Bulkier than a standard Starfleet-issue phaser, it was composed of a squat cylindrical body connected to a stubby handgrip. It had two power settings, clearly marked in Federation Standard: "Stun" and "Kill."
"I'll be damned." He held it up for Taurik to see. "This looks like a first-generation phase pistol."
Taurik nodded as he took the other weapon from their Dokaalan companion. "You would be correct, Commander. This model has not been in use by Starfleet personnel for approximately two hundred years, though they are occasionally available from various illegitimate sources."
"Yeah, but it's an easy bet that the Dokaalan don't do a lot of business with the Orion Syndicate or their black market," La Forge replied. "And besides, these are the first ones we've seen since we've been here. I'm guessing there's not a lot of them, and their owners probably want to keep them low-profile." It was yet more evidence that someone more advanced technologically than the Dokaalan was operating clandestinely here, but who? What would be the gain?
"Do not move!" another voice abruptly shouted from somewhere behind them before the whine of another phase pistol resonated in the corridor. It struck the wall near La Forge, and the engineer instinctively moved away from it as he backpedaled for the airlock.
"Commander," Taurik said as he took one of the confiscated weapons from Faeyahr. "They are bringing reinforcements. We must leave now." La Forge looked up to see more Dokaalan in green uniforms running down the long corridor in their direction.
"We have to warn the captain," he said as he pushed Faeyahr through the airlock door, then waited for Taurik to go in before following after them and sealing the hatch shut.
"None of them are wearing suits," Faeyahr said as he reached for his helmet and put it on, "but more security moderators may be waiting for us outside."
"I do not see any alternative," Taurik countered as he pulled the lever to open the airlock's outer door. To the trio's joint relief, the area outside the facility appeared to be deserted, for now at least.
How long is that going to last? La Forge wondered as they ran for the landing area.
## Chapter Twenty-nine
WILL RIKER ENTERED the engineering section to find the entire staff gathered, more or less, near Data's diagnostic alcove. He watched for a moment as the officer in charge, Lieutenant Diix, attempted to assert his authority by giving instructions to the various engineers in the room.
Having listened to Lieutenant Diix's vague report only moments before, he could not help the anxiety he felt as approached the group. The Andorian engineer had requested Riker's presence down here, rather than providing a complete report over the ship's intercom. As he observed the scene in engineering for himself, he realized that Diix's suggestion had been the correct one.
Riker could hear the Andorian stammering a bit as he issued instructions, and he paused several times to review whatever notes he might have entered hastily into the padd he carried. He knew the young officer was juggling the responsibilities of presiding over the very heart of the starship along with the current problem he faced, and that strain was beginning to reveal itself.
Time to help the man out, he mused.
"What happened?" he asked in what he hoped was his best mentoring voice as he stepped closer to the diagnostic alcove and the immobile form harbored inside it. He listened with growing worry as Diix, the senior engineering officer on duty while Geordi La Forge was off the ship, provided a complete recounting of the moments up to and following Data's abrupt collapse.
"We thought it best to put him here for the time being, given his instructions," Diix explained, indicating the dormant android.
"His instructions?" Riker asked as he studied his friend's inanimate face.
"Yes, sir," Diix said. "After he collapsed, he spoke just long enough to tell us not to attempt any repairs and to notify Commander La Forge of the situation. We only moved him to the alcove so we could monitor his internal diagnostic protocols and try to make sense of whatever they might find."
Riker nodded, noticing a hesitation in Diix's words that he chalked up to the events of the last few minutes.
"I know you're doing what you can," he said, hoping his tone sounded more reassuring to Diix than it did to himself. He tried to remember that, just as the medical staff would spring to action were a biological crew member injured on duty, there was no doubt that the Enterprise's complement of engineers were acting with similar concern and haste to aid Data in a time of need.
Yet, as he studied his friend's unmoving form, his face still frozen as if in the middle of a sentence, the first officer felt a knot of worry forming in his stomach. With his incomparable physical and cognitive skills, Data had proven himself time and again to be an invaluable member of the crew. Riker's first instinct as Data's friend was to order the engineers on hand to spare no effort in getting the android up and running again.
As the starship's acting commanding officer, however, he was well aware of the pressures facing the group of people surrounding him. Pulling all of them from their assigned duties to focus on Data posed a potentially worse problem than having the android out of commission. The engineering crew needed to stay on their toes in regard to every system on the ship, particularly given the hazardous environment of the Dokaalan system. Regardless of the value his friend represented to him and the rest of the crew, Riker was reminded of the hard fact that he could consider no one irreplaceable.
Data himself would tell you that.
"Ensign Veldon," he said as he turned to the Benzite engineer manning a portable field-use monitor that had been wheeled next to the alcove and linked to its emergency access ports, "what can you tell me?"
Veldon indicated the scrolling stream of computer data on the portable console's primary monitor. "The commander's internal diagnostics are indicating that his positronic pathways have suffered a cascading failure. It appears he is attempting to isolate the ones that are no longer operational."
"So part of his brain is still working?" Riker asked.
Nodding, the ensign replied, "Apparently, but there's no way yet to tell which part. He definitely has no control over his motor skills." The Benzite paused to enter a new string of commands. "He might be able to find his way around some of the affected pathways, but even if he does, we have no idea how long that might take."
Riker tried to translate for himself what the engineer was saying. "It almost sounds like he's had a stroke."
Veldon turned to look at him and offered an appreciative smile. "That is an accurate analogy, Commander."
Riker had seen Data absorb all manner of punishment over the years that required physical repairs, but he had always harbored the notion that whatever was broken on his friend could be identified and repaired. Each time there had been a malfunction in the past, they had found a way to help the android, and the first officer wanted to believe that would be the case now.
So why did he feel this situation was different? Was it because of the way Data's debilitating condition had been portrayed, as though he had fallen ill from a disease that had no known cure? Lieutenant Diix had described the cascading wave of circuitry and relay burnouts as though it had affected Data as an individual. This breakdown, if it could not be corrected, seemed to carry the potential to alter Data, even more so than his emotion chip's removal.
Seeing Data in this condition only served to demonstrate again that no matter the sophistication of his friend's software or the ways in which experience helped to shape him as an individual, he was still, at the end of it all, a machine.
Riker himself had almost proven that fact too well more than a decade ago during the landmark legal proceeding that established that Data was a sentient being and entitled to civil rights as recognized by the Federation. Ordered by Starfleet's Judge Advocate General to serve as prosecutor at the hearing, it had fallen to Riker to prove that Data was simply a machine and nothing more, a notion he had not believed then and certainly did not accept now. Despite that, it was a fight he had very nearly won, and also was one of several dark incidents from his life that he wanted to forget. He instead chose to retain the memory, along with the lessons he had learned about his friend that day.
Turning to Diix, Riker asked, "According to your report, you were the one of the closest people to him when this happened. Do you have any idea what might have caused it?"
"We are currently examining several theories, sir," the Andorian replied. "One is that he may have somehow been affected by the radiation surrounding us and generated by the asteroid field. I have ordered a check of all deflector-shield systems to insure that some form of radiation we might have previously failed to detect is not penetrating the hull."
Riker nodded approvingly. "I take it you haven't found anything on that front."
"No, sir, but at the very least it will rule out a cause if we find nothing. Our other ideas mainly revolve around Commander Data himself, and potential faults that might lie within his internal software. However, given his operational record I find that unlikely, too." He shook his head. "I am sorry, sir, but I have only limited expertise with Commander Data's construction and internal systems. Commander La Forge is rather protective of him when it comes to maintenance and diagnostic matters, you understand."
Riker could not help smiling at the image that evoked. "Only too well, Lieutenant. Commander La Forge is very much the mother hen when it comes to Data." Indicating the android with a nod of his head, he added, "Given that he's told you to let him run his own diagnostics, I think you're right. We'll let him work the problem himself until Geordi gets back."
The smile faded, however, as he regarded his friend once more. Though he had faith in the rest of the engineering staff when it came to the Enterprise itself, Diix was right when he said that no one else knew Data the way Geordi La Forge did.
When is he due back again? Not for a while yet, according to the last report he had received from Lieutenant Vale. Shaking his head, Riker dismissed the melancholy feelings. Until La Forge returned, Diix was the officer in charge, and he as well as the rest of his staff needed to be reassured of that fact.
Turning to face the engineers gathered nearby, the first officer said, "I want you to know that I appreciate your efforts to this point. I know it's difficult when you're working a problem that you've never faced before, but if Starfleet didn't have confidence in your abilities they wouldn't have posted you to the Enterprise in the first place. Don't hesitate to report anything you find to Lieutenant Diix, no matter how inconsequential it may seem." To the Andorian he added, "Keep me informed, Lieutenant."
"We'll make it so, Commander," Veldon said.
Leisner grimaced and slapped the Benzite on the shoulder. "Oh, very cute," he said, his tone teasing.
Riker grinned, allowing himself a moment to enjoy the light demeanor exuded by the collection of fresher faces at the stations surrounding him. Mixing up the duty rosters had turned out to be a good idea, he decided, and it seemed to be popular among the ranks; it broke up the routine.
What I wouldn't give for an hour of routine right now.
"Lieutenant," Riker said to Diix after a minute, "come with me, please." He noticed the Andorian's eyes widen a bit at the request, and they walked to the chief engineer's office in silence as the first officer mulled what he wanted to say. It certainly would do no good at all for him to add to Diix's anxiety level as long as he remained in charge.
Once inside the office and with the doors closed behind them, Riker gestured for Diix to take the seat behind the desk as he took one of the empty chairs in front of it. "How do you think things are going down here, Lieutenant?"
Obviously caught off guard by the question, Diix paused a bit before answering. "Given the circumstances, I think the crew is doing its best."
"And you? How are you doing?"
Riker saw the veneer of reserve crack just slightly as the Andorian appeared to weigh his thoughts. "To be very honest," he replied, "I have found all of this to be very unexpected."
"Don't let it shake you," Riker said, smiling. "I know this position is the first time you've been in command when things aren't going well."
Diix nodded. "That it is."
"If I might offer some advice?"
"Certainly," the younger officer said.
"You've got good people who know their jobs," Riker continued, trying not to sound condescending, "which takes a lot of the pressure off of you from the start. Just go about your business and let them go about theirs. They want to work for you, so let them."
Riker was well aware that his leadership methods were not as rigid or forceful as those demonstrated by more seasoned officers in the fleet. He had learned over the years that the reins of command rested more comfortably in his hands when they were loosened a bit, especially where his Enterprise shipmates were concerned.
With so many of the senior staff off the ship or, in the case of Data, wholly unavailable, it fell to junior officers like Diix to take charge of the less experienced personnel. It was trial by fire, so to speak, a time-tested approach used to determine who possessed those qualities both tangible and indefinable that conspired to make a true leader. Riker felt Diix possessed those qualities, and hoped that the encouragement he offered the younger officer might help him to relax and allow him to focus on his duties rather than on his own expectations of what a leader should be.
"Thank you, sir," Diix said. "I will bear that in mind."
* * *
As he watched Commander Riker depart the engineering section, presumably to resume his duties on the bridge, Kalsha waited until the human was safely out of earshot before allowing himself a sigh of relief. He had been able to field the first officer's questions easily enough, though he had to admit that part of the reason for that was the general, nonaccusatory nature of the human's queries.
Still, it had been a challenge. Riker smelled no better than any of the other humans, after all, a condition made worse by the confined space of the chief engineer's office.
Kalsha had been able to imbue enough truth when deception was required that it made telling the lies easier. It was a trick he had learned long ago during his earliest days as a covert operative, and the human Riker had not been any the wiser. He had asked his questions and given his motivational speeches without any idea that he had been staring into the face of the enemy.
While he had prepared himself for a more intensive questioning session as Riker demanded answers for what had happened to the android and who or what might be responsible, Kalsha was not surprised that the first officer did not begin voicing allegations about anyone who might be a culprit for the damage done to Data. After all, the actuation servo used to deactivate the android had gone undetected by anyone in the engineering section. There was nothing to suggest that anything untoward had occurred here.
At least, not yet.
With the android safely housed in his alcove, there was no way Kalsha could approach him or make another attempt to deactivate him permanently without the risk of drawing attention.
He was still angry with himself over his having miscalculated the requirements of the android's shutdown protocol. The possibility existed that Data would reactivate and perhaps even devise a solution to repair itself or offer information to the engineers directing them toward a course of action. What if its internal sensors had detected or even recorded the pulse Kalsha had sent? It would provide the crew with the first clue that something sinister might be happening in their midst.
Kalsha could not dwell on that. The only thing for him to do was carry on in his persona of Lieutenant Diix and continue with his mission, only now he would have to move faster in the event the engineers did manage to make some progress in their investigation. He would have to be more careful from this point on, of course. If another suspicious act were to occur before he could complete his primary task and escape the ship, the crew would certainly believe they were under some form of attack and would enact appropriate countermeasures. Even on a ship this size and with his mimicking abilities, Kalsha had no illusions that he could evade their security forces for any prolonged period.
Relax, he tried to assure himself. By the time that happens, it will be too late.
He reached for the padd on his desk, the one he had been using to further his disguise as just another Enterprise engineer, when a new thought suddenly gave him pause.
The private talk with Commander Riker had been interesting, to say the least, and Kalsha could not help the fleeting feeling of admiration he felt for the human, despite the odor that seemed to be an unavoidable trait of his species. It was obvious from his demeanor that Riker was a benevolent leader who cared a great deal for those under his command. In all his own experience as a soldier and later a spy, Kalsha had never enjoyed the guidance of someone so devoted to his duties as well as to those who served under him.
It was a stark contrast from the methods of intimidation and brutality routinely practiced by superiors he had known during his career. Kalsha could not help but wonder if the performance and morale of his own military might have benefited from the effects of more leaders like the human Riker. Such qualities might well have made the difference during the last war.
Enough, he scolded himself, forcing the wayward thoughts from his mind and reminding himself to return his focus to the task at hand. Still, as he retrieved his padd and made his way from the office, intent on carrying out his mission, Kalsha allowed himself one last brief moment of resignation.
It would almost be a shame, he decided, when Riker died along with the rest of the ship's crew.
## Chapter Thirty
WHEN HE SAW no sign of activity near the shuttlecraft, La Forge knew that something was up.
"It doesn't make any sense that they wouldn't have somebody waiting for us," he said as he ran, his breath becoming labored with the effort of jogging in the environment suit. "Where are they?"
Running alongside him and to his right, Taurik replied, "Perhaps the incident inside the complex unfolded too rapidly for whoever is trying to detain us. They may not have expected resistance."
La Forge shook his head. "Maybe, but I'm betting that they're also trying to keep this low-key." Indicating Faeyahr, he added, "Whoever's playing around behind the scenes here, they're doing it without the knowledge of at least some of the Dokaalan. They may be trying to keep their presence a secret. If that's the case, then they'll be looking to catch us quickly and quietly. That might give us a bit of an advantage, at least until we get off the planet."
Behind him, Faeyahr asked, "Why would someone want to interfere with what we are doing here? What do we have that anyone could want?" La Forge noted that the Dokaalan's breathing was even heavier than his own. Despite being acclimated to the heavier gravity on the planet's surface, Faeyahr was probably not accustomed to this type of exertion.
"That's what we're hoping to find out," the chief engineer said, "but to do that we're going to need help. That's why we need to get back to the Enterprise."
He heard the telltale beep of Taurik's tricorder and turned to see the Vulcan slowing to a walk in order to study the device. Then the junior engineer pointed toward another storage building to their right.
"Three life-forms have just emerged from the far side of that structure," he reported. "They are armed, two with older-model Klingon disruptors and one with what appears to be a Bajoran phaser."
"Interesting mix," La Forge said. Whoever they were dealing with, he theorized, they used whatever materials and weapons they could get their hands on. Was all of this the work of some type of rogue group? Were they dealing with a band of pirates or profiteers manipulating the Dokaalan's situation for their own benefit?
He knew they had only seconds before the new arrivals saw the trio running for the shuttlecraft. Studying the nearby structure with his ocular implants, he determined that it was nearly one hundred meters away. How fast could their pursuers cover that distance? Were they accurate marksmen with their eclectic collection of weaponry?
There was only one way to find out.
"Keep moving," he said, taking off toward the shuttlecraft with a renewed energy. As he ran, he tapped his suit's communicator. "La Forge to shuttlecraft Ballard. Initiate prelaunch sequence."
"Acknowledged," replied the feminine voice of the shuttle's onboard computer.
The first shot came just as he reached for the panel set into the small vessel's hull to open its rear hatch. Orange energy struck the ground near his feet and he turned to see three figures heading toward them, eighty meters away but closing the distance rapidly even while dressed in bulky environment suits similar to Faeyahr's.
"Inside!" he yelled. "Taurik, get us ready for take off."
As Taurik and Faeyahr scrambled aboard the shuttlecraft, La Forge sighted down the length of his phase pistol at one of their pursuers and fired. The beam lanced forward from the weapon and struck the figure in the chest but he continued forward, the weapon having had no noticeable effect.
Uh-oh.
Backing into the Ballard and slapping the door control, La Forge fired the weapon again and achieved the same result. The Dokaalan kept running as if hit by nothing at all.
"Hang on, Commander," he heard Taurik say from the shuttle's cockpit. "I am initiating liftoff."
La Forge fell onto one of the passenger couches as the tiny vessel's engines flared to life and he felt the shuttle move beneath his feet. He could tell by the craft's movements that Taurik was wasting no time with niceties, pushing the Ballard to maximum thrust the moment they left the ground. The engineer was pushed into his chair as the ship banked sharply and accelerated, the view through the forward canopy that of clouds rushing past as the shuttle headed straight up and away from the planet's surface.
"Go to full impulse power as soon as we're clear of the atmosphere," he said a moment later as the craft leveled off and he could rise from his chair. Removing his SEWG helmet, he made his way forward to the cockpit and dropped into the copilot's seat. "Our friends down there are sure to have buddies of their own somewhere. Any signs of pursuit?"
"Affirmative," Taurik replied immediately, pointing to the console set between the two pilot seats and indicating the series of displays there, which showed data generated by the shuttle's array of external sensors. "Five small vessels are on separate intercept courses near the outer boundary of the asteroid field."
"Skiffs, most likely," Faeyahr said, rising from his own chair to lean over La Forge's shoulder.
Taurik nodded. "You are correct. Sensor readings show that the vessels are similar to the craft you piloted to the Enterprise earlier today."
"Any weapons?" La Forge asked. He knew that the Dokaalan ships were very similar to Starfleet workpods, but it did not mean that their mysterious pursuers had not modified the vessels in some way for their own needs.
"None that our sensors have detected," Taurik replied. "They are equipped with the same array of maneuvering arms and laser drill emitters, but that is all."
Frowning, La Forge shook his head. "Well, not really. Those things are fast, and their pilots are probably better at maneuvering through those asteroids than we are. We're not home free just yet."
"And they may have additional ships waiting for us within the asteroid field," Taurik added. "Sensors are unable to penetrate the radiation to any significant degree."
Wonderful, La Forge thought, remembering the care he and Taurik had been forced to exercise when traveling to Ijuuka from the Enterprise earlier in the day. They would have to slow their speed once they entered the field itself, nullifying their lone advantage against their pursuers. The Ballard possessed no weapons of its own, and they would be flying with compromised instrumentation as well.
"Somebody doesn't want us to get back to the ship, all right," he said. Things were unfolding much too rapidly for this to be the work of mere pirates or rogues, La Forge decided. Whoever they were, they were using technology more advanced than that available to the Dokaalan, and they were working very hard to capture the Starfleet engineers. Obviously, he and Taurik had uncovered something that someone wanted to keep quiet. Though it seemed that the majority of the Dokaalan were oblivious of the skullduggery taking place in their midst, La Forge wondered how many might actually be involved in this affair. Who could be trusted?
"Taurik," he said as he studied the sensor images that showed the current position, course, and speed of their pursuers, "can you plot an evasive course?"
"The approach vectors of the pursuing ships are such that it is likely we will encounter at least one of the ships if we continue to travel in the general direction of the Enterprise," the Vulcan replied. "I can plot a course that will take us away from the ship, but we would risk encountering other vessels that we have not yet detected."
"In other words, better the devil you know." Checking his own console, La Forge sighed in resignation. "I'd rather keep heading for the ship. If we can get close enough, their sensors might be able to detect us if we run into trouble." Looking over his shoulder, he said to Faeyahr, "You need to get back in your seat. This is liable to get a bit bumpy before it's over."
At La Forge's prompting, Taurik guided the Ballard into the asteroid field, retarding the shuttlecraft's speed as the first of the enormous masses of rock slipped past the edges of the viewport. Given their proximity to some of the asteroids, La Forge could not even order the use of the ship's deflector shields as a defense against collision, lest the shields interfere with the shuttle's maneuvering ability.
He forced himself to relax his clenched jaw.
"Sensor effectiveness is down sixty-eight percent," Taurik reported. "I have lost track of three vessels. One of the remaining two is maneuvering in behind us while the other is approaching from the port side forward. Both ships are closing."
"Trying to pinch us," La Forge said. He considered increasing their speed but almost as quickly dismissed the idea. They were already traveling as fast as he dared and while he considered himself a more than capable shuttlecraft pilot, he knew that neither he nor Taurik could navigate the asteroid field with the same audacity as their pursuers.
Movement in the corner of his eye made him turn to see a Dokaalan skiff coming around one of the larger asteroids, accelerating as it cleared the massive rock. Even from this distance the chief engineer could see through the two-person craft's canopy and into its cockpit, where only one of its pilot seats appeared to be occupied.
Then he felt the shuttlecraft bank to starboard as Taurik attempted to evade the approaching vessel. Outside, the skiff flashed in the viewport, so close that La Forge could see the join lines between hull plates before it passed by, disappearing somewhere behind them.
An alarm suddenly blared in the shuttle's small cabin, followed by the voice of the computer. "Warning. Incoming vessel on collision course. All hands brace for impact."
"Behind us," Taurik called out just before the entire shuttle shuddered around them. La Forge felt them shoved off course even as the Vulcan fought to retain control of the craft.
"Is he crazy?" La Forge asked, to no one in particular.
Next to him, Taurik nodded. "Such aggressive behavior would seem to indicate that they are willing to go to great lengths to secure our capture."
"But ramming us?" Faeyahr said, the higher pitch in his voice a strong indicator of the Dokaalan's anxiety. "What do they gain from that?"
"It keeps us from reporting what we've found," La Forge replied. "That might be good enough for them if they can't catch us." He checked the damage-control monitor on the console near his left hand. "Minimal buckling to the aft hull. I don't read any damage to the skiff, though."
Maybe shields wouldn't be such a bad idea after all, he mused. His hand moved toward the controls that would activate the Ballard's deflector shields. The motion was stayed as Taurik guided the shuttlecraft close enough to an asteroid perhaps half the size of the Enterprise that the chief engineer thought he might actually be able to reach out and touch the rock's craggy surface. It was a maneuver that would have been impossible had the shields been activated.
"Nice flying, Taurik," he commented, though the Vulcan said nothing, his attention focused instead on his controls.
Faeyahr said, "The skiffs are heavily plated for protection in external mining sites. They can withstand serious collisions, even at these speeds."
The shuttle trembled again, but the impact was not as severe this time. "Warning," the computer said, "outer hull breach in aft section."
"They are firing at us with their laser drill," Taurik said. He tapped new commands to his console and the Ballard banked again, this time to port as the Vulcan guided the ship around a larger asteroid. "It was only a glancing blow, but a well-aimed shot might be able to penetrate the hull."
"Well, let's make sure we don't give them that shot," La Forge replied. He looked over his shoulder to Faeyahr. "Anything else about those ships you can tell us?"
The Dokaalan nodded. "They are fast and maneuverable, but their engines are not that powerful. We tend to avoid approaching the larger asteroids at faster speeds because their gravitational pull can be dangerous at close range. Your ship's engines are stronger, so you may not have to worry about such things."
"It's not like we can ignore it, but it might be something we can use if things get tight." Returning his attention to his console, he checked the sensor display, shifting the information being transmitted by the ship's scanners until he found what he was looking for. "Taurik, maneuver us in close to that big asteroid at bearing ninety-seven mark four."
"Aye, sir," the Vulcan replied, his fingers entering the necessary commands. Outside the shuttle's viewport, La Forge saw the asteroid he had selected, an immense hunk of rock perhaps half the size of a small moon.
The computer's proximity alert sounded once more just before another bump rattled the inside of the shuttlecraft. La Forge was nearly thrown from his seat as Taurik struggled to keep the vessel on course. Another alarm blared in the cabin and a status indicator on the damage control monitor flared crimson.
"I'm getting tired of being a punching bag," the chief engineer muttered.
"We are venting drive plasma from the starboard nacelle," Taurik said. "I have to shut it down."
La Forge nodded. Leaving the drive plasma to vent uncontrolled risked its ignition by the shuttle's engine, which would almost certainly result in an explosion large enough to destroy the ship altogether.
He shook his head in frustration. "A single phaser bank would be more than enough to keep them off our back."
"Perhaps it is an enhancement we can investigate upon our return to the Enterprise," Taurik offered. Were it not for their present circumstances, La Forge might have laughed at the Vulcan's deadpan reply.
Suddenly, inspiration struck.
"Ease our speed back," he said. "Let them catch up." Though he did not look up from his station, he could feel stares from both Taurik and Faeyahr.
"Closer?" Faeyahr repeated. "Commander La Forge, what are you doing?"
"I've got an idea," La Forge said, his fingers moving over his console.
The results of his actions were immediately noticeable to Taurik. "Commander, you have instructed the computer to open our port engine coolant interlock. I submit that this is not the best time to purge our plasma exhaust."
"Let them get closer," La Forge said, his attention focused on his console's status readings. "This is going to get a little dicey." Looking to Taurik, he asked, "You ever hear of the Kolvoord Starburst maneuver?"
"I have," Taurik replied. "It is an intricate aerobatic maneuver involving five ships traveling in tight formation, then crisscrossing each other's path at close range and igniting their drive plasma. The resulting visual effect is said to be quite stimulating. Is it your intention to vent and ignite our drive plasma in a similar manner?"
La Forge nodded. "Thank our friends for shooting up the starboard engine and giving me the idea." Of course, he did not need to say that it was a dangerous maneuver, almost as likely to flash back and destroy the shuttle itself as it was to ignite the plasma trail he was about to create.
Of course, Taurik held no such misgivings.
"Commander," Taurik said, "Starfleet Academy banned cadets from attempting the maneuver more than a century ago due to the extreme risks involved."
"I know all about the risks," La Forge replied. The maneuver had been attempted illegally by five Academy cadets a decade ago, one of them Wesley Crusher, and had resulted in the death of one of the participants.
So let's hope I have better luck, he thought grimly.
Taurik pointed to the sensor display. "Ship approaching aft, range two kilometers and closing."
"Hang on," La Forge said, watching the monitor and waiting until the gap separating the Ballard from the incoming skiff was less than a kilometer before his finger stabbed a control on his console.
The interior bulkheads vibrated as the drive plasma vented and made contact with the superhot engine exhaust. In his mind's eye he saw the ignited plasma trail flared out behind the shuttlecraft, likely washing over the forward surface of their pursuer's ship.
Then the ship rocked violently to starboard and alarms blared inside the cabin as consoles throughout the shuttle's interior blinked crazily or went dark altogether. Taurik was thrown to the deck but La Forge managed to stay in his chair, and found himself scrambling to keep the ship from careening out of control.
"What's happening?" Faeyahr cried out.
"We've lost the port engine," the chief engineer replied, pinned into his chair as he fought to reach his console. "Inertial dampeners are out."
Regaining his seat, Taurik reported, "Attitude control is offline, Commander. I am having difficulty maintaining our course."
"Restart the starboard engine," La Forge ordered. "It's all we've got left." Glancing briefly at the sensor display, he added, "That blast must have damaged the other ship, too. It looks like they're drifting."
"They may be the more fortunate," Taurik said. "Helm control is becoming more difficult, and the starboard engine has lost too much plasma. It will not restart."
This is definitely not good, La Forge thought as he studied the status monitors. Systems all over the ship had been affected by the plasma explosion, and the trouble was mounting with each passing second.
"Commander!" he heard Faeyahr yell out from behind him and the chief engineer looked up to see the immense asteroid looming in the viewport.
"Taurik!" he shouted. "We need thruster control now!"
"I am trying, sir," the Vulcan replied. "The controls are sluggish."
Even from this distance, La Forge he could make out the rock's craggy features, towering peaks contrasting sharply with deep canyons cloaked in shadow. A ship the size of their shuttlecraft could fall into one of the asteroid's numerous chasms and never be found.
And they were heading straight for it.
## Chapter Thirty-one
"HE'S STILL RUNNING his own internal diagnostics, sir," Commander Riker's voice said through Picard's combadge. "So far, he hasn't said anything else since it happened."
Standing in the Zahanzei Council's meeting chambers on the Dokaalan central habitat, Picard frowned as he listened to his first officer's report. "And a cause still hasn't been found?"
"No, sir. The engineering staff is working on it, but they don't know if the problem is with Data himself or if it's the result of an external source. They'll know more when Data's diagnostics are complete."
In the years since Picard had known him, Data had proven to be a startlingly robust individual, a pinnacle of cybernetic engineering as envisioned by his creator, Dr. Noonien Soong. Though he had suffered injury on several occasions, those instances were almost always caused by the influence of an outside element working against him.
Therefore, to hear about his sudden incapacitation was troubling to say the least.
"While I have full confidence in the engineering staff," Picard said, "no one knows Data's systems like Geordi. Has there been any word from him?"
"Not yet, sir," Riker replied, "but communication between here and Ijuuka is compromised due to the radiation field, and he's not supposed to be back for a few hours."
The captain sighed in resignation. "Keep me informed, Number One. Picard out." With the connection severed, he was once again reminded that there were occasions where he could only stand by and wait for others to do their jobs, and that this was one of them.
Such is the double-edged sword of command.
For a brief moment Picard felt a twinge of apprehension. He considered himself a self-reliant individual unafraid to make even the most difficult decisions required of his position, but as a leader he had long ago learned the virtue of accepting and acting on the counsel of the officers under his command. It was therefore disconcerting when one or more of his most trusted advisors was unavailable to him, an admission he had not made even to Deanna Troi during their private conversations.
Logic quickly reasserted itself, however. La Forge was off the ship carrying out Picard's orders and would be back in short order. Once apprised about Data, the chief engineer would expend all energy and resources to determine a cause and a solution for his friend's condition.
So, why did Picard still feel uneasy?
"Captain?" Troi prompted as she stepped closer, having stood to the side as Picard received Riker's report.
Shaking his head, he said, "I don't like the timing of this, Counselor. It's decidedly convenient given the circumstances." He glanced over his shoulder to where Hjatyn and other members of the council stood in a circle talking amongst themselves. "For the sake of appearances, however, I think it best that we not discuss this in front of the others." If something odd was going on, he did not want to alert anyone to the idea that he might be suspicious.
Troi replied, "I understand, sir."
"Have you detected anything else from any of the council members worth noting?"
"Nothing more than I already reported, sir," the counselor said. "The security minister, Nidan, maintains a suspicious attitude, but I attribute that to the nature of his responsibilities. Hjatyn has been most forthcoming regardless of the questions I've asked, but I still sense caution when he answers even though he does a remarkable job of concealing it. Other members of the council continue to demonstrate a growing sense of comfort and trust at our presence." Frowning, she added, "And there are those whose enthusiasm seems to have dampened somewhat since our arrival."
"How so?" Picard asked.
Pausing a moment before replying, Troi shrugged. "It's almost as though one or two of the council members have had a change of heart, or perhaps they've begun to doubt their original feelings about us. Minister Creij, for example. At our first meeting, she was among the most vocal of our supporters, but now I sense hesitation when she talks to me."
"Is it possible," Picard said, "that she feels our presence here might somehow be threatening to her work?" They had quickly learned that the Dokaalan were a proud people, steadfastly determined to see the transformation of Ijuuka into their new home through their own efforts. Though Minister Creij had welcomed any suggestions by the Enterprise crew that might accelerate the terraforming process, had she done so simply for the sake of politeness? Did she privately harbor feelings of resentment and fear at being upstaged by people with advanced technology?
Troi replied, "I don't know, sir, but my instincts tell me that's not the reason."
The captain nodded. "Well then, we should continue as we have and see where it takes us." It was a weak and undesirable plan, but given the circumstances it was the only course of action open to him.
For now, anyway.
Their attention was drawn to a door opening at the far end of the council chambers, allowing Dr. Crusher to enter. Picard knew that the physician had transferred her remaining Dokaalan patients, left over from the mining outpost rescue operation, to the central habitat from the Enterprise several hours earlier. According to her last report, she had been monitoring their condition since then, and he could see by the expression on her face that she too still seemed to be troubled.
"Doctor?" he prompted as she approached them.
Crusher attempted to affect a smile, but it was forced and she seemed to realize it as she exhaled in apparent frustration. "I've just spent the last three hours in their medical center with my patients. Three hours ago most of their major internal organs were on the verge of collapse, and there was nothing I could do to stop it. Now their condition is improving with every minute, and I didn't do a damn thing to cause it."
"You're still learning about Dokaalan medicine, Beverly," Troi offered. "Surely their doctors know how best to treat their own people, even though you've done wonderfully in such a short time."
Shaking her head, Crusher replied, "I could accept that if it were the case, but their doctors didn't do anything either. Besides, it wasn't just the five miners we rescued. One of their doctors was on the Enterprise with me, and he began to present the same symptoms as the others." Waving her hand to indicate their surroundings, she added, "Something here is affecting their physiology, something that causes a negative reaction when its influence is removed, and I think I've got an idea what."
"The radiation," Picard said.
"Exactly," the doctor replied. "It was like what happens to addicts suffering withdrawal symptoms when whatever substance causing the addiction is removed."
Picard nodded. "On the ship and with the shields up, the radiation would be blocked, at least enough to deprive the Dokaalan of whatever benefits they receive from the radiation." It was an interesting notion, he conceded. "Could it be a by-product of their having lived out here all these years? Their physiology would have had to acclimate to the environment, but in only a few hundred years?"
"It's not out of the question, Captain," Troi said. "Remember the colonists on Tau Cygna V?"
It took Picard a moment of sifting through his memory to recall the Enterprise's mission to that planet, where a Federation colony ship, the S.S. Artemis, had ended up. The mission had arisen after the Sheliak, a reclusive race with whom the Federation had a strained relationship for more than a century, exercised their rights as owners of Tau Cygna V and demanded the colonists leave or face extermination. Picard had managed to resolve the dispute between the Sheliak and the colonists, but only after a great deal of assistance from Data.
"Their descendants eventually adapted to the hyperonic radiation on that planet," Troi continued. "It's entirely possible that something similar has happened here."
Crusher replied, "I agree. I'll need time to set up some new tests to be sure, but it would explain their reaction both here and on the ship."
"Proceed as you think best, Doctor," Picard said. Shaking his head, he added, "Well, this will certainly make my next report to Admiral Nechayev more interesting." He had dispatched a status report the previous evening, transmitting it along with his log entries back to Starfleet Command via subspace. With the background radiation still presenting an obstacle to communications, Data had programmed an unmanned probe to navigate out of the asteroid field and to the perimeter of the Dokaalan system in order to transmit the information.
No doubt that report already was stirring up controversy in the hallways of power back on Earth, and Picard was reasonably sure that Alynna Nechayev was enjoying every minute of it. It was an image that almost made the captain smile.
But not for long.
An earsplitting klaxon suddenly blared, echoing in through the council chambers and nearly making Picard jump out of his skin. "What is that?" he asked.
"It is an emergency alert signal," Hjatyn said as he broke from the circle of other council members, shuffling as quickly as his aged body would carry him toward the control room Picard and his people had visited earlier. The captain followed after with Troi and Crusher behind him.
The command center was a rush of activity, with Dokaalan technicians scrambling from console to console and warning lights flashing for attention on a number of workstations around the room. Though the alarm was not sounding in here, Picard's ears were still assaulted by bursts of static washing over someone yelling out in a panicked voice.
"What is it?" Hjatyn asked as he entered the room.
Turning from where he watched over the shoulder of a technician manning one computer console, Nidan replied, "Mining Station Twelve is reporting an explosion. We are still trying to gather information, First Minister."
At that moment, Picard's combadge chirped for attention and Riker's voice called out, "Riker to Captain Picard."
"Picard here. Go ahead, Number One."
* * *
"Sir, we're picking up a massive detonation on one of the nearby mining outposts," Riker said as he sat in the captain's chair on the bridge of the Enterprise. "Sensor scans are still fuzzy, but it was large enough to detect even through the interference."
"Are you able to ascertain the extent of the damage?" Picard asked.
Rising from the center seat, Riker replied, "No sir, we'd have to get closer for that. Request permission to render assistance."
"Absolutely," the captain said. "Set a course for the outpost immediately. We'll catch up in the shuttlecraft."
Riker nodded to Kell Perim at the conn. "Prepare to get under way, Lieutenant." He saw the look of uncertainty in Perim's eyes, but the Trill officer said nothing as she turned back to her station and began entering the necessary instructions to her console.
"Number One," Picard's voice said over the intercom, "Minister Hjatyn has told me that there are more than eight hundred people on the outpost, and reports are coming in that several areas have experienced explosive decompression. Their life-support systems appear to have sustained damage as well. The Dokaalan are dispatching rescue ships, but they won't be able to get there as quickly as the Enterprise. Time is of the essence, Will."
"We're on it, Captain. Stand by," Riker said as he stepped toward the conn and ops stations and laid a hand on Perim's shoulder. "Kell, you sure you can handle this? If you think you need help, just say the word."
There was no mistaking the nervousness on the lieutenant's face even as she nodded in response. "I think so, Commander. I'm no Data, but I'll have the computer helping me."
While she was of course no match for Data's superior reflexes and experience, Perim was an exceptional pilot in her own right. Riker had faith in her ability to navigate the Enterprise through the asteroid field, knowing she would call for assistance if she felt it was warranted.
Smiling, Riker patted her shoulder. "You'll do fine," he said before turning away from the forward bridge stations. "We're getting under way now, Captain."
"Good," Picard replied. "We'll be right behind you."
"We'll leave a light on for you, sir," the first officer said, smiling to himself as he settled once more into the command chair. "Helm, move us out," he said.
Perim nodded. "Aye, sir."
On the main viewer, the colossal asteroid that was home to the Dokaalan's central habitat drifted beyond the left edge of the screen as the Enterprise turned on its axis to align itself with its new heading. Seconds later, the shift was over and the ship began to move forward.
"Lieutenant Vale," he said, "contact sickbay and notify Dr. Tropp to prepare triage measures, just like last time. Cargo holds, shuttlebays, whatever he needs. Let him know that Dr. Crusher will be in contact shortly with more instructions, but for now he's in charge."
"Aye, sir," Vale replied.
All around Riker, members of the crew set to their various tasks. Left with nothing do to except sit quietly and wait for the situation to evolve, he once again noted the ratio of alpha-shift crew members to those brought on duty as replacements for officers otherwise unavailable for one reason or another.
While he knew that every member of the crew was qualified to carry out his or her responsibilities, Riker could not deny the unease he felt at not having his most trusted colleagues by his side. He glanced at the chair to his left, the one normally occupied by Deanna Troi and which now of course was conspicuously empty.
Watching Perim's fingers move over her console, Riker tried to conjure some of the confidence he hoped to have given her for himself. Despite her own skills, it was hard not to think of the sometimes harrowing passage Data had provided during the Enterprise's first journey through the asteroid field. Though the android had shown no signs of strain or unease during that earlier crossing, Riker had to believe that it had been a trying experience even for his friend's extraordinary talents.
"Number One," Picard said, interrupting his thoughts. "We've received new information from the outpost. They believe the explosion wasn't an accident."
A sudden chill ran down Riker's spine at the report. Someone had deliberately caused such catastrophic damage, possibly resulting in the deaths of hundreds of people? There had been discussions about those among the Dokaalan opposed to the terraforming process and how some had taken to sabotage, but on this scale? If such people were indeed operating in the shadows among the Dokaalan, what else were they capable of doing? Did they pose a threat to the Enterprise and if so, would they attempt to take action against the ship as he and the crew tried to render assistance to the outpost victims?
There's nothing you can do about that now, he admonished himself. Shut up and play the cards you're dealt.
"Understood, sir," he said simply. What else was there to say? It did not matter to the people on the outpost that there might be others seeking to harm him and the crew. It was not relevant to those same people currently in distress that Data was not here, or that several of the people he trusted most were off ship. The people on that asteroid could not wait for circumstances to be ideal before a rescue was attempted. They were in trouble, they were dying, and they needed help.
Right now.
##
**About the Authors**
**DAYTON WARD** has been a fan of Star Trek since conception (his, not the show's). After serving for eleven years in the U.S. Marine Corps, he discovered the private sector and the piles of cash to be made there as a software engineer. He got his start in professional writing by having stories selected for each of Pocket Books' first three Star Trek: Strange New Worlds writing contests. In addition to his various writing projects with Kevin Dilmore, Dayton is the author of the Star Trek novel In the Name of Honor and the science fiction novel The Last World War. Though he currently lives in Kansas City with his wife, Michi, Dayton is a Florida native and still maintains a torrid long-distance romance with his beloved Tampa Bay Buccaneers. Readers interested in contacting Dayton or learning more about his writing are encouraged to venture to his Internet cobweb collection at **www.daytonward.com**.
After 15 years as a newspaper reporter and editor, **KEVIN DILMORE** turned his full attention to his freelance writing career in 2003. Since 1997, he has been a contributing writer to Star Trek Communicator, writing news stories and personality profiles for the bimonthly publication of the Official Star Trek Fan Club. Look for Kevin's interviews with some of Star Trek's most popular authors in volumes of the Star Trek Signature Editions. On the fictional side of things, his story "The Road to Edos" was published last year in the Star Trek: New Frontier anthology No Limits. With Dayton Ward, he has also written a story for the anthology Star Trek: Tales of the Dominion War and seven installments of the continuing e-book series Star Trek: S.C.E.—with more to come. A graduate of the University of Kansas, Kevin lives in Prairie Village, Kansas, with his wife, Michelle, and their three daughters.
We hope you enjoyed reading this Pocket Books eBook.
* * *
Join our mailing list and get updates on new releases, deals, bonus content and other great books from Pocket Books and Simon & Schuster.
CLICK HERE TO SIGN UP
or visit us online to sign up at
eBookNews.SimonandSchuster.com
This book is a work of fiction. Names, characters, places and incidents are products of the authors' imaginations or are used fictitiously. Any resemblance to actual events or locales or persons, living or dead, is entirely coincidental.
www.SimonandSchuster.com
An Original Publication of POCKET BOOKS
POCKET BOOKS, a division of Simon & Schuster, Inc.
1230 Avenue of the Americas, New York, NY 10020
Copyright © 2004 by Paramount Pictures. All Rights Reserved.
STAR TREK is a Registered Trademark of Paramount Pictures.
This book is published by Pocket Books, a division of Simon & Schuster, Inc., under exclusive license from Paramount Pictures.
All rights reserved, including the right to reproduce this book or portions thereof in any form whatsoever. For information address Pocket Books, 1230 Avenue of the Americas, New York, NY 10020
ISBN: 0-7434-8891-1
ISBN-13: 978-0-7434-8891-4
POCKET and colophon are registered trademarks of Simon & Schuster, Inc.
Visit us on the World Wide Web:
www.startrek.com
|
Design and Control of the Adjustable Turn-ratio LLC Converter for High-Efficiency Operation of Wired/Wireless Integrated EV Charging System This paper proposes an LLC resonant converter with an adjustable turn-ratio of the transformer to replace phase-shift (PS) control for high-efficiency operation in a wired/wireless integrated EV charging system (ICS) for electric vehicles (EVs). To design the LLC converter of the ICS, the range of the dc-link voltage by the characteristics of inductive power transfer (IPT) converter and the design specification are derived by simulation. Considering the voltage gain of the LLC converter by each parameter, the parameters of the LLC converter are determined and a multi-tap transformer is manufactured. After that, the LLC converter is operated in ICS, by PS control and the adjustable turn-ratio transformer. The feasibility of the adjustable turn-ratio transformer is verified by comparing the efficiency of the LLC converter. |
Metallurgical Failure Analysis of Intramedullary Nail Used for Femoral Fracture Stabilization Currently orthopedics challenge is the use of intramedullary nails to straighten diaphyseal femoral fractures. In this paper it was conducted a case study on an intramedullary nail used for femoral fracture stabilization, in the case of one young patient. The evolution was unfavorable to the fracture site and the implant failed after three month of first surgical intervention. Intramedullary nail dimensions were 300mm length and 10mm in diameter. The following investigations were made in order to establish the failure causes: determination of the chemical composition through spectral analysis, macrostructural analysis using stereomicroscopy, optical microstructural analysis using optical microscopy, fractographic analysis using scanning electron microscopy. The final conclusions showed that the metallic biomaterial used for manufacturing the intramedullary nail was approximately an austenitic stainless steel AISI 316L, but with major microstructural defects. Macro-structural analysis revealed the presence of two zones of cracking, which are very rare at austenitic stainless steels. Also breaking with a fragile character has radial front tear propagation. In longitudinal section, cracks were evidenced due to the extraction operation and also the presence of corrosion products was shown. From fractographic analysis it was determined that intramedullary nail failure was predominantly through the mechanism of brittle fracture that took place at the point of maximum bending of the implant fragile. |
/************************************************************
*
* CyberLink for C
*
* Copyright (C) <NAME> 2005
*
* File: cmediarenderer.h
*
* Revision:
* 2009/06/11
* - first release.
*
************************************************************/
#ifndef _CG_CLINKCAV_MEDIARENDERER_H_
#define _CG_CLINKCAV_MEDIARENDERER_H_
#include <mupnp/upnp.h>
#include <mupnp/std/av/cupnpav.h>
#ifdef __cplusplus
extern "C" {
#endif
#undef CG_CLINKCAV_USE_UPNPSTD_XML
/****************************************
* Struct
****************************************/
typedef struct _mUpnpAvRenderer {
mUpnpMutex* mutex;
mUpnpDevice* dev;
CG_UPNPAV_HTTP_LISTENER httplistener;
CG_UPNPAV_ACTION_LISTNER actionListner;
CG_UPNPAV_STATEVARIABLE_LISTNER queryListner;
mUpnpAvProtocolInfoList* protocolInfoList;
void* userData;
} mUpnpAvRenderer;
/****************************************
* Constants (Media Server)
****************************************/
#define CG_UPNPAV_DMR_DEVICE_TYPE "urn:schemas-upnp-org:device:MediaRenderer:1"
#define CG_UPNPAV_DMR_DEFAULT_HTTP_PORT 38520
/****************************************
* Constants (Rendering Control)
****************************************/
#define CG_UPNPAV_DMR_RENDERINGCONTROL_SERVICE_TYPE "urn:schemas-upnp-org:service:RenderingControl:1"
#define CG_UPNPAV_DMR_RENDERINGCONTROL_GETVOLUME "GetVolume"
#define CG_UPNPAV_DMR_RENDERINGCONTROL_GETMUTE "GetMute"
#define CG_UPNPAV_DMR_RENDERINGCONTROL_SETVOLUME "SetVolume"
#define CG_UPNPAV_DMR_RENDERINGCONTROL_SETMUTE "SetMute"
#define CG_UPNPAV_DMR_RENDERINGCONTROL_CURRENTMUTE "CurrentMute"
#define CG_UPNPAV_DMR_RENDERINGCONTROL_DESIREDMUTE "DesiredMute"
#define CG_UPNPAV_DMR_RENDERINGCONTROL_CURRENTVOLUME "CurrentVolume"
#define CG_UPNPAV_DMR_RENDERINGCONTROL_DESIREDVOLUME "DesiredVolume"
#define CG_UPNPAV_DMR_RENDERINGCONTROL_LASTCHANGE "LastChange"
/****************************************
* Constants (Connection Manager)
****************************************/
#define CG_UPNPAV_DMR_CONNECTIONMANAGER_SERVICE_TYPE "urn:schemas-upnp-org:service:ConnectionManager:1"
#define CG_UPNPAV_DMR_CONNECTIONMANAGER_HTTP_GET "http-get"
#define CG_UPNPAV_DMR_CONNECTIONMANAGER_GET_PROTOCOL_INFO "GetProtocolInfo"
#define CG_UPNPAV_DMR_CONNECTIONMANAGER_SOURCE "Source"
#define CG_UPNPAV_DMR_CONNECTIONMANAGER_SINK "Sink"
#define CG_UPNPAV_DMR_CONNECTIONMANAGER_CURRENTCONNECTIONIDS "CurrentConnectionIDs"
#define CG_UPNPAV_DMR_CONNECTIONMANAGER_SOURCEPROTOCOLINFO "SourceProtocolInfo"
#define CG_UPNPAV_DMR_CONNECTIONMANAGER_SINKPROTOCOLINFO "SinkProtocolInfo"
/****************************************
* Constants (AVTransport)
****************************************/
#define CG_UPNPAV_DMR_AVTRANSPORT_SERVICE_TYPE "urn:schemas-upnp-org:service:AVTransport:1"
#define CG_UPNPAV_DMR_AVTRANSPORT_GETTRANSPORTINFO "GetTransportInfo"
#define CG_UPNPAV_DMR_AVTRANSPORT_STOP "Stop"
#define CG_UPNPAV_DMR_AVTRANSPORT_LASTCHANGE "LastChange"
#define CG_UPNPAV_DMR_AVTRANSPORT_CURRENTTRANSPORTSTATE "CurrentTransportState"
#define CG_UPNPAV_DMR_AVTRANSPORT_CURRENTTRANSPORTSTATUS "CurrentTransportStatus"
#define CG_UPNPAV_DMR_AVTRANSPORT_CURRENTSPEED "CurrentSpeed"
#define CG_UPNPAV_DMR_AVTRANSPORT_CURRENTTRANSPORTSTATE_NOMEDIAPRESENT "NO_MEDIA_PRESENT"
#define CG_UPNPAV_DMR_AVTRANSPORT_CURRENTTRANSPORTSTATE_STOPPED "STOPPED"
#define CG_UPNPAV_DMR_AVTRANSPORT_CURRENTTRANSPORTSTATUS_OK "OK"
/****************************************
* Public Functions
****************************************/
mUpnpAvRenderer* mupnp_upnpav_dmr_new();
void mupnp_upnpav_dmr_delete(mUpnpAvRenderer* dmr);
#define mupnp_upnpav_dmr_getdevice(dmr) (dmr->dev)
#define mupnp_upnpav_dmr_start(dmr) mupnp_device_start(dmr->dev)
#define mupnp_upnpav_dmr_stop(dmr) mupnp_device_stop(dmr->dev)
#define mupnp_upnpav_dmr_lock(dmr) mupnp_mutex_lock(dmr->mutex)
#define mupnp_upnpav_dmr_unlock(dmr) mupnp_mutex_unlock(dmr->mutex)
#define mupnp_upnpav_dmr_setfriendlyname(dmr, value) mupnp_device_setfriendlyname(dmr->dev, value)
#define mupnp_upnpav_dmr_getfriendlyname(dmr) mupnp_device_getfriendlyname(dmr->dev)
#define mupnp_upnpav_dmr_setudn(dmr, value) mupnp_device_setudn(dmr->dev, value)
#define mupnp_upnpav_dmr_getudn(dmr) mupnp_device_getudn(dmr->dev)
#define mupnp_upnpav_dmr_sethttplistener(dmr, func) (dmr->httplistener = func)
#define mupnp_upnpav_dmr_gethttplistener(dmr) (dmr->httplistener)
#define mupnp_upnpav_dmr_setactionlistener(dmr, func) (dmr->actionListner = func)
#define mupnp_upnpav_dmr_getactionlistener(dmr) (dmr->actionListner)
#define mupnp_upnpav_dmr_setquerylistener(dmr, func) (dmr->queryListner = func)
#define mupnp_upnpav_dmr_getquerylistener(dmr) (dmr->queryListner)
#define mupnp_upnpav_dmr_setuserdata(dmr, data) (dmr->userData = data)
#define mupnp_upnpav_dmr_getuserdata(dmr) (dmr->userData)
void mupnp_upnpav_dmr_addprotocolinfo(mUpnpAvRenderer* dmr, mUpnpAvProtocolInfo* info);
#define mupnp_upnpav_dmr_getprotocolinfos(dmr) mupnp_upnpav_protocolinfolist_gets(dmr->protocolInfoList)
void mupnp_upnpav_dmr_setsinkprotocolinfo(mUpnpAvRenderer* dmr, char* value);
char* mupnp_upnpav_dmr_getsinkprotocolinfo(mUpnpAvRenderer* dmr);
void mupnp_upnpav_dmr_setsourceprotocolinfo(mUpnpAvRenderer* dmr, char* value);
char* mupnp_upnpav_dmr_getsourceprotocolinfo(mUpnpAvRenderer* dmr);
void mupnp_upnpav_dmr_setcurrentconnectionids(mUpnpAvRenderer* dmr, char* value);
char* mupnp_upnpav_dmr_getcurrentconnectionids(mUpnpAvRenderer* dmr);
void mupnp_upnpav_dmr_setavtransportlastchange(mUpnpAvRenderer* dmr, char* value);
char* mupnp_upnpav_dmr_getavtransportlastchange(mUpnpAvRenderer* dmr);
void mupnp_upnpav_dmr_setrenderingcontrollastchange(mUpnpAvRenderer* dmr, char* value);
char* mupnp_upnpav_dmr_getrenderingcontrollastchange(mUpnpAvRenderer* dmr);
#ifdef __cplusplus
}
#endif
#endif
|
When an oil well is first drilled and completed, the fluids (such as crude oil) may be under natural pressure that is sufficient to produce on its own. In other words, the oil rises to the surface without any assistance.
In many oil wells, and particularly those in fields that are established and aging, natural pressure has declined to the point where the oil must be artificially lifted to the surface. Subsurface, or downhole, pumps are located down in the well below the level of the oil. A string of sucker rods extends from the pump up to the surface to a pump jack device, or beam pump unit. A prime mover, such as a gasoline or diesel engine, or an electric motor, or a gas engine on the surface causes the pump jack to rock back and forth, thereby moving the string of sucker rods up and down inside of the well tubing.
The string of sucker rods operates the subsurface pump. A typical pump has a plunger that is reciprocated inside of a barrel by the sucker rods. The barrel has a standing one-way valve, while the plunger has a traveling one-way valve, or in some pumps the plunger has a standing one-way valve, while the barrel has a traveling one-way valve. Reciprocation charges a chamber between the valves with fluid and then lifts the fluid up the tubing toward the surface.
The clearance between the plunger and barrel allows one to reciprocate easily and smoothly with respect to the other. This clearance is large enough to be lubricated by the downhole fluids and small enough to prevent leakage of fluid around the pump valves.
In normal use, the pump barrel and plunger experience wear. The wear leads to loss of performance of the lifting ability of the pump. Well fluid leaks around the traveling valve and the plunger; consequently the differential pressures across the valve that are necessary for its operation are unable to develop.
To repair the pump, the pump must be pulled from the well. The components are inspected and any worn components are replaced. Pulling the pump and replacing components results in downtime for the well and expense in the operation of the well. In normal use, a pump may last between three months to a year before it is pulled for repair.
In wells that produce sand, a pump may last only a few weeks. The sand abrades the ends of the reciprocating component and eventually enters the clearance between the plunger and the barrel, causing wear. Consequently, the pump components must be replaced more often.
Barrels and plungers are typically made of relatively soft material, having Rockwell hardness of C20. The barrels and plungers could be made of a harder material but they would be brittle and not as durable in the well. Instead, the barrels and plungers are treated on their wear surfaces so as to harden the wear surfaces. Such surface treatments include carbonizing, chroming and spray metal. Yet these treated surfaces quickly degrade in wells that produce sand. |
Asthma prevalence, knowledge, and perceptions among secondary school pupils in rural and urban coastal districts in Tanzania Background Asthma is a common chronic disease of childhood that is associated with significant morbidity and mortality. We aimed to estimate the prevalence of asthma among secondary school pupils in urban and rural areas of coast districts of Tanzania. The study also aimed to describe pupils perception towards asthma, and to assess their knowledge on symptoms, triggers, and treatment of asthma. Methods A total of 610 pupils from Ilala district and 619 pupils from Bagamoyo district formed the urban and rural groups, respectively. Using a modified International Study of Asthma and Allergies in Childhood (ISAAC) questionnaire, a history of diagnosed asthma or the presence of a wheeze in the previous 12 months was obtained from all the studied pupils, along with documentation of their perceptions regarding asthma. Pupils without asthma or wheeze in the prior 12 months were subsequently selected and underwent a free running exercise testing. A≥20% decrease in the post-exercise Peak Expiratory Flow Rate (PEFR) values was the criterion for diagnosing exercise-induced asthma. Results The mean age of participants was 16.8 (±1.8) years. The prevalence of wheeze in the past 12 months was 12.1% in Bagamoyo district and 23.1% in Ilala district (p<0.001). Self-reported asthma was found in 17.6% and 6.4% of pupils in Ilala and Bagamoyo districts, respectively (p<0.001). The prevalence of exercise-induced asthma was 2.4% in Bagamoyo, and 26.3% in Ilala (P<0.002). In both districts, most information on asthma came from parents, and there was variation in symptoms and triggers of asthma reported by the pupils. Non-asthmatic pupils feared sleeping, playing, and eating with their asthmatic peers. Conclusion The prevalence rates of self-reported asthma, wheezing in the past 12 months, and exercise-induced asthma were significantly higher among urban than rural pupils. Although bronchial asthma is a common disease, pupils perceptions about asthma were associated with fear of contact with their asthmatic peers in both rural and urban schools. Background Asthma is one of the most common childhood disorders that is associated with significant morbidity. There is wide variation in asthma prevalence across countries throughout the world. In Phase One of the ISAAC study, the prevalence of asthma symptoms ranged from less than 5% in developing countries to more than 20% in developed countries. The prevalence of asthma has also been increasing over the past few decades, with the highest increase seen among children and young adults living in the inner cities and in regions where the prevalence had previously been low. This increase has mainly been attributed to the increasing urbanization in developing countries, including those in Africa. The traditional rural lifestyle and early childhood exposure to infectious agents in rural areas are believed to be protective against asthma and allergic diseases. Infection in early childhood, facilitated by unhygienic conditions within families and communities, has been shown to prevent the development of allergic diseases, including asthma. Urbanization on the other hand is associated with a reduction in the frequency of childhood infections, due to the increased use of antibiotics, improved personal and public hygiene, and changes in diet. As a result of these differences in frequency of early childhood infections, there is a lower prevalence of asthma in rural areas as compared to urban areas. In addition, urbanisation is associated with increased environmental pollution, sedentary lifestyle, obesity and unhealthy diet; factors associated with increased risk of asthma. There are also variations in beliefs and perceptions on asthma, due to differences in the level of education between urban and rural areas. These differences not only affect treatment of asthma, but also contribute to the increase in morbidity and mortality of the disease. This study sought to estimate the prevalence of asthma, and to assess perceptions with regards to asthma among secondary school pupils in the rural and urban coast of Tanzania. Study design This was a cross-sectional study that was conducted to determine the prevalence of asthma and information about symptoms, triggers, and perceptions of asthma among form I -IV secondary school pupils in the Ilala and Bagamoyo districts in Tanzania. Study population The study involved secondary school pupils from Ilala and Bagamoyo districts, both of which are located along the Indian Ocean. Ilala is one of the three districts of Dar es Salaam, Tanzania's largest commercial city (population 634,924), and one of the most industrialized and polluted districts in the country. Bagamoyo is a rural colonial town with a population of 228,967, which has no industries and depends largely on farming and fishing. According to the Ministry of Education and Culture, there were 18 and 9 secondary schools located in Ilala and Bagamoyo, respectively. With simple random selection, six secondary schools were selected from each district, and from these schools 27 pupils from each of the four classes were randomly selected. To minimise the influence of other disease conditions with symptoms similar to asthma, pupils with known chronic heart diseases were excluded from the study. The sample size was calculated using a sampling error of 2%, 90% power, and anticipated population prevalence of asthma of 6%. These parameters gave a minimum sample size of 542 pupils from each district, which was increased by 20% to a total of 1301 pupils to account for non-response. Procedures and outcomes The data were collected in 2007 using a modified ISAAC questionnaire. Additional questions on pupils' perceptions regarding asthma and their knowledge of symptoms and triggers of asthma were included in the questionnaire. The original English version of the questionnaire was translated into Swahili by two independent health professionals. In order to check for any differences when compared with the original English version, a back translation into English was then done by another qualified translator. The Swahili questionnaire was then piloted among 25 pupils in Ilala district who were selected from a school which was not part of the studied population. It was administered by researchers to assess if all of the respondents interpreted questions in the same way, whether the Swahili interpretation for words such as "wheeze" and "asthma" would be understood by the pupils in the study, and whether each question measured what the study was intended to measure. No focus group discussion was done, and the information from the pilot was used to develop the final Swahili version of the questionnaire. Permissions to involve pupils in the study were initially sought from the district educational authorities, headteachers, and class teachers. During the initial visit to each school, pupils were informed about the study objectives and procedures. Pupils aged 18 years or older signed consent forms themselves, if they agreed to participate in the study. For pupils less than 18 years old and not living in the school campuses, information sheets explaining the study's purpose and procedures were provided to their parents/guardians. Parents/guardians were requested to give signed consent if they agreed to allow their children to participate in the study. For those pupils living in hostels, a witnessed consent from their teachers (matrons/patrons) was used. In addition, all pupils younger than 18 years were required to sign assent forms. All information sheets, consent and assent forms, and validated questionnaires were in Swahili. Subsequent visits were arranged to collect information on consented pupils. Of 1301 pupils selected for interview, 1229 (94.5%) agreed to participate, and a total of 619 pupils from Bagamoyo and 610 pupils from Ilala were enrolled. Seventy two pupils did not participate in the study for various reasons. Of these, 6 pupils had known cardiac diseases. None of them had a chronic respiratory disease or asthma. In addition, sixty six pupils were excluded from the study for various reasons including acute illnesses during the study days (malaria-2 pupils, gastroenteritis-2 pupils and pneumonia-3 pupils) and either refusal to participate or non-availability at school during the study days (59 pupils). Using self-administered questionnaires, a history of "diagnosed" asthma or the presence of wheezing in the prior 12 months was obtained from all the pupils studied. Each pupil's age was documented, and anthropometric data including height and weight, were measured. Although all pupils knew their dates of birth, this information was verified by checking school records. Their standing heights were measured using a specially designed portable stadiometer to the nearest 0.1 centimetre. Body weight was determined to the nearest 0.1 kg with a calibrated digital scale (SECA, Type 803, United Kingdom), with the subject standing and wearing light clothes. Peak expiratory flow rates (PEFR) were assessed using Micro-Spirometers (Micro Medical Limited England). After a group demonstration and participant practice using the peak flow meter, each subject was requested to perform three peak flows, from which the highest value was recorded as the pupil's PEFR. Pupils without self-reported asthma or wheeze were subsequently exercised by freely running for six minutes on a plane football ground. Within five to ten minutes after exertion, each pupil performed at least three PEFR measurements, supervised by the same observer. The measurement with the highest reading was recorded. The percentage fall in the post-exercise PEFR was then calculated as follows: Exercise-induced asthma was defined as a fall of postexercise PEFR by ≥ 20%. The study was approved by the Ethics Committee of the Muhimbili University College of Health and Allied Sciences (MUCHS). Statistical analysis Data were entered, cleaned, and analysed using the Statistical Package for Social Sciences version 10.0 (SPSS Inc., Chicago, IL). Means and standard deviation were calculated for quantitative data. We used the Chi-squared test to determine the associations between categories. Pearson correlation was used to find the significant relationship between PEFR and height of a pupil. A p-value < 0.05 was considered statistically significant. Characteristics of the study population A total of 1229 pupils participated in the study. The mean (SD) age of participants was 16.8 (±1.8) years, 68% of them being less than 17 years old, with the Ilala district having a significantly younger group than Bagamoyo (Table 1). Overall, there were more boys (59.2%) than girls involved in the study. Prevalence of self-reported asthma and wheeze The prevalence of self-reported asthma and wheeze among pupils in the studied areas is presented in Table 2. The overall prevalence of self-reported asthma was 11.8%. Pupils from the schools in Ilala district had a higher prevalence of self-reported asthma as compared to those in Bagamoyo (17.1% versus 6.6%, p < 0.001). The majority of pupils in Bagamoyo (58.6%) and Ilala (61.1%) knew whether or not they had a prior diagnosis of asthma from their parents, and about a third of them (29.3% in Bagamoyo and 30.6% in Ilala) knew this information from healthcare workers. In addition to wheezing, other symptoms reported by pupils in both districts included shortness of breath, cough, and chest tightness. In Bagamoyo, shortness of breath, cough and chest tightness were reported in 19.4%, 20.8% and 12% of the pupils, respectively. Similarly, pupils in Ilala reported shortness of breath (24%), cough (15.8%) and chest tightness (24.4%). Peak expiratory flow rate (PEFR) The mean resting PEFR for male pupils was 478.05 ± 77.99 l/min in Ilala and 484.04 ± 79.18 l/min in Bagamoyo (p < 0.33). Mean resting rates for female pupils were 400.00 ± 57.00 l/min and 393.92 ± 62.02 l/min in Ilala and Bagamoyo, respectively (p < 0.28). In both study areas, there was a significant positive correlation between height and (P = 0.01). For every one meter increase of height there was an increase in PEFR of 0.537 l/s and 0.446 l/s for Ilala and Bagamoyo, respectively. The correlation was R = 0.7 and R = 0.5 for Ilala and Bagamoyo, respectively. Prevalence of exercise-induced asthma Using reductions in PEFR of both 20% and 15%, exerciseinduced asthma was more prevalent among urban than rural pupils. With 15% PEFR reduction, asthma was diagnosed in 4.3% and 7.2% of pupils Ilala and Bagamoyo, respectively (P = 0.044). Similarly, using a 20% drop in PEFR to define exercise-induced asthma, the prevalence of asthma was significantly higher (P = 0.002) in Ilala (6.3%) than Bagamoyo (2.4%). Table 3 lists the common triggers for asthma mentioned by the pupils. Over half of healthy pupils, 69.8% and 53.8% (p < 0.001) from Ilala and Bagamoyo districts, respectively, were aware of asthma as a disease. Dust and cat hair/fur were the commonest asthma triggers reported. About one fifth (21.3%) of pupils in Ilala and 16.3% of pupils in Bagamoyo reported avoidance of the triggers as the means of preventing asthma attacks. Several modes of treatment were reported, including hospital medicines (58% and 70%); traditional herbs (33.3% and 17.6%), and honey (4% and 7%) for Bagamoyo and Ilala, respectively. Other treatments mentioned were raw eggs, induced vomiting, better ventilation, and heavy clothing. Knowledge of asthma triggers Perceptions about asthma Table 4 shows the perceptions of asthma among the study's participants. Non-asthmatic pupils feared sleeping, playing, studying, and eating with their asthmatic peers, a finding which suggests that the non-asthmatic pupils believed that asthma is infectious. Discussion Asthma is globally one of the most common childhood chronic disorders associated with significant hospitalization and school absenteeism. Therefore, it is important for countries to establish reliable data on the prevalence of childhood asthma, and to institute effective interventions to reduce the economic and social costs associated with childhood asthma. This study compared the prevalence of childhood asthma among secondary school pupils in both rural (Bagamoyo) and urban (Ilala) districts along the Indian Ocean coastline of Tanzania. The study has shown that asthma was more prevalent among pupils living in urban areas than among those living in rural areas. Although the magnitude of differences varied, this rural-urban difference in prevalence has also been reported in other studies. The 6.6% prevalence for self-reported asthma in the rural pupils in this study is comparable to that reported from other parts of Africa, India, and tropical countries. Similarly, the high prevalence of 17.1% for self-reported asthma in the urban pupils from Ilala is comparable with that reported from both the western world and other African cities. In the ISAAC study, similar prevalence rates were reported among 13 to 14 year-old pupils in Cape Town (20.3%), Polokwane (18.0%), Reunion Island (21.5%), Brazzaville (19.9%), Nairobi (18.0%), Urban Ivory Coast (19.3%) and Conakry (18.6%). However, the reported prevalence rates for both urban and rural self-reported asthma in our study are higher than the prevalence of 1.9-5.2% that was previously estimated in Tanzania in 2004. This discordancy is probably due to time and methodological differences between the two studies. Nonetheless, the prevalence of wheeze in the past 12 months for the rural pupils in the current study is comparable to that reported among 9-10 year old children in Northern Tanzania. Exercise tests have been widely used in the diagnosis of asthma in children. Although a negative test does not automatically rule out asthma, a drop in the peak flow rate of 20% of the resting rate is considered positive. Falls in peak expiratory flow rates of 10%, 15% or even a 25% have also been used to define exerciseinduced asthma in some studies. The use of different cut-off values has not only contributed to the variation in the reported prevalence rates of exerciseinduced asthma, but has also rendered comparison of findings from these studies problematic. Using a 20% fall in PEFR, the prevalence of asthma in rural Bagamoyo and urban Ilala is 2.3% and 6.4%, respectively. On the other hand, using a 15% fall in PEFR as the criteria for diagnosis of childhood asthma, the prevalence in our study increased to 4.3% and 7.2% for rural and urban areas, respectively. These rates are higher than the prevalence rates reported in a South African study that used a 15% drop in PEFR to define exercise-induced asthma and found prevalence rates of approximately 3% in urban children and 0.1% in rural children. Similar to other studies, we found a rural-urban difference in the prevalence rates of exercise-induced asthma. In this study, the majority of pupils had received information about their asthma status from parents and health facilities. A surprising finding of our study was that schools were not significant sources of the pupils' information about causes and pathophysiology of asthma. The findings suggest that there are gaps in the secondary school curricula regarding asthma education, an issue that needs to be revisited. Our study also reports varying perceptions about asthma among the studied pupils, suggesting pupil belief that asthma is an infectious disease. These perceptions may be related to our additional finding that non-asthmatic pupils fear playing, eating with, or sleeping in the same room with asthmatic pupils. These observed perceptions suggest inadequate or deficient knowledge about the causes and pathophysiology of asthma on the part of the study's pupils. The non-asthmatic pupil's fear of their peers with asthma was found to be more pronounced among rural rather than urban pupils, a finding that may be explained by differences in socio-cultural values and access to information about asthma. Parents have been reported to play an important role in shaping the health care behaviour and beliefs of pupils. However, most parents are likely to share their own cultural norms, prejudices, fears, and beliefs. Teachers on the other hand, because of their intense and prolonged contact with pupils during the school year, are in a better position to be an important source of information about asthma. Nonetheless, teachers may not be able to provide such valuable health information, because they teach according to standard curricula, which may not include information about asthma or because of their own ignorance and/or personal beliefs about the disease. In this regard, provision of correct information to parents and teachers about childhood asthma may alleviate the fears many pupils may have about this common childhood condition. Conclusion The prevalence of self-reported asthma, wheeze, and exercise-induced asthma was lower in secondary school pupils in a rural area of costal Tanzania compared with similarly matched pupils in a costal urban area. In both studied populations, pupils had perceptions about asthma that suggested they believed it is an infectious disease, a belief that was associated with fear of contact with asthmatic pupils in rural, as opposed to urban pupils. As most of the pupils' information on asthma came from their parents, the same perceptions may also be held by their communities at large. It is recommended that further studies on the knowledge and perceptions about asthma should be carried out on a larger scale, for the purpose of developing educational materials for schools and the general population. It is anticipated that provision of accurate information about asthma to pupils will empower communities to develop preventive strategies and effective management of asthma. Although pupils in Ilala and Bagamoyo districts represent urban and rural settings, respectively, they may not represent pure urban and rural communities, because of frequent migration of pupils between rural and urban areas for schooling. In addition, these two districts are located along the coast of Tanzania, and the findings of this study may not be generalizable to mainland Tanzania. A further limitation of this study may be pupil unreliability regarding the recall of wheeze in the prior 12 months. Although a Swahili description of "wheeze" was provided before the administration of questionnaires, misinterpretation of this term is a possibility with some of the study's pupils. The Swahili language lacks a word precisely equivalent to wheeze. |
package com.neotys.dynatrace.monitoring;
import com.neotys.action.argument.ArgumentValidator;
import com.neotys.action.argument.Option;
import com.neotys.extensions.action.ActionParameter;
import static com.neotys.action.argument.DefaultArgumentValidator.ALWAYS_VALID;
import static com.neotys.action.argument.DefaultArgumentValidator.NON_EMPTY;
import static com.neotys.action.argument.Option.AppearsByDefault.False;
import static com.neotys.action.argument.Option.AppearsByDefault.True;
import static com.neotys.action.argument.Option.OptionalRequired.Optional;
import static com.neotys.action.argument.Option.OptionalRequired.Required;
import static com.neotys.extensions.action.ActionParameter.Type.TEXT;
/**
*
*/
enum DynatraceMonitoringOption implements Option {
DynatraceId("dynatraceId", Required, True, TEXT,
"Dynatrace ID",
"Dynatrace ID (section of your Dynatrace saas url).",
NON_EMPTY),
DynatraceApiKey("dynatraceApiKey", Required, True, TEXT,
"Dynatrace API key.",
"Dynatrace API key",
NON_EMPTY),
DynatraceTags("tags", Optional, True, TEXT,
"tag1,tag2",
"Dynatrace tags. Links the NeoLoad computed data to Dynatrace tags (format: tag1,tag2).",
ALWAYS_VALID),
DynatraceManagedHostname("dynatraceManagedHostname", Optional, False, TEXT,
"",
"Hostname of your managed Dynatrace environment.",
ALWAYS_VALID),
NeoLoadDataExchangeApiUrl("dataExchangeApiUrl", Optional, False, TEXT,
"",
"Where the DataExchange server is located. Optional, by default it is: http://${NL-ControllerIp}:7400/DataExchange/v1/Service.svc/",
NON_EMPTY),
NeoLoadDataExchangeApiKey("dataExchangeApiKey", Optional, False, TEXT,
"",
"Identification key specified in NeoLoad.",
ALWAYS_VALID),
NeoLoadProxy("proxyName", Optional, False, TEXT,
"",
"The NeoLoad proxy name to access Dynatrace.",
ALWAYS_VALID),
TraceMode("traceMode", Optional, False, TEXT,
"",
"",
ALWAYS_VALID);
private final String name;
private final Option.OptionalRequired optionalRequired;
private final Option.AppearsByDefault appearsByDefault;
private final ActionParameter.Type type;
private final String defaultValue;
private final String description;
private final ArgumentValidator argumentValidator;
DynatraceMonitoringOption(final String name, final Option.OptionalRequired optionalRequired,
final Option.AppearsByDefault appearsByDefault,
final ActionParameter.Type type, final String defaultValue, final String description,
final ArgumentValidator argumentValidator) {
this.name = name;
this.optionalRequired = optionalRequired;
this.appearsByDefault = appearsByDefault;
this.type = type;
this.defaultValue = defaultValue;
this.description = description;
this.argumentValidator = argumentValidator;
}
@Override
public String getName() {
return name;
}
@Override
public Option.OptionalRequired getOptionalRequired() {
return optionalRequired;
}
@Override
public Option.AppearsByDefault getAppearsByDefault() {
return appearsByDefault;
}
@Override
public ActionParameter.Type getType() {
return type;
}
@Override
public String getDefaultValue() {
return defaultValue;
}
@Override
public String getDescription() {
return description;
}
@Override
public ArgumentValidator getArgumentValidator() {
return argumentValidator;
}
}
|
Development and validation of an instrument to evaluate medical students' lifestyle. Introduction It is required to have validated instruments in health science students that identify unhealthy habits and assess the impact of educational interventions and programs aimed at promoting a healthy lifestyle. Objective To evaluate the validity and reliability of an instrument to measure medical students' lifestyles. Methods A lifestyle questionnaire was developed using the Delphi technique by a group of experts. The final questionnaire was applied to 332 students of the School of Medicine of the Ricardo Palma University in 2017. A preliminary examination was carried out to assess preconditions for construct validityincluding the correlation matrix, the Kaiser Meyer Olkin statistic, and the Bartlett sphericity test. Factor analysis was used for construct validity, and the possible resulting factors were extracted through the principal component analysis. Cronbach's alpha coefficient was calculated to assess the instrument reliability. Results In this study, 41.6% of participants were men with a mean age of 20 years (standard deviation = 3). The preconditions for the factor analysis were a Kaiser Meyer Olkin coefficient = 0.773 and a significant Bartlett sphericity test. For the 47 items of the final questionnaire, the factor analysis showed an explained variance of 56.7% with eigenvalues greater than one. Cronbach's alpha was 0.78. The final questionnaire could assume values between -23 to 151 points. Based on a cut point of 71 points, the prevalence of students with an unhealthy lifestyle was 73.6%. Conclusion The developed instrument has acceptable validity and reliability to measure lifestyle in medical students. For external validation, studies in other university populations are suggested. |
Examining Granger Causality in the Behavioral Reactions of Institutional Investors Evidence from India The study examines the behavioral reactions of foreign and domestic institutional investors in the Indian stock market. It poses some critical questions on whether these two types of institutional investors have common investing behavior, and whether foreign institutional investors (FIIs) affect domestic institutional investors (DIIs) strategies. Vector error correction model (VECM) is used to examine the trading and investing behavior of these institutional investors. Granger causality test is used to check if foreign institutional investment strategy influences domestic institutional strategy or vice versa. The results indicate that neither foreign institutional investors sell (FIISELL) activities affect domestic institutional investors sell (DIISELL) activities nor DIISELL affects FIISELL. This may have a crucial policy implication that both institutional investors have independent trading strategies, especially when it comes to selling stocks. But both institutional investors sale transactions do affect their own buy transactions implying that any of the institutions selling activities should be supported by their buying activities. |
<filename>src/demo.py
from arg_cat import ArgCat
def print_hi():
argcat = ArgCat()
argcat.add_key("env")
argcat.add_key("release", is_a_bool=True)
argcat.add_key("some_path", is_a_path=True)
argcat.from_arg_and_environ(environ_override_all=True)
argcat.from_arg()
argcat.from_environ()
argcat.remove("env")
argcat.put("template", "true", is_a_path=False, is_a_bool=True)
print(f'env: {argcat.get_string("env")}')
print(f'release: {argcat.get_bool("release")}')
print(f'some_path: {argcat.get_string("some_path")}')
print(f'template: {argcat.get_bool("template")}')
argcat.sync_to_file()
if __name__ == '__main__':
print_hi()
|
<reponame>mb64/chrome-ec
/* Copyright 2016 The Chromium OS Authors. All rights reserved.
* Use of this source code is governed by a BSD-style license that can be
* found in the LICENSE file.
*/
#ifndef __CROS_EC_INIT_CHIP_H
#define __CROS_EC_INIT_CHIP_H
enum permission_level {
PERMISSION_LOW = 0x00,
PERMISSION_MEDIUM = 0x33, /* APPS run at medium */
PERMISSION_HIGH = 0x3C,
PERMISSION_HIGHEST = 0x55
};
int runlevel_is_high(void);
void init_runlevel(const enum permission_level desired_level);
void init_jittery_clock(int highsec);
void init_sof_clock(void);
#endif /* __CROS_EC_INIT_CHIP_H */
|
Schizophrenia is a debilitating psychiatric disorder characterized by a combination of negative (blunted affect, withdrawal, anhedonia) and positive (paranoia, hallucinations, delusions) symptoms as well as marked cognitive deficits. While the etiology of schizophrenia is currently unknown, the disease appears to be produced by a complex interaction of biological, environmental, and genetic factors. Atypical antipsychotics form the front line in the treatment of schizophrenia and more recently in bipolar disorder. However, up to 30% of schizophrenic patients are not adequately treated by currently available medication. While there are a number of atypical antipsychotic agents currently available, these agents suffer from a high rate of discontinuation due to either patient and/or physician dissatisfaction with efficacy or safety/tolerability. Atypical antipsychotics possess a pharmacology which is thought to underlie their ability to achieve efficacy at positive symptoms via antagonism at dopamine D2 and serotonin 5-HT2A receptors. These activities produce some efficacy on negative symptoms but also contribute to adverse side effects. These adverse side effects include weight gain/metabolic effects (thought to be associated with antagonism at 5-HT2C and antagonism at histamine H1 receptors), extra-pyramidal effects and prolactin secretion (thought to be associated with antagonism at dopamine D2 receptors), sedation (thought to be associated with antagonism at α1 adrenergic and antagonism at histamine H1 receptors) and cognitive impairment (thought to be associated with antagonism at muscarinic M1 receptors). Accordingly, there is a need in the art for atypical antipsychotic agents with better efficacy on positive symptoms, negative symptoms and/or decreased adverse side effects. |
The present invention relates to analyzing chemical reactions and, more particularly, but not exclusively to systems and methods for automatically identifying outliers among chemical reaction assays.
An outlier may be indicative of a measurement error, a contaminated sample, a human error, an experimental error, etc, as known in the art.
Traditionally, the classification of chemical assays is based on manual examination by an expert in the field.
The expert manually examines hundreds or thousands of samples, say thousands of graphs derived from results of Quantitative Fluorescent Polymerase Chain Reaction (QF-PCR) based assays, or other chemical assays.
The expert detects certain features in the samples, and classifies each sample into one of two or more groups.
Typically, the results of the chemical assays are obtained through real time photometric measurements of reactions such as real-time Polymerase Chain Reaction (PCR) and Quantitative Fluorescent Polymerase Chain Reaction (QF-PCR), thus producing a time series of values.
The values produced through the measurements, may be represented in a two dimensional graph depicting spectral changes over time, say of a real-time PCR based assay.
The values may also be represented in a three dimensional graph depicting spectral changes vs. molecule length vs. time, say of a Capillary PCR based assay, etc., as known in the art.
For example, the spectral changes may include Fluorescence Intensity (FI) values measured over a PCR reaction apparatus, as known in the art. The measured FI values are indicative of presence and quantity of specific molecules, as detected in the PCR reaction.
The values measured may be used, to classify the chemical reaction assay into a certain type, to determine if the assay is positive or negative (say with respect to occurrence of a certain genetic mutation), etc.
For example, in QF-PCR, a graph representing the values measured over time may have linear properties, which indicate that no amplification takes place in a reaction apparatus.
Alternatively, the QF-PCR graph may include a sigmoid curve interval, which indicates the occurrence of a DNA amplification reaction in the reaction apparatus.
Parameters extracted from the graph are used to determine the properties of the amplification.
The right combination of parameters, say slopes of the graph in selected points on the graph, may indicate the existence of a specific subject (say the existence of a specific bacterial DNA sequence).
The traditional methods rely on a model built manually, by the expert.
In order to build the model, the expert has to manually examine hundreds or thousands of samples of a training set.
The expert may position points in a coordinate system, say on a paper or on a computer screen. Each of the points represents one the samples. The position of each of the points depends on the parameters extracted from the graph, and represents the results of a respective assay (i.e. a single one of the samples).
Then, the expert classifies each of the samples (as represented by points) into one of two or more groups.
Finally, the expert manually draws a line defining a separation between the two or more groups. For example, the expert may draw a line defining a separation between positive and negative samples.
A new sample may thus be classified into one of the groups based on position of a point which represents the future sample, on one or other side of the line which defines the separation between the groups.
Occasionally, while building the training set, the expert may find some of the samples problematic and difficult to classify into one of the groups, thus finding the problematic samples as outliers.
Some currently used methods are based on automatic classification of samples. For example, some of the currently used methods use SVM (Support Vector Machine), to identify patterns in biological systems.
Support Vector Machines (SVMs) are a set of related supervised learning methods that analyze data and recognize patterns. Supervised learning methods are widely used for classification and regression analysis.
Standard SVM may take a set of input data, and predict for each given input, which of two possible categories the input is a member of.
Given a set of training samples, each marked as belonging to one of the two categories, an SVM training algorithm builds a model usable for assigning a new sample into one category or the other.
Intuitively, the SVM built model is a representation of the samples as points in space, mapped so that the examples of the separate categories are divided by a clear gap.
Consequently, new samples may be mapped into that same space and predicted to belong to one of the categories, based on which side of the gap the new samples fall on. |
Replication refers to the concept of distributing replicas of data (e.g., files) to distributed storage devices, so as to make data more available compared to scenarios in which the data is stored on a single storage device. The replicas of the data are continuously updated in order to ensure that up-to-date data is readily available and accessible. That is, data replication systems maintain a consistency invariant that is maintained (e.g., stored) regardless of any failures that can occur in distributed computing systems. Such failures may include message loss, hardware failures, network partitioning, message corruption, message duplication, message alteration, and the like.
Fault-tolerance refers to the concept of enabling systems to continuously function despite failure by or of one or more of the system's components. For instance, in the event of a temporary failure by or of a system component, such as the system's storage device (or components connecting the system to the storage device), the system can continue to function using the replicas stored in the distributed storage devices. In the event of a permanent failure by or of the system's components, including the system's storage device and/or corruption of the data stored therein, the systems' replacement storage device can be replenished using the replicas stored in the distributed storage devices.
In this way, fault-tolerant file replication systems are equipped to partially function even at reduced efficiency, while avoiding a total system failure. Making the data available, via replicas, in order to prevent complete system breakdowns is beneficial in all computing scenarios, but is of particular importance in critical systems such as: fire alarms, emergency dispatching, electricity generation, robotic surgery, nuclear reaction, defibrillators, radiation therapy, infusion pumps, construction equipment, amusement rides, scuba equipment, railway signaling, airbags, braking, power steering, advanced driver assistance, battery management, electric park, air traffic control, flight planning, radio navigation, space flight, and rocket launch.
Traditionally, data replication mechanism rely on replication logs. Replication logs store a list of all changes to a file in a sequential order, assign each change with a consecutive number, and append those changes to a persistent log on each replica. To update a replica, the changes in the persistent log are applied to the replica in the order specified in the persistent log, thereby ensuring that all replicas are executing the same changes in the same order established in the replication log.
One drawback, however, is that traditional replication mechanisms such as those employing replication logs are inefficient because they require changes to replicas to be sequentially written. In other words, a series of updates to parts of a file (e.g., disjunct parts of a file) are processed one after the other. Thus, such replication mechanisms do not exploit the ability of storage devices to concurrently execute a series of operations.
Moreover, traditional replication mechanisms which require writing each change and/or update twice: once to a persistent log corresponding to the replica, and a second time to the replica file itself. Thus, each change and/or update to a file results in two independent input/output (I/O) operations to/from the storage device on which the replica is stored. As a result, storage devices are faced with additional storage and/or processing burdens. Other traditional replication systems merely update the persistent log of the replica and, at a later time, update the replica file itself. This results in systems having to consult the persistent log each time the replica is attempted to be accessed, to ensure that the replica contains the most up-to-date data.
Given the foregoing, it would be beneficial to provide fault-tolerant file replication that allows concurrent processing, consistency to linearizability, and direct modification of replicas. It would also be beneficial to provide fault-tolerant file replication that efficiently updates replicas while minimizing the processing and storage burden on distributed storage devices. |
#include "stdafx.h"
#include "Actor.h"
#include "actor.h"
#include <stdlib.h>
#include "async.h"
#include <assert.h>
#define ASSERT(x)
Result Actor_Init(Actor* actor)
{
actor->state = ACTOR_STATE_NONE;
actor->tasks_size = 0;
actor->taks_max_size = 100;
actor->current_tasks = 0;
int r = mtx_init(&actor->s_queue_mutex, mtx_plain);
return r == thrd_success ? RESULT_OK : RESULT_FAIL;
}
void Actor_Destroy(Actor* actor)
{
mtx_destroy(&actor->s_queue_mutex);
}
static int Actor_GetMessages(Actor* actor,
ActorTask** current_tasks)
{
*current_tasks = NULL; //out
int tasks = 0;
mtx_lock(&actor->s_queue_mutex);
tasks = actor->tasks_size;
if (tasks != 0)
{
actor->state = ACTOR_STATE_RUNNING;
*current_tasks = actor->current_tasks;
actor->current_tasks = NULL;
actor->tasks_size = 0;
}
else
{
actor->state = ACTOR_STATE_NONE;
}
mtx_unlock(&actor->s_queue_mutex);
return tasks;
}
static void ActorProcessMessages(Result result, void* p)
{
Actor* actor = (Actor*)(p);
for (;;)
{
ActorTask* current_tasks;
int tasks = Actor_GetMessages(actor, ¤t_tasks);
if (tasks == 0)
{
break;
}
//for (int i = tasks - 1; i >= 0; i--)
for (int i = 0; i < tasks; i++)
{
ActorTask* pTask = ¤t_tasks[i];
pTask->Callback(RESULT_OK,
actor,
pTask->Data);
}
}
}
void Actor_Post(Actor* actor,
void(*callback)(Result, struct Actor_t*, void*),
void* data)
{
int result = 0;
mtx_lock(&actor->s_queue_mutex);
if (actor->current_tasks == 0)
{
actor->current_tasks =
(ActorTask*)malloc(sizeof(ActorTask) * actor->taks_max_size);
if (actor->current_tasks == 0)
{
callback(RESULT_OUTOFMEM, actor, data);
result = 1;
}
}
if (result == 0)
{
actor->current_tasks[actor->tasks_size].Callback = callback;
actor->current_tasks[actor->tasks_size].Data = data;
actor->tasks_size++;
switch (actor->state)
{
case ACTOR_STATE_NONE:
actor->state = ACTOR_STATE_ONQUEUE;
AsynPool_Run(&ActorProcessMessages, actor);
break;
case ACTOR_STATE_ONQUEUE:
case ACTOR_STATE_RUNNING:
break;
default:
ASSERT(false);
}
}
mtx_unlock(&actor->s_queue_mutex);
}
|
Respiratory responses of domestic fowl to hyperthermia following selective air sac occlusions Ventilation together with blood and respiratory gas tensions were measured in adult domestic fowl under normothermic and hyperthermic conditions, following bilateral occlusion of the cranial and caudal thoracic air sacs (series I) or the cranial and caudal thoracic plus the abdominal air sacs (series II). Series I birds showed no significant differences from controls. Both control and experimental animals displayed a typical thermal polypnoea combined with mild hypocapnaemia. A larger drop in PCO2 was demonstrated in the clavicular sac than in the blood, possibly indicating partial failure of inspiratory valving at the ventrobronchi. However, there was no evidence of any effect of thoracic air sac occlusion on inspiratory airflow valving in the palaeopulmo. Series II birds were strongly hypercapnaemic/hypoxaemic in normothermic conditions, with a normal minute volume, but a faster, shallower breathing pattern. During hyperthermia they increased minute ventilation 3fold, as in control animals, and blood gas tensions were almost restored to normal. Again, there was no evidence that experimental reduction in air sac capacity, in this case up to 70% of the total, had any effect on inspiratory airflow valving in the palaeopulmo, although inevitably in this case airflow in the neopulmo was abolished. |
"""
A simple example that doesn't do anything computationally expensive, but shows how to pass consume
data and pass values between functions. Additionally, shows how to catch and handle exceptions
"""
import logging
from multiflow import MultithreadedFlow
import sys
import time
def get_logger(name):
"""
Gets logger instance
"""
logging.basicConfig(
level=logging.INFO,
format='%(asctime)s - %(name)s - %(levelname)s - %(message)s',
stream=sys.stdout
)
return logging.getLogger(name)
def add_n(v, n=1):
"""
Adds two numbers
"""
return v + n
def fail_or_sleep(v):
"""
Returns exception if the value is odd. Otherwise, sleeps the value mod 5
"""
if v % 2 == 0:
x = v % 5
time.sleep(x)
return x
else:
raise Exception('Value is odd: {}'.format(v))
def handle_exception(e, v):
"""
Handles exception from fail_or_sleep function
"""
if v == 13:
# after catching exception and if v is equal to 13, will return -1 and mark the job as successful
return -1
else:
# otherwise raises error
raise e
if __name__ == '__main__':
logger = get_logger('test')
with MultithreadedFlow(
max_workers=32,
retry_count=1,
logger=logger,
log_all=True,
quiet_traceback=True
) as flow:
# consumes the iterable values from 0 to 19
flow.consume(range, 20)
# calls add_n on all values yielded from range
flow.add_function(add_n, n=5)
# calls fail_or_sleep on all values yielded from add_n. If there is an exception, will
# call handle_exception to handle the exception
flow.add_function(fail_or_sleep).error_handler(handle_exception)
# for all results from the thread pool
for output in flow:
# if the job was successful
if output:
# prints v (the first argument passed into the last function - fail_or_sleep)
# and the output of the last function
print(output[0], output)
else:
e = output.get_exception()
# this value is 1 which represents the second function called - fail_or_sleep in this case
fn_id = output.get_fn_id()
# gets total number of tries (this will be 1 or 2 in the case of the exception raised by fail_or_sleep)
num_of_tries = output.get_num_of_attempts()
# gets total number of success (11) and failed counts (9)
success_count = flow.get_successful_job_count()
failed_count = flow.get_failed_job_count()
|
I remember the last time they changed the notes. Within 24 hours there was not a single old note to be seen anywhere, it was pretty impressive.
Sure. We are going to believe that a big Japanese industry is being honest, transparent, and tells the truth..
Look how when they talk in the news about "Japanese workers" they seem to include everyone, when they are just referring to the top half of the workforce, your regular salaryman with a permanent contract. The bottom half will work -a lot- these holidays.
However, Japanese family law does not contemplate / incorporate foreigners into the system.
This alone is one of the most discriminatory things Japanese do.
All these big companies want to maximise profits every year, but want workers to accept minimum wages and long hours of hard work. Rise the wages, give better working conditions to workers (insurance, health care, permanent contracts.. to name a few) and they will come. And the franchisees usually struggle to reach profit because of the contract conditions.
NHK does provide a very valuable service during major disasters like earthquakes and tsunamis.
6,2 tons of gold.. amazing.
The press should be more careful when reporting this kind of news. "hundreds" of radicals do not represent the feeling of all Russians, at all. But they become the front page picture on Japan Today, but a "Russians protest" title. This brings more polemic and, would say hate, to the table than a more objective reporting would bring.
gyaranomi or drinking parties that male participants pay women to attend.
This is much worse than that Spa! article, but nobody seems to be complaining about it.
He could be spending his money to help the poor and/or to contribute to the society, this give away is just another look-at-me excersise of selfishness.
It's not that many people! And only some 100,000 Japanese on the list? I'd have expected ten times that, for how heavily promoted the Olympics are.
The government is going to spend $4 billion in combat planes, yet there seems to be no yen at all to help with the childcare problem.
I also heard on the TV that they want to give 2% "tax discounts" if you pay with credit card in the supermarket, which makes no sense. I just looks like someone in the government owes something to big banks..
This is usual Japan, money for the big companies.
But this is an insult to low-income families! Don't do anything to help with their situation, give them some vouchers to shop because they are so poor they can't buy anything new.
Daylight savings are great, and would be great for Japan. I makes no sense to have a silly 4am sunrise, and a really early 7pm sunset during the summer.
Transforming temples in "social hubs", when social hubs are also going to disappear.
Yubaru is right on the second comment. Living in an island of nature, were the weather is good all year long, and the guy needs a mall to spend time with the family? Come on, the mall may be convenient and fun for a day or two, but you should not need it.
But Yubaru, tourism is the key for the future of Okinawa, as long as you make it right and go for sustainable tourism in the hands of its habitants. Please don't pledge to the usual big companies will.
The Japanese government hopes the Olympics will show the region is recovering and that products made there are safe.
How is that related to the Olympics?
Again, this film should be about Olympics in Japan. Not about Japanism.
Kon Ichikawa's one is a masterpiece, a beautiful documentary. This new one will be just as flat and lifeless as current Japanese films are.
Only 30,000? I'd have expected 50 times that number, considering the Olympics mindset campaign we have had on the TV for the last couple of years.
And exactly why? I don't see Japanese eating whale fish anyway, apart from the occasional izakaya dish. Who behind pushing this whaling agenda so much?
Kids need to play with crayons, toys and wood pieces! There's much more to these for learning than to use just a finger on a screen all day long.
Anyone with kids knows that they will learn to use any digital device in less than one minute anyway, no need to hook them to these since kindergarden!
I don't understand the reason why he's considered for a Nobel every year. Yes, he writes popular books, and he is a clever, interesting man. But his work is faaaar from being Nobel worthy. |
<filename>cosmos/launchpad/client/alttendermint/mempool_test.go<gh_stars>0
package alttendermint
import (
"io/ioutil"
"net/http"
"net/http/httptest"
"testing"
"github.com/stretchr/testify/require"
)
func TestClient_UnconfirmedTxs(t *testing.T) {
fileData, err := ioutil.ReadFile("testdata/unconfirmed_txs.json")
require.NoError(t, err)
s := httptest.NewServer(http.HandlerFunc(func(writer http.ResponseWriter, request *http.Request) {
_, err2 := writer.Write(fileData)
require.NoError(t, err2)
}))
defer s.Close()
client := NewClient(s.URL)
resp, err := client.UnconfirmedTxs()
require.NoError(t, err)
require.Equal(t, []string{
"<KEY>
}, resp.Txs)
}
|
<reponame>leekayden/jcodec
package org.jcodec.player.filters;
import java.io.IOException;
import java.nio.ByteBuffer;
import java.util.ArrayList;
import java.util.Comparator;
import java.util.Iterator;
import java.util.List;
import java.util.TreeSet;
import java.util.concurrent.Callable;
import java.util.concurrent.ExecutorService;
import java.util.concurrent.Executors;
import java.util.concurrent.Future;
import java.util.concurrent.ThreadFactory;
import java.util.concurrent.locks.ReentrantLock;
import org.jcodec.common.JCodecUtil;
import org.jcodec.common.VideoDecoder;
import org.jcodec.common.model.Frame;
import org.jcodec.common.model.Packet;
import org.jcodec.common.model.Picture;
import org.jcodec.common.model.Rational;
import org.jcodec.common.model.RationalLarge;
import org.jcodec.common.model.Size;
import org.jcodec.common.model.TapeTimecode;
import org.jcodec.common.tools.Debug;
/**
* This class is part of JCodec ( www.jcodec.org ) This software is distributed
* under FreeBSD License
*
* @author The JCodec project
*
*/
public class JCodecVideoSource implements VideoSource {
//ThreadLocal instances are typically private static fields in classes that wish to associate state with a thread
private final static ThreadLocal<VideoDecoder> decoders = new ThreadLocal<VideoDecoder>();
private ExecutorService tp;
private List<ByteBuffer> drain = new ArrayList<ByteBuffer>();
private MediaInfo.VideoInfo mi;
private PacketSource src;
private ReentrantLock seekLock = new ReentrantLock();
private TreeSet<Packet> reordering;
public JCodecVideoSource(PacketSource src) throws IOException {
Debug.println("Creating video source");
this.src = src;
mi = (MediaInfo.VideoInfo) src.getMediaInfo();
reordering = createReordering();
tp = Executors.newFixedThreadPool(Runtime.getRuntime().availableProcessors(), new ThreadFactory() {
public Thread newThread(Runnable r) {
Thread thread = new Thread(r);
thread.setPriority(Thread.MIN_PRIORITY);
return thread;
}
});
}
private TreeSet<Packet> createReordering() {
return new TreeSet<Packet>(new Comparator<Packet>() {
public int compare(Packet o1, Packet o2) {
return o1.getPts() > o2.getPts() ? 1 : (o1.getPts() == o2.getPts() ? 0 : -1);
}
});
}
static int cnt = 0;
@Override
public Frame decode(byte[][] buf) throws IOException {
seekLock.lock();
Packet nextPacket;
try {
nextPacket = selectNextPacket();
} finally {
seekLock.unlock();
}
if (nextPacket == null)
return null;
final Future<Picture> job = tp.submit(new FrameCallable(nextPacket, buf));
Frame frm = new FutureFrame(job, new RationalLarge(nextPacket.getPts(), nextPacket.getTimescale()),
new RationalLarge(nextPacket.getDuration(), nextPacket.getTimescale()), mi.getPAR(),
(int) nextPacket.getFrameNo(), nextPacket.getTapeTimecode(), null);
return frm;
}
public Packet selectNextPacket() throws IOException {
fillReordering();
if (reordering.size() == 0)
return null;
Packet first = reordering.first();
if (first != null)
reordering.remove(first);
return first;
}
private void fillReordering() throws IOException {
while (reordering.size() < 5) {
Packet pkt = pickNextPacket();
if (pkt == null)
break;
reordering.add(pkt);
}
}
public Packet pickNextPacket() throws IOException {
ByteBuffer buffer;
synchronized (drain) {
if (drain.size() == 0) {
drain.add(allocateBuffer());
}
buffer = drain.remove(0);
buffer.rewind();
}
return src.getPacket(buffer);
}
public class FutureFrame extends Frame {
private Future<Picture> job;
public FutureFrame(Future<Picture> job, RationalLarge pts, RationalLarge duration, Rational pixelAspect,
int frameNo, TapeTimecode tapeTimecode, List<String> messages) {
super(null, pts, duration, pixelAspect, frameNo, tapeTimecode, messages);
this.job = job;
}
@Override
public boolean isAvailable() {
return job.isDone();
}
@Override
public Picture getPic() {
try {
return job.get();
} catch (Exception e) {
throw new RuntimeException(e);
}
}
}
class FrameCallable implements Callable<Picture> {
private Packet pkt;
private byte[][] out;
public FrameCallable(Packet pkt, byte[][] out) {
this.pkt = pkt;
this.out = out;
}
public Picture call() {
VideoDecoder decoder = decoders.get();
if (decoder == null) {
decoder = JCodecUtil.getVideoDecoder(mi.getFourcc());
decoders.set(decoder);
}
Picture pic = decoder.decodeFrame(pkt.getData(), out);
synchronized (drain) {
drain.add(pkt.getData());
}
return pic;
}
}
@Override
public boolean drySeek(RationalLarge sec) throws IOException {
return src.drySeek(sec);
}
@Override
public void seek(RationalLarge sec) throws IOException {
seekLock.lock();
try {
clearReordering();
src.seek(sec);
fillReordering();
Iterator<Packet> it = reordering.iterator();
while (it.hasNext()) {
if (it.next().getPtsR().lessThen(sec))
it.remove();
else
break;
}
} finally {
seekLock.unlock();
}
}
private void clearReordering() {
TreeSet<Packet> old = reordering;
reordering = createReordering();
for (Packet packet : old) {
drain.add(packet.getData());
}
}
private ByteBuffer allocateBuffer() {
Size dim = mi.getDim();
return ByteBuffer.allocate(dim.getWidth() * dim.getHeight() * 2);
}
public MediaInfo.VideoInfo getMediaInfo() throws IOException {
return (MediaInfo.VideoInfo) src.getMediaInfo();
}
public void close() throws IOException {
src.close();
}
@Override
public void gotoFrame(int frame) throws IOException {
clearReordering();
src.gotoFrame(frame);
}
} |
. We report an autopsy case of a cardiomyopathy characterized by fatty replacement of the right ventricular myocardium and compare its clinical and histologic characteristics with those of the arrhythmogenic right ventricular cardiomyopathy. A 39-year old male died suddenly in a hospital room. He had an alcoholic cirrhosis with ascitis, but the clinical examination and the biology showed no abnormalities explaining the death. Histologically, in the right ventricle, large areas of cardiomyocytes were replaced by fat, but there was no fibrosis. In contrast, fibrosis is present in association with fat in arrhythmogenic right ventricular cardiomyopathy. Fatty replacement of the right ventricle is likely to be a distinct entity. Right ventricular failure has been shown to be a possible complication. Sudden death is probably rare and is likely to occur when other arrhythmogenic factors are associated. |
<reponame>wyaneva/ParTeCL
/*
* Copyright 2017 <NAME>, The University of Edinburgh
*
* Licensed under the Apache License, Version 2.0 (the "License");
* you may not use this file except in compliance with the License.
* You may obtain a copy of the License at
*
* http://www.apache.org/licenses/LICENSE-2.0
*
* Unless required by applicable law or agreed to in writing, software
* distributed under the License is distributed on an "AS IS" BASIS,
* WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
* See the License for the specific language governing permissions and
* limitations under the License.
*/
#include "CpuCodeGenerator.h"
#include "Constants.h"
#include "Utils.h"
#include <sstream>
#include <string>
/*
* Gnerate structs.h
*/
void generateDeclaration(std::ofstream &strFile,
const struct Declaration &declaration) {
std::string type = declaration.type;
std::stringstream size;
// if the size is not a numeric string, then hardcode it
if (declaration.size.find_first_not_of("0123456789") != std::string::npos)
size << structs_constants::POINTER_ARRAY_SIZE;
else
size << declaration.size;
if (declaration.isPointer) { // add the star to delcaraiont
strFile << " " << type << "* " << declaration.name << ";\n";
} else if (declaration.isArray) {
strFile << " " << type << " " << declaration.name << "[" << size.str()
<< "];\n";
} else {
strFile << " " << type << " " << declaration.name << ";\n";
}
}
void generateStructs(
const std::string &outputDirectory,
const std::list<struct Declaration> &stdinInputs,
const std::list<struct Declaration> &inputDeclarations,
const std::list<struct ResultDeclaration> &resultDeclarations,
const std::list<std::string> &includes) {
llvm::outs() << "Generating memory buffer structs... ";
std::string structsFilename =
outputDirectory + '/' + filename_constants::STRUCTS_FILENAME;
std::ofstream strFile;
strFile.open(structsFilename);
// write input
strFile << "#ifndef STRUCTS_H\n";
strFile << "#define STRUCTS_H\n\n";
for (auto &include : includes) {
strFile << "#include \"" << include << "\"\n";
}
strFile << "\n";
strFile << "typedef struct " << structs_constants::INPUT << "\n";
strFile << "{\n";
strFile << " int " << structs_constants::TEST_CASE_NUM << ";\n";
strFile << " int " << structs_constants::ARGC << ";\n";
for (auto &inputDecl : inputDeclarations) {
generateDeclaration(strFile, inputDecl);
}
for (auto &stdinArg : stdinInputs) {
generateDeclaration(strFile, stdinArg);
}
strFile << "} " << structs_constants::INPUT << ";\n\n";
// write result
strFile << "typedef struct " << structs_constants::RESULT << "\n";
strFile << "{\n";
strFile << " int test_case_num;\n";
for (auto &resultDecl : resultDeclarations) {
generateDeclaration(strFile, resultDecl.declaration);
}
strFile << "} " << structs_constants::RESULT << ";\n\n";
strFile << "#endif\n";
strFile.close();
llvm::outs() << "DONE!\n";
}
/*
* Generate cpu-gen.h and cpu-gen.c
*/
std::string generatePrintByTypeNonArray(const struct Declaration &declaration) {
std::stringstream ss;
ss << "printf(\"TC %d: \", curres." << structs_constants::TEST_CASE_NUM
<< ");\n";
if (declaration.type == "int") {
ss << "printf(\"%d \\n\", curres." << declaration.name << ");\n";
} else if (declaration.type == "char") {
ss << "printf(\"%c \\n\", curres." << declaration.name << ");\n";
} else {
// TODO: Handle other types; currently default to int
#if ENABLE_WARNINGS
llvm::outs() << "\ngenerateCompareResults: I don't know how to print "
"results of type '"
<< resultDecl.declaration.type << "'. Defaulting to 'int'.\n";
#endif
ss << "printf(\"%d \", curres." << declaration.name << ");\n";
}
return ss.str();
}
std::string generatePrintByTypeArray(const struct Declaration &declaration) {
std::stringstream ss;
if (declaration.type == "int") {
ss << " int curel = "
<< "curres." << declaration.name << "[k];\n";
ss << " printf(\"%d \", curel);\n";
} else if (declaration.type == "char") {
ss << " char curel = "
<< "curres." << declaration.name << "[k];\n";
ss << " printf(\"%c \", curel);\n";
} else {
// TODO: Handle other types; currently default to int
#if ENABLE_WARNINGS
llvm::outs() << "\ngenerateCompareResults: I don't know how to print "
"results of type '"
<< declaration.type << "'. Defaulting to 'int'.\n";
#endif
ss << " int curel = "
<< "curres." << declaration.name << "[k];\n";
ss << " printf(\"%d \", curel);\n";
}
return ss.str();
}
std::string generatePrintArray(const struct Declaration &declaration) {
std::string size = declaration.size;
// if the size is not a numeric string, then it must be a member of the result
// struct
if (declaration.size.find_first_not_of("0123456789") != std::string::npos)
size = "curres." + declaration.size;
std::stringstream ss;
ss << " printf(\"TC %d: \", curres." << structs_constants::TEST_CASE_NUM
<< ");\n";
ss << " for(int k = 0; k < " << size << "; k++)\n";
ss << " {\n";
ss << generatePrintByTypeArray(declaration);
ss << " }\n";
ss << " printf(\"\\n\");\n";
return ss.str();
}
std::string generatePrintCalls(const struct ResultDeclaration &resultDecl) {
std::string str;
if (resultDecl.declaration.isArray) {
str = generatePrintArray(resultDecl.declaration);
} else {
str = generatePrintByTypeNonArray(resultDecl.declaration);
}
return str;
}
void generateCompareResults(
std::ofstream &strFile,
const std::list<struct ResultDeclaration> &resultDecls) {
strFile << "void compare_results(struct " << structs_constants::RESULT
<< "* results, struct " << structs_constants::RESULT
<< "* exp_results, int num_test_cases)\n";
strFile << "{\n";
strFile << " for(int i = 0; i < num_test_cases; i++)\n";
strFile << " {\n";
strFile << " struct " << structs_constants::RESULT
<< " curres = results[i];\n";
for (auto &resultDecl : resultDecls) {
// TODO: Find out how to compare; for now just print
strFile << generatePrintCalls(resultDecl);
}
strFile << " }\n";
strFile << "}\n";
}
void generatePopulateInput(std::ofstream &strFile, struct Declaration input,
std::string count, std::string container, int i) {
std::string name = input.name;
std::string argsidx = std::to_string(i + 1);
// for arrays, add a loop and indexes
if (input.isArray) {
std::stringstream size;
// if the size is not a numeric string, then make it a variable name
if (input.size.find_first_not_of("0123456789") != std::string::npos)
size << "input->" << input.size;
else
size << input.size;
strFile << " for(int i = 0; i < " << size.str() << "; i++)\n";
name.append("[i]");
argsidx = "i+";
argsidx.append(std::to_string(i + 1));
} else {
strFile << " if(" << count << " >= " << i + 2 << ")\n"
<< " {\n";
}
// pointers
// TODO: add handling for pointers which are not 'char *'
if (input.isPointer) {
strFile << " int len = strlen(" << container << "[" << argsidx << "]);\n"
<< " input->" << name
<< " = (char *)malloc(sizeof(char *)*len);\n"
<< " strcpy(input->" << name << ", " << container << "["
<< argsidx << "]);\n";
// not pointers
} else if (contains(input.type, "int")) {
strFile << " input->" << name << " = "
<< "atoi(" << container << "[" << argsidx << "]);\n";
} else if (contains(input.type, "bool")) {
strFile << " input->" << name << " = "
<< "atoi(" << container << "[" << argsidx << "]);\n";
} else if (contains(input.type, "char")) {
strFile << " input->" << name << " = "
<< "*" << container << "[" << argsidx << "];\n";
} else {
#if ENABLE_WARNINGS
llvm::outs() << "POPULATE_INPUTS: Improvising for custom type "
<< input.type << ".\n";
#endif
strFile << " input->" << name << " = "
<< "atoi(" << container << "[" << argsidx << "]);\n";
}
// close bracket opened in the beginning
if (!input.isArray) {
strFile << " }\n";
}
}
void generatePopulateInputs(std::ofstream &strFile,
const std::list<struct Declaration> &inputDecls,
const std::list<struct Declaration> &stdinInputs) {
strFile << "void populate_inputs(struct " << structs_constants::INPUT
<< " *input, int argc, char** args, int stdinc, char** stdins)\n";
strFile << "{\n";
strFile << " input->" << structs_constants::TEST_CASE_NUM
<< " = atoi(args[0]);\n";
strFile << " input->" << structs_constants::ARGC << " = argc;\n";
int i = -1; // command line args start from index 1
for (auto &input : inputDecls) {
i++;
generatePopulateInput(strFile, input, "argc", "args", i);
}
i = -2; // stdin args start from index 0
for (auto &stdinArg : stdinInputs) {
i++;
generatePopulateInput(strFile, stdinArg, "stdinc", "stdins", i);
}
strFile << "}\n";
}
void generateCpuGen(const std::string &outputDirectory,
const std::list<struct Declaration> &inputs,
const std::list<struct ResultDeclaration> &results,
const std::list<struct Declaration> &stdinInputs) {
llvm::outs() << "Generating CPU code... ";
// generate header file
std::ofstream headerFile;
std::string headerFilename =
outputDirectory + "/" + filename_constants::CPU_GEN_FILENAME + ".h";
headerFile.open(headerFilename);
headerFile << "#ifndef CPU_GEN_H\n";
headerFile << "#define CPU_GEN_H\n";
headerFile << "#include \"structs.h\"\n\n";
headerFile << "void populate_inputs(struct " << structs_constants::INPUT
<< "*, int, char**, int, char**);\n\n";
headerFile << "void compare_results(struct " << structs_constants::RESULT
<< "*, struct " << structs_constants::RESULT << "*, int);\n\n";
headerFile << "#endif\n";
headerFile.close();
// generate source file
std::ofstream strFile;
std::string sourceFilename =
outputDirectory + "/" + filename_constants::CPU_GEN_FILENAME + ".c";
strFile.open(sourceFilename);
strFile << "#include <stdlib.h>\n";
strFile << "#include <string.h>\n";
strFile << "#include <stdio.h>\n";
strFile << "#include \"cpu-gen.h\"\n\n";
generatePopulateInputs(strFile, inputs, stdinInputs);
generateCompareResults(strFile, results);
strFile.close();
llvm::outs() << "DONE!\n";
}
|
Fast codeword selection for limited feedback beamforming multiple-input-multiple-output systems using breadth-first tree search Codebooks with constant modulus entries are being considered for the limited feedback beamforming multiple-input-multiple-output (MIMO) system to improve the power amplifier efficiency at the transmitter. Assume that one such codebook is known to both the transmitter and receiver. The receiver must determine a target codeword from this codebook and send its index back to the transmitter. A receiver can be implemented with low cost if fast codeword selection algorithm is executed. In this study, the authors utilise the properties possessed by three such codebooks and propose a novel tree search algorithm for fast codeword selection. Compared with two previously reported codeword selection algorithms, our algorithm is of fixed complexity and does find the target codeword. Furthermore, our algorithm for codeword selection is similar to the tree search for MIMO detection. These two similar tree search algorithms for both codeword selection and MIMO detection can be implemented by the same hardware architecture. A baseband receiver with small chip area for the dual-mode (the spatial multiplexing and beamforming transmission modes) MIMO system is possible. |
<reponame>remik2212/holochain
use hdk3::prelude::*;
#[hdk_extern]
fn random_bytes(bytes: RandomBytesInput) -> ExternResult<RandomBytesOutput> {
Ok(
RandomBytesOutput::new(Bytes::from(
hdk3::prelude::random_bytes(
bytes.into_inner()
)?
))
)
}
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.