dataesr/scientific-paragraphs-categorization huggingface dataset:
conclusion Even though a large amount of work has been done for the HHCRSPs, the majority of them belongs to the deterministic models, which can only make the final decision on the schedule satisfy the deterministic scenarios. According to the feedback from HHC companies, caregivers have to deal with some uncertainties when carrying out a given schedule to visit their patients. This work formulates a robust optimization model for an HHC Routing and Scheduling Problem with taking into account uncertain travel and service times. Specifically, the non-deterministic variables are defined based on the theory of budget uncertainty, and then the arrival time of each caregiver is rewritten as a complicated recursive function. After that, Gurobi Solver, Simulated Annealing, Tabu Search, and Variable Neighborhood Search are adapted to solve the model respectively.
Accordingly, data were collected from 236 and 237 genotypes from Arua and Mubende, respectively. This resulted into a total of 268 genotypes that had phenotypic data from at least one of the two environments. Penetrometer assessment. The waxed roots from the two field locations were stored in a -80 °C freezer to avoid deterioration prior to softness evaluation. Freezing was done to ensure long preservation (more than one month), because waxing can only preserve roots for about one month  (Lebot, 2009). In a pilot experiment that we conducted earlier with ten genotypes, root softness for frozen root samples over a duration of 30 days was strongly correlated (r 2 = 0. 76, P-value = 0. 0009) with softness from fresh roots. This provided confidence in the freezing process adopted to handle the relatively high number of samples analysed in this study.
Thus, at each time point, the 7. 9 mm diameter tip of a digital penetrometer (Model number: FHT-1122, Vetus Industrial Company Limited, Hefei, China) was pushed to a depth of 1 cm into each cooked root section. This was done at three different positions of the sectioned root i. e. , three technical measurements taken per root section. Hence, we obtained three observations for each time point, per genotype per site, a dataset appropriate for quantifying heritability for root softness in cassava.
Statistical analyses Softness quantitative data. In order to determine heritability of root softness, we jointly analysed softness data generated from Arua and Mubende trials. Initially, we processed each cooking time point (15, 30, 45 and 60 min) separately, and thus generated four datasets for root softness. For each dataset, the Box-Cox power transformation  (Box and Cox, 1964)  was conducted to identify the optimal transformation procedure that best corrected for unequal variances and nonnormality of error terms. This analysis was conducted in the MASS package in R (R Core Team, 2015) by fitting a linear model where genotype, environment, incomplete block nested within environment, and plot grid row nested within environment, were fitted as fixed effects. The softness data for 30, 45, and 60 min time points did not need transformation (optimal convenient lambda = 1), whereas the square root transformation (optimal convenient lambda = 0.
test function of the stats package. To represent the true directionality of the relationship between softness BLUPs, the transformed BLUPs at the 15 min time point were back-transformed prior to conducting the correlation analysis. Analysis of consumer data. We used a linear model to analyse the consumer evaluation scores. The Box-Cox procedure  (Box and Cox, 1964)  was implemented by fitting a linear model, where the fixed effects were variety, sex, and age, with consumer evaluation scores as the dependent variable in the MASS package in R. The convenient Lambda of 1. 0 was obtained and thus, data were not transformed. Data were screened for outliers in ASReml-R version 3. 0  (Gilmour et al. , 2009) , by examining the Studentised deleted residuals  (Neter et al. , 1996)  obtained from a linear model fitted with variety, sex, and age as fixed effects.
ACKNOWLEDGEMENT This research was undertaken as part of Roots, Tubers and Bananas (RTB) research, and funded by, the CGIAR Research Programme on RTB and supported by CGIAR Trust Fund contributors. Additional funds were provided by the Next Generation Cassava Breeding Project through funds from the Bill and Melinda Gates Foundation (Project No. OPP1048542) and the Department for International Development of the United Kingdom (UKaid) (Project No. OPP1048542). We thank the technical staff of National Crops Resources Research Institute (NaCRRI) Root Crops Programme, who assisted with field trial establishment, maintenance, and data collection both in the field and laboratory. We also acknowledge the technical guidance from RTBfoods project staff. We give special thanks to Guillaume Bauchet for assistance in data curation.
Methods: The following four steps were conducted to define MediArch: (1) identification of mediation requirements to allow SoS properties; (2) establishment and categorization of twelve types of mediators, for enabling capabilities of communication and control of constituent systems interactions and conversion of heterogeneous messages exchanged through a mediation infrastructure; (3) specification of duties, behaviors, assumptions, and guarantees of mediators; and (4) organization of MediArch in three layers, namely, the constituents & consumer systems layer; the communication, conversion, & coordination layer; and the control layer. This architecture was used as the backbone for the software architectures of two SoS in different domains, namely, flood monitoring system-of-systems (FMSoS), and health-care supportive home system-of-systems (HSH-SoS), for providing evidence on how MediArch supports the architecting process of SoS.
Important advances in software connectors, mediators, emergent middleware, software platforms, and frameworks have been made to overcome interoperability problems in complex and large-scale systems  [3, 8, 25, 36, 40, 42-44, 47, 62, 63]. However, existing approaches do not consider strategies to enable all interoperability levels, i. e. , technical, semantic, syntactic, and organizational, neither other important issues of SoS architectures  [32] , such as dynamic integration of constituent systems, incorporation of new SoS missions or requirements, prediction of emergent behaviors, decision making, and resilience. This article presents MediArch, a three-layered architecture that establishes mediators as first-class software entities to construct SoS. Mediators are located at the two higher layers and aim to offer capabilities of communication, conversion, coordination, and control.
MediArch was used as a backbone for the design of two SoS, namely, FMSoS (Flood Monitoring SoS) and HSH-SoS (Healthcare Supportive Home SoS). Both SoS gave us evidence to conclude that MediArch advances the state-of-the-art on SoS architecting, since it (1) allows the integration of independent constituent systems, (2) provides strategies to control emergent behaviors, (3) defines strategies of control authorities,  (4)  gives structures for SoS evolution, and (5) promotes resilience and adaptability of SoS architectures. The remainder of this article is structured as follows. The "Background" section presents the theoretical background used in this work. The "Materials and methods" section details the methods used to establish and assess MediArch. The "Software mediators for SoS" section describes MediArch and specifies all software mediators that compose this layered architecture.
Definition of MediArch Since SoS architectures must be conceived to address a continuous integration of constituent systems, dynamic reconfigurations, evolution, scalability, and resilience, mediators must be organized towards satisfying such requirements. Therefore, they must be structured in a way they can be created, composed, removed, modified, and reconfigured at without affecting SoS behaviors or constituent systems operations. Interactions among mediators and dependencies among their behaviors were identified for the establishment of mediators organization in SoS architectures. Categories of mediators were organized in a threelayered architecture, called MediArch, detailed in the "Software mediators for SoS" section. The structure of this mediators-oriented architecture was based on the architectural pattern of pace layering, which enables the construction of complex behaviors through layer hierarchies  [57].
Evaluation of MediArch To obtain evidence of the applicability of MediArch, the mediators contained in this architecture were used as first-class software entities for the construction of the software architecture of two SoS, namely, FMSoS (Flood Monitoring SoS) and HSH-SoS (Healthcare Supportive Home SoS). The FMSoS is an SoS whose main missions are the continuous monitoring of rivers in a city and emergency situations detection (e. g. , floods). The HSH-SoS' mission is to assist patients diagnosed with chronic diseases (e. g. , diabetes mellitus) in the management of their conditions during their daily life activities. Both SoS have been a focus of research of our group over the past years, and their mediators-based architectures are detailed in the "Evaluation of MediArch" section. The creation of FMSoS and HSH-SoS architectures followed the guidelines for architecting software systems in  [29] , using MediArch as backbone.
The mediatorsoriented architectures of FMSoS and HSH-SoS were assessed regarding their feasibility to allow SoS properties and their related quality attributes described in the two first columns of Table  1. For this, the following research questions were investigated: For the sake of clarity and simplicity, constituent systems, consumer systems, and mediators are referred to as software entities, i. e. , E, that can be mediated. MediArch was defined following the pace layering pattern  [57]  and is composed of a hierarchy of mediators that establishes dependencies among all type of software entities found in SoS, as illustrated in Fig. 2. Therefore, mediators in upper layers depend on data coming from entities in lower layers. Mediators in the control layer use data provided by mediators in the communication, conversion, & coordination layer to define the current status of the SoS and establish, for instance, emergency and reconfiguration plans.
Control layer The upper layer of MediArch is focused on control issues, ensuring the identification and execution of emergent behaviors, dynamicity of the SoS, and missions accomplishment. Mediators in this layer only have direct interaction with mediators located in the communication and conversion layer. Hence, a direct connection between control mediators and constituent or consumer systems is not possible. Mediators in the control layer are concerned with behavioral and control issues of SoS software architectures. Four mediators, namely, monitor, analyzer, planner, and executer, were defined to deal with architectural reconfigurations for the execution of emergent behaviors, availability of constituent systems capabilities, or changes in SoS missions or its environment. Mediators for control purposes are presented in Fig.
Evaluation of MediArch To assess the applicability of MediArch , presented in the "Software mediators for SoS" section, the software architectures of two SoS, FMSoS and HSH-SoS, were structured considering mediators as first-class entities and are presented in the "Examples of SoS architectures application based on MediArch" section. The "Results of MediArch assessment" section provides answers to the five research questions introduced in the "Materials and methods" section.
Examples of SoS architectures application based on MediArch To design software architectures of FMSoS and HSH-SoS, the guidelines proposed by Hofmeister et al. [29]  were followed. These guidelines define that, in a general way, the architecting process comprises the stages of domain analysis, architectural analysis, architectural synthesis, and architectural evaluation. Specifically, in the stage of synthesis, software architectures of both SoS were built following the structure proposed in Medi-Arch, depicted in Fig. 2. In the remainder of this section, both architectures for FMSoS and HSH-SoS are presented in the "Flood monitoring systems-of-systems-FMSoS" and "Healthcare supportive home systems-of-systems -HSH-SoS" sections, respectively.
Results of MediArch assessment Based on the experience of using software mediators defined in MediArch to construct FMSoS and HSH-SoS, we present a descriptive analysis about how MediArch can contribute to address important properties of SoS architectures, namely, integration of constituent systems, emergent behavior assurance, decision-making or control strategies, evolutionary development, and adaptability or resilience  [32]. In the remainder of this section, we answer the five research questions (RQs) proposed for our study, which were introduced in the "Evaluation of MediArch" section.
RQ5-How do SoS architectures based on MediArch address resilience or adaptability? Most operational and managerial independence and distribution of constituent systems imply inaccessibility of constituents capabilities (due to network problems or unavailability of systems) required in SoS operations. Therefore, SoS architectures must be resilient to support SoS operations in challenging environments. Resilience can be considered in software architectures for enabling the self-organization of their structures and dynamic reconfiguration of their operations. Resilience is an important requirement for SoS and assure reliable and robust operations  [52, 64]. In MediArch, self-organization and dynamic configuration can be achieved by two strategies. The first one is to organize MediArch mediators following the pace layering pattern  [57] , also known as layers of changes.
e. , presence, integration, and homogenization) for information systems. This framework is oriented to collect data from different databases and integrate such data to be presented in an aggregated way to final users. However, this framework does not consider interactions, collaboration, or coordination among data providers which is a common characteristic in SoS. Li et al. [43]  define a mediator to allow cooperation among different web services, focusing on the conversion of individual services work-flows to collaborate in the execution of composed business processes. Spalazzese et al. [62]  is one of the first works proposing the dynamic synthesis of mediators in networked systems. The creation of mediators at runtime is made by a central controller and supports interoperability at technical and organizational levels since communication and operational protocols of distributed systems are homogenized.
e. , centralized, decentralized, full-decentralized), evolve over time including or modifying new requirements, policies, or constituents, and decide and execute reconfigurations at runtime. This is possible, due to mediators were proposed in MediArch to address important qualities, such as interoperability (in all its levels), low-coupling, separation of concerns, scalability, and maintainability. Moreover, based on experiences at architecting FMSoS and HSH-SoS, we are confident that MediArch can be used as backbone to create software architectures for directed, acknowledge, and collaborative SoS.
We observed that existing patterns, proposed more than 15 years ago  [4] , are as relevant now to architectures of contemporary systems (e. g. , SoS and self-* systems), as they are for other types of systems. However, it is important to investigate about pattern languages, architectural frameworks, and reference architectures, to establish guidelines for solving recurrent problems in SoS architectures. MediArch could be used as initial step to standardize architectural solutions for SoS, and its application in FMSoS and HSH-SoS is an important start point for its consolidation.
Construct validity This validity reflects in which measure the use of Medi-Arch supported the construction of SoS architectures that achieve continuous integration of constituent systems, assurance of emergence behaviors, decision-making authorities, evolution, and dynamic configurations. To avoid threats to construction validity, MediArch and its mediators were defined based on deep studies on software connectors and mediators in large-scale and complex systems. Moreover, SoS architectural patterns and styles were investigated to understand their mediation approaches and their support to quality attributes of integration, interoperability (in technical, syntactic, semantic, and organizational levels) situation-aware, accountability of decisions, maintainability, modifiability, separation of concerns, portability, low-coupling, flexibility, scalability, adaptability, fault-tolerance, robustness, and dynamic configurations (see Table  1 ).
Internal validity This validity considers whether all causal relations that affect the application of MediArch were defined and handled. The following factors that could prejudice the construction of SoS architectures based on MediArch were identified: (1) the understanding of FMSoS and HSH-SoS scope and their requirements, which had no impact on results, since authors had previous experience on working with both SoS; (2) the difficulty to understand mediators and their application in SoS architectures, that was avoided, since mediators and the layered architecture were proposed based on well-known architectural patterns and styles; and (3) problems to instantiate MediArch, that were mitigated by using well-understood guidelines for software architecting  [29].
Conclusions and future works In our preliminary work  [23] , we established a taxonomy to support the selection of software mediators during architectural design of SoS. In this work, we extend such taxonomy as basis to construct MediArch, a high-level architecture composed of three layers: the constituent and consumer systems layer; the communication, conversion, and coordination layer; and the control layer. The last two layers describe hierarchical organizations of three software mediators, namely, communication & coordination, conversion, and control. MediArch considers mediators as first-class entities in SoS architectures and was used as a backbone during the architectural synthesis of two systems, FMSoS, in the domain of crisis and emergency management, and HSH-SoS, in the domain of smart homes for health-care.
Software architectures for both SoS have already been studied by authors in  [21, 22, 26, 27]. In particular, in this work, alternative architectures for these SoS were presented using software mediators as core entities to enhance continuous integration of constituent systems, assurance of emergence behaviors, decision-making authorities, evolution, and dynamic configurations. As future work, validation and verification of SoS software architectures based on MediArch can be done using simulation approaches such as those presented in  [26]. Mediators were defined in an abstract way to support low-coupled architectures; hence, it is expected mediators could be dynamically synthesized and deployed to conform to different architectural configurations of an SoS. Moreover, mediators described herein are fine grained, with clear objectives and specifications; hence, they can be also implemented following different architectural styles, for instance, SOA or microservices to construct service-oriented SoS.
Additionally, MediArch can be used to design more complex SoS architectures and reference architectures in different domains, as presented in  [21, 22]. Finally, we intend to develop and publish a mediators-based platform that implements MediArch. This platform will facilitate SoS mediation improving the development of those systems, reducing costs and time. Besides that, it is our goal to continue investigating on mechanisms to support interoperation and dynamic organization of SoS in different domains, for instance, education, defense  [6] , and big data  [60].
e. , E, that can be mediated. MediArch was defined following the pace layering pattern [57]  and is composed of a hierarchy of mediators that establishes dependencies among all type of software entities found in SoS, as illustrated in Fig. 2. Therefore, mediators in upper layers depend on data coming from entities in lower layers. Mediators in the control layer use data provided by mediators in the communication, conversion, & coordination layer to define the current status of the SoS and establish, for instance, emergency and reconfiguration plans. Similarly, this middle layer depends on.
Moreover, light confinement in the vertical direction is not perfect and the total reflection at each interface induces an evanescent vertical field profile in surrounding media. For a given guided mode, the extinction coefficient αsub of the evanescent wave in the cladding layer is expressed by  [28] : sub = 2 eff -sub (2) The inverse of the extinction coefficient gives the penetration depth in the cladding layer. If the thickness of this latter is superior or equal to 15 times the penetration depth, the interaction between the guided mode and the underneath substrate (here silicon) becomes negligible. In the following, light propagation in our micro-structured architecture has been modelled using the 2D and 3D Mode Solver software developed by Optiwave for the analysis of planar and channel waveguides, respectively.
Characterization The fluorescence emission of Rudpp-doped Ti-BzAc layers was measured at room temperature under excitation at 460 nm using a Plate reader infinite 200 PRO -TECAN spectrometer that enables measurements in air or in liquid media. The opto-geometrical properties of epoxy and Ti-BzAc layers, namely the thickness and refractive indices at the Rudpp excitation (460 nm) and emission wavelength (610 nm), were deduced from spectroscopic ellipsometry measurements performed with an AutoSE HORIBA Scientific device. To extract the thickness and refractive index values, spectral data acquired in the 400-800 nm wavelength range were fitted with the empirical Cauchy model that is commonly employed for transparent materials. The profile and dimensions of photo-imprinted Ti-BzAc patterns were studied by Atomic Force Microscopy (AFM) using a Bruker Dimension Icon device in tapping mode and by stylus profilometry using a Bruker Dektak device.
The waveguide output facet was carefully cut and polished using a circular precision saw (DISCO DAD32). Thanks to this polished facet, the emerging light was focused on a Solinocam H2D2 camera through an Mitutoyo objective lens. So-obtained images were first acquired through a Firewire card analyzed with the LabVIEW software. The emerging light intensity converted in a text file was then integrated on the whole waveguide section using the MATLAB software. More detailed data on these measurements are provided in the 'Results and discussion' section.
6a. Thus, these data globally demonstrate that our two-step deposition / insolation procedure enables to elaborate a channel waveguide / diffraction grating architecture that reliably respects the patterns obtained after a single insolation. Channel waveguide / diffraction grating coupling was assessed on so-obtained architectures using the optical set-up described in section 2. 4. For practical convenience, light at a 610 nm wavelength was injected through a diffraction grating (> 100 µm in length and with a 1 µm / 2 µm width / pitch) at the input of waveguides (1 mm in length and with 10 to 50 µm widths), and it was collected from their polished outlet facet, i. e. a grating -waveguide configuration. This is a reverse configuration compared to the previously modeled one where light was firstly injected in the waveguide and then extracted through the grating, i.