text
stringlengths 0
128k
|
|---|
/*
* ***** BEGIN LICENSE BLOCK *****
* Zimbra Collaboration Suite CSharp Client
* Copyright (C) 2009, 2010, 2012 VMware, Inc.
*
* The contents of this file are subject to the Zimbra Public License
* Version 1.3 ("License"); you may not use this file except in
* compliance with the License. You may obtain a copy of the License at
* http://www.zimbra.com/license.
*
* Software distributed under the License is distributed on an "AS IS"
* basis, WITHOUT WARRANTY OF ANY KIND, either express or implied.
* ***** END LICENSE BLOCK *****
*/
package org.zmail.utils;
import java.io.*;
import java.text.*;
import java.util.logging.*;
import java.util.logging.Formatter;
import java.util.*;
public class ZCSPLogger
{
private static Logger deflogger;
private static boolean deflog_init=false;
private static FileHandler dfh;
private static final String default_loggername="ZCSPROV";
private static final int log_max_size=100*1000000; // 100 Mb
private static final int log_max_files=100;
private String ilogpath;
private HashMap<String,Logger> LoggerMap;
private HashMap<String,FileHandler> FileHandlerMap;
Handler hwndconsole;
public ZCSPLogger(String logpath)
{
ilogpath=logpath;
LoggerMap=new HashMap<String,Logger>();
FileHandlerMap=new HashMap<String,FileHandler>();
hwndconsole = new ConsoleHandler();
hwndconsole.setFormatter(new ConsoleLogFormatter());
}
public synchronized Logger get_logger(String logname)
{
Logger tmplogger=null;
try
{
if (LoggerMap.containsKey(logname))
{
return LoggerMap.get(logname);
}
FileHandler tmplfh;
boolean append =true;
String lgname = ilogpath+logname+"_%g.log";
int limit = log_max_size;
int numLogFiles = log_max_files;
tmplfh = new FileHandler(lgname, limit, numLogFiles,append);
tmplfh.setFormatter(new LogFormatter());
tmplogger = Logger.getLogger(logname);
tmplogger.addHandler(tmplfh);
tmplogger.setUseParentHandlers(false);
tmplogger.log(Level.INFO, "**********************************************************");
tmplogger.log(Level.INFO, "Start Logging:");
tmplogger.log(Level.INFO, "**********************************************************");
tmplogger.addHandler(hwndconsole);
LoggerMap.put(logname,tmplogger);
FileHandlerMap.put(logname,tmplfh);
}
catch(Exception ex)
{
System.out.println(ex.getMessage());
ex.printStackTrace();
}
return tmplogger;
}
public synchronized void RemoveConsoleHwnd(String logname)
{
Logger tmpLogger=null;
if (LoggerMap.containsKey(logname))
{
tmpLogger=LoggerMap.get(logname);
}
if (tmpLogger!=null)
{
tmpLogger.removeHandler(hwndconsole);
}
}
public synchronized void AddConsoleHwnd(String logname)
{
Logger tmpLogger=null;
if (LoggerMap.containsKey(logname))
{
tmpLogger=LoggerMap.get(logname);
}
if (tmpLogger!=null)
{
tmpLogger.addHandler(hwndconsole);
}
}
public synchronized void close(String logname)
{
Logger tmpLogger=null;
if (LoggerMap.containsKey(logname))
{
tmpLogger=LoggerMap.get(logname);
}
if (tmpLogger!=null)
{
FileHandler tmpFh= FileHandlerMap.get(logname);
tmpLogger.removeHandler(tmpFh);
tmpFh.close();
tmpLogger=null;
}
hwndconsole.close();
}
public synchronized void closeAll()
{
Set<String> LoggerSet=LoggerMap.keySet();
Iterator itr= LoggerSet.iterator();
while (itr.hasNext())
{
String log_name=(String)itr.next();
close(log_name);
}
}
//returns default app logger
public static synchronized Logger get_default_logger()
{
if (!deflog_init)
{
try
{
boolean append =true;
String fqlogpath=ZCSUtils.getCurrentDirectory()+"/logs";
String lgname = "zcsprov%g.log";
String fqnlog= fqlogpath+"/"+lgname;
ZCSUtils.check_dir(fqlogpath);
int limit = log_max_size;
int numLogFiles = log_max_files;
dfh = new FileHandler(fqnlog, limit, numLogFiles,append);
dfh.setFormatter(new LogFormatter());
deflogger = Logger.getLogger(default_loggername);
deflogger.addHandler(dfh);
deflog_init=true;
deflogger.log(Level.INFO, "**********************************************************");
deflogger.log(Level.INFO, "Start Logging:");
deflogger.log(Level.INFO, "**********************************************************");
}
catch (IOException e)
{
e.printStackTrace();
}
}
return deflogger;
}
//close default logger
public static synchronized void close_default_logger()
{
if (dfh!=null)
{
deflogger.removeHandler(dfh);
dfh.close();
dfh=null;
}
}
}
class LogFormatter extends Formatter
{
private static final DateFormat dtformat = new SimpleDateFormat("MM/dd/yyyy HH:mm:ss");
private static final String lineSep = System.getProperty("line.separator");
public String format(LogRecord record)
{
String loggerName = record.getLoggerName();
if(loggerName == null)
{
loggerName = "root";
}
StringBuilder output =null;
output = new StringBuilder()
.append("*****")
//.append(loggerName)
.append("[")
.append(record.getLevel()).append('|')
.append(Thread.currentThread().getName()).append(':')
.append(Thread.currentThread().getId()).append("| ")
.append(dtformat.format(new Date(record.getMillis())))
.append("]: ")
.append(record.getMessage()).append(' ')
.append(lineSep);
return output.toString();
}
}
class ConsoleLogFormatter extends Formatter
{
private static final DateFormat dtformat = new SimpleDateFormat("MM/dd/yyyy HH:mm:ss");
private static final String lineSep = System.getProperty("line.separator");
public String format(LogRecord record)
{
StringBuilder output = new StringBuilder()
.append("[")
.append(record.getLevel()).append('|')
.append(Thread.currentThread().getName()).append(':')
.append(Thread.currentThread().getId()).append("| ")
.append(dtformat.format(new Date(record.getMillis())))
.append("]: ")
.append(record.getMessage()).append(' ')
.append(lineSep);
return output.toString();
}
}
|
'use strict';
const express = require('express');
const router = express.Router();
const artworksModel = require('../models/Artworks');
const ArtworksCollection = require('../models/data-collection-class');
const artists = new ArtworksCollection(artworksModel);
router.get('/artworks', getArtworks);
router.get('/artworks/:id', getArtwork);
router.put('/artworks/:id', updateArtwork);
router.post('/artworks', createArtwork);
router.delete('/artworks/:id', deleteArtwork);
router.delete('/artworks', deleteAllArtworks);
async function getArtworks(req, res) {
res.status(200).json(await artists.get());
}
async function getArtwork(req, res) {
res.status(200).json(await artists.get(req.params.id));
}
async function createArtwork(req, res) {
res.status(200).json(await artists.create(req.body));
}
async function updateArtwork(req, res) {
res.status(200).json(await artists.update(req.params.id, req.body));
}
async function deleteArtwork(req, res) {
res.status(200).json(await artists.delete(req.params.id));
}
async function deleteAllArtworks(req, res) {
res.status(200).json(await artists.delete());
}
module.exports = router;
|
VBA - Hide Excel (Start Pop ups)
I tried to search a lot to find an answer but all search results just ending up giving a solution to hide the excel interface.
my code is:
' Start Excel and get Application object.
oXL = New Excel.Application
' Set some properties
oXL.Visible = False
oXL.DisplayAlerts = False
oXL.WindowState = Excel.XlWindowState.xlMaximized
Dim wkbk As Excel.Workbook = oXL.Workbooks.Add
'add(worksheet)
wkbk.Worksheets.Add()
'open existing work
oWB = oXL.Workbooks.Open("...")
' Get the active sheet
oSheet = DirectCast(oWB.ActiveSheet, Excel.Worksheet)
oSheet.Name = "Sheet1"
While it does hide excel ones it is open as a process, it still pops up to open the file and the workbook THEN it goes into hidden.
Is there anyway to prevent the process flashing the excel workbook on the screen for some seconds?
appreciate advises.
Thank you in advance.
mfg Dom
oXL.Screenupdating = False
Seems a bit better (faster), but 2 workbooks still pop up for about 1 second
Try commenting out the WindowState line
Why are you maximizing Excel if you don't want it visible? That line of code seems likely to be the problem. Please maximize this window, then don't show it seems like a logic error to me.
yea, thanks for pointing it out. I deleted it already when i added your suggestions, so unfortunately it was not the problem
|
1. Introduction {#sec1-sensors-21-08017}
With the advancement of digital technology from the past few decades, every digital equipment and appliance is expected to be embedded with tiny yet powerful device called sensor nodes. Furthermore, the wireless communication between physical items and sensors to exchange information for smart living in the future has been coined as the Internet of Things (IoT). In the world of modern wireless telecommunications, IoT is a revolutionary paradigm that is rapidly growing \[[@B1-sensors-21-08017]\]. When these sensor nodes communicate together to collect a large amount of data from the targeted area via the wireless channel, they are called Wireless Sensor Networks (WSNs). Businesses, industries, and the military have utilized WSN to track an object or monitor a phenomenon. Besides, many types of research areas have emerged from the WSNs domain such as from routing protocol, security, and privacy to data mining and many others. Nevertheless, currently, researchers are concerned with improving the performance of the WSNs technologies \[[@B2-sensors-21-08017]\]. In WSN, sensor nodes are equipped with sensing, processing, radio, and power unit, yet they have limited resources in terms of energy, computation, and storage \[[@B3-sensors-21-08017]\]. Frequently, a large number of the sensor nodes are deployed widely in the target environment and continuously communicate the phenomenon measurement like ambient temperature, relative humidity, soil moisture, and wind speed to the base station. Therefore, in most situations, sensor data need to collect accurate and reliable measurements for data analysis and decision-making especially in a critical domain such as in meteorology stations, military applications as well as security monitoring. Unfortunately, the raw data collected from WSN communications usually are not reliable and inaccurate due to the imperfect nature of WSNs \[[@B2-sensors-21-08017]\]. The reason is that the sensor nodes are deployed in a harsh and unattended environment, and vulnerable to malicious attacks. Therefore, data collected from these sensor nodes are often generates missing data, duplicated or error records. To ensure the collected data is reliable and accurate for data analysis and decision-making, one of the solutions is to detect erroneous data, malicious attacks, or changes in the environment namely anomaly or outlier detection (These terms will be used inter changeably throughout this paper). Anomaly detection is one of the potential approaches that can be considered as a solution. Furthermore, it is defined by \[[@B4-sensors-21-08017]\] as the process of identifying data patterns that vary from anticipated behaviour. When it comes to WSNs, anomaly detection has been widely employed across a wide range of industries such as the military and environmental sectors \[[@B5-sensors-21-08017]\]. This is due to the characteristic of low-cost, small in size, and multi-functional sensor nodes; it helps to achieve the need for fast and cheap data collection.
Identifying misbehaviour or anomalies in the network is important in providing liable and secure functioning of the network \[[@B6-sensors-21-08017]\]. In comparison to networks like MANET and BAN, sensor network has resource constraint and has been a major designing challenge in lightweight detection scheme. Although many techniques have been proposed to design and develop a lightweight anomaly detection model for WSNs, effective and efficient solutions are still a major research challenge. The common design issue in the existing solution lay in the online updating of the detection model and the use of communication overhead among sensors nodes.
This paper focuses on designing a lightweight anomaly detection scheme to provide reliable data collection while consuming less energy using one-class learning schemes and dimension reduction concepts. This paper aims to design and develop a lightweight anomaly detection by accurately detecting anomalous data while utilizing energy efficiently. One-class support vector machine (OCSVM) is used as an anomaly detection algorithm due to its advantage in classifying unlabelled data while the hyper-ellipsoid variance can detect multivariate data. Various OCSVM formulations have been proposed such as a hyper-plane, hyper-sphere, Quarter-sphere, Hyper-Ellipsoid, and Centred-Ellipsoid (CESVM). On the other hand, to decrease the computational complexity, CCIPCA is utilized to reduce data dimensions.
An accurate sensor measurement is needed to make an important decision at the end- point such as the base station. However, the raw data collected from sensors may be inaccurate due to many reasons. For instance, hardware failures, changes in the environment as well as malicious attacks that may produce anomalies or outliers in data. These data anomalies or outliers can be detected by designing and developing an anomaly detection model. Unfortunately, large data distribution in WSN makes communication overhead and needs more computational complexity as well as increases memory usage thus reducing the efficiency of the anomaly detection model \[[@B7-sensors-21-08017],[@B8-sensors-21-08017]\]. Furthermore, the enormous volume of data acquired from sensor nodes contains irrelevant and redundant features \[[@B9-sensors-21-08017],[@B10-sensors-21-08017]\], resulting in increased resource usage and a decrease in detection effectiveness Moreover, multivariate data is also needed to be considered when designing an anomaly detection scheme as multivariate data are always sensed in the target phenomenon \[[@B11-sensors-21-08017],[@B12-sensors-21-08017]\] which also contributed to the energy exhausted. Due to these factors, therefore, lightweight anomaly detection which incorporated dimensionality reduction is crucial as proposed in \[[@B13-sensors-21-08017],[@B14-sensors-21-08017]\].
Many anomaly detection solutions such as in \[[@B4-sensors-21-08017],[@B15-sensors-21-08017],[@B16-sensors-21-08017],[@B17-sensors-21-08017],[@B18-sensors-21-08017]\] specifically in WSNs, use a one-class classifier, such as the One-class Support Vector Machine (OCSVM), to construct the normal reference model. The limitation of these solutions is the classification over high-dimensional data which increases the computational complexity and the communication overhead. Meanwhile, the unsupervised Principal Component Analysis (UNPCA) based solutions such as in \[[@B7-sensors-21-08017],[@B19-sensors-21-08017]\] are more lightweight and efficient due to the dimension's reduction used before the classification. However, the effectiveness in terms of the detection accuracy of such solutions needs to be improved. Therefore, a lightweight and effective anomaly detection that incorporated dimensionality reduction with an effective classifier is needed. To this end, in this study, a lightweight and effective anomaly detection scheme is proposed. The contribution of this study can be summarized as follows:An effective and efficient anomaly detection scheme is designed and developed by combining the unsupervised One-Class Support Vector Machine (OCSVM) with the Candid Covariance-Free Incremental Principal Component Analysis (CCIPCA) to decrease the computational complexity and improve memory utilization while increasing the detection accuracy.Various OCSVM formulations have been investigated such as a hyper-plane, hyper-sphere, Quarter-sphere, Hyper-Ellipsoid, and Centred-Ellipsoid (CESVM) to improve the detection accuracy for multivariate data.The Candid Covariance-Free Incremental Principal Component Analysis (CCIPCA) has been incorporated in the design to reduce the data dimension and thus decrease the computational complexity and improve memory utilization.Extensive experiments have been conducted to evaluate and validate the effectiveness and efficiency of the proposed scheme.
The rest of this paper is organized as follows. [Section 2](#sec2-sensors-21-08017){ref-type="sec"} presents the related work. [Section 3](#sec3-sensors-21-08017){ref-type="sec"} describes the proposed CESVM-DR Scheme in detail while [Section 4](#sec4-sensors-21-08017){ref-type="sec"} explains the experimental design and setup. Results and Discussion are presented in [Section 5](#sec5-sensors-21-08017){ref-type="sec"} and this paper is concluded in [Section 6](#sec6-sensors-21-08017){ref-type="sec"}.
2. Related Work {#sec2-sensors-21-08017}
The quality of data sensed by sensor nodes is a crucial issue in WSNs. Erroneous and malicious data can affect data quality \[[@B20-sensors-21-08017]\]. Some of these anomalous data may come from faulty nodes. These erroneous or malicious data are usually known as anomalies or outliers. Outliers in data collected by WSNs can be caused by a various factors, including noise and error, real events, and malicious activities \[[@B21-sensors-21-08017]\]. Therefore, anomaly detection is implemented in WSN to provide more accurate data collection for further analysis at the base station. Nevertheless, accurate and reliable data are needed for critical decision-making such as disaster, or fraud detection. Furthermore, assuring the security of wireless sensor networks and preventing malicious attacks requires the ability to identify anomalous behaviour \[[@B22-sensors-21-08017]\].
The anomaly detection techniques learn normal behaviour and construct a model for normal events in the network \[[@B23-sensors-21-08017]\]. The anomaly detection techniques are either based on the type of background information about the data presented \[[@B24-sensors-21-08017],[@B25-sensors-21-08017]\] or by the type of model they learn. The first approach categorizes anomaly detection into supervised, unsupervised, and semi-supervised. The classifier is trained using labelled data in a supervised mechanism to identify anomalous data. Meanwhile, the unsupervised mechanism, identifies anomalous data without any prior understanding of the data. Lastly, to define a normality boundary, a semi-supervised learning technique uses training on pre-labelled normal results. The second approach categorizes the taxonomy of anomaly detection into classification-based, nearest-neighbour-based, clustering-based, statistical-based, information-theoretic, and spectral-based anomaly detection techniques in \[[@B4-sensors-21-08017]\]. The same taxonomy of anomaly detection techniques is found in the latest survey by \[[@B23-sensors-21-08017],[@B26-sensors-21-08017]\].
The design of anomaly detection model has been addressed using several techniques. used to construct the anomaly detection model. Among these techniques, the one-class classifier is preferred in the WSNs due unsupervised approach \[[@B15-sensors-21-08017],[@B27-sensors-21-08017],[@B28-sensors-21-08017],[@B29-sensors-21-08017],[@B30-sensors-21-08017]\] can be utilized in the absence of a ground truth labelled dataset. One-class classifiers have evolved as a method for scenarios in which only one of two classes in a two-class issue has labelled data \[[@B31-sensors-21-08017]\]. The fundamental concept of OCSVM is to use the feature space's origin as a representation of the abnormal data and then isolate the target sample from the origin by the maximum possible margin \[[@B32-sensors-21-08017]\]. Moreover, anomalous data may often be insufficient due to difficult acquisition or costly manual labelling, thus one-class learning is usually favoured. One-class classifiers are categorized under unsupervised learning by having all the data objects with the same label in the target class. A few anomaly detection solutions, specifically in WSNs, use a one-class classifier to construct the normal reference model, such as the One-class Support Vector Machine (OCSVM) \[[@B4-sensors-21-08017],[@B15-sensors-21-08017],[@B16-sensors-21-08017],[@B17-sensors-21-08017],[@B18-sensors-21-08017]\]. The limitation of these solutions is the classification over high-dimensional data which increases the computational complexity while increasing the communication overhead. While anomaly detection solutions such as in \[[@B7-sensors-21-08017],[@B19-sensors-21-08017]\] use the unsupervised Principal Component Analysis (UNPCA) to construct the reference model which is more lightweight and efficient due to the dimension reduction approach used in the UNPCA. However, the effectiveness in terms of the detection accuracy of such solutions needs to be improved.
Feature space mapping is the core feature of one-class SVM-based outlier detection approaches. Data vectors obtained in the original space are mapped into feature space in a higher dimensional space. In the resulting feature space, a normal data decision boundary is determined that contains most of the data vectors. An outlier is a data vector that is beyond the boundary \[[@B33-sensors-21-08017]\]. Several types of OCSVMs were formulated which can be distinguished by their shapes and formulations namely Hyper-plane \[[@B34-sensors-21-08017]\], Hyper-sphere \[[@B35-sensors-21-08017]\], Quarter-sphere (QS-SVM) \[[@B36-sensors-21-08017]\], Hyper-ellipsoidal (TOCC) \[[@B37-sensors-21-08017]\] and centred ellipsoidal (CESVM) \[[@B15-sensors-21-08017]\]. A study by \[[@B38-sensors-21-08017]\] indicates that the generalization capability and classification performance of OCSVM formulations can be ranked in decreasing order as follows:
On the other hand, data transmission is the main cause for energy depletion com-pared to the data sensing and processing by the sensor nodes. Commonly, there are two ways the sensing data impacts the energy consumption includes the unneeded data sample and power consumption of the sensing subsystem. For its ability to cope with enormous amounts of data, dimensionality reduction has been highlighted as an effective 203 method to overcome the "curse of dimensionality" \[[@B39-sensors-21-08017]\]. Therefore, dimensional reduction is performed to reduce the amount of data sensing data while maintaining sufficient data 205 quality or accuracy after data is transferred to the base station. Moreover, the dimension reduction as the energy-efficient mechanism is one approach to obtain a reduction in the number of data to be sent to the sink \[[@B40-sensors-21-08017]\]. The dimensional reduction schemes based on PCA and its variants, DWT, and ANN algorithm for instance have been used to encode high dimensional data to low dimensional data.
Dimensional reduction techniques have been discussed in \[[@B39-sensors-21-08017],[@B40-sensors-21-08017],[@B41-sensors-21-08017],[@B42-sensors-21-08017],[@B43-sensors-21-08017]\]. Due to computational and energy restrictions in sensor nodes, developing a dimensionality reduction model for WSNs that is suitable to this constraint domain is necessary. Besides, many studies have been developed in univariate settings while few multivariate dimensional reduction models have been introduced. PCA-based dimensional reduction in a univariate data is proposed in \[[@B44-sensors-21-08017],[@B45-sensors-21-08017]\] where PC computing is distributed to sensor nodes. In \[[@B44-sensors-21-08017]\], the network architecture is based on clustered structure and data is collected from the first network layer, while the rest of the layers will perform dimension reduction using CA-based dimension reduction algorithm. Meanwhile, Ref. \[[@B45-sensors-21-08017]\] is based on aggregation tree structure in two-hops communication between sensor node, an intermediate node, and base station. Ref. \[[@B19-sensors-21-08017]\] used kernel PCA (KPCA) to classify outliers data in WSNs as well as to reduce data dimension. Since PCA is one of the encoding algorithms, in this research, KPCA is used in pre-processing step to extract significant features using Mahalanobis kernel thus reducing the data size before the distance-based anomaly detection is applied. The real-world environment consists of multivariate data, thus designing the multivariate dimension reduction is essential to address the power and memory constraint of the WSNs. Few multivariate data reduction models have been proposed in \[[@B46-sensors-21-08017],[@B47-sensors-21-08017],[@B48-sensors-21-08017],[@B49-sensors-21-08017],[@B50-sensors-21-08017]\]. PCA is a popular multivariate data analysis method used to reduce the dimensionality of a set of correlated data observations into a set of uncorrelated variables known as principal components (PCs) \[[@B8-sensors-21-08017],[@B51-sensors-21-08017]\].
The primary purpose of this study is to design more energy-efficient communication in WSNs and reduce the computational complexity. Besides the encoded data accuracy must be maintained after the data is decoded on the recipient's side. Therefore, choosing the lightweight dimension reduction algorithm can contribute to energy-efficient communication, low computational complexity, and may also improve data accuracy. Candid Covariance-Free Incremental Principal Component Analysis (CCIPCA) data dimension schemes based on PCA have been proposed by \[[@B7-sensors-21-08017]\] for the WSNs domain. The CCIPCA algorithm was introduced by \[[@B52-sensors-21-08017]\] to tackle the issue of high-dimensional image vectors. This paper addresses energy-efficient WSN by proposing the CCIPCA reduction technique. Meanwhile, designing one-class support vector machine-based anomaly detection can address the issues of unlabelled data due to the absence of ground truth labelled dataset and a costly manual labelling. Furthermore, using centred ellipsoidal (CESVM) as a one-class classifier results in a considerable reduction in complexity owing to the linear optimization problem, which is considerably less expensive \[[@B38-sensors-21-08017]\]. Therefore, the proposed lightweight anomaly detection scheme in this study combines the CCIPCA with the unsupervised OCSVM based CESVM kernel to decrease the computational complexity, improve memory utilization, and increase detection accuracy.
3. The Proposed CESVM-DR Scheme {#sec3-sensors-21-08017}
In this section, the proposed CESVM-DR scheme is described in detail. The proposed CESVM-DR is a lightweight anomaly detection scheme. CESVM-DR incorporates the dimension reduction method into the one-class anomaly detection to minimize the communication overhead, computational complexity as well as memory utilization. By implementing dimension reduction in the scheme, less energy will be consumed in the sensor nodes due to its' reduced data size. On the other hand, the proposed anomaly detection scheme is developed to detect anomalies based on the one class learning scheme namely One-Class Support Vector Machine (OCSVM) technique. One-class classifiers are unsupervised techniques because they only require input data samples without their labelling into normal or abnormal samples. As stated by \[[@B49-sensors-21-08017]\], the one-class classifies concepts that learn the data during data training without requiring the labelled data. The one-class unsupervised techniques learn the boundary around normal instances during training while some anomalous instances may exist and declare any new instance lying outside this boundary as an outlier. Due to the pre-labelled data being difficult to obtain in WSNs environment, thus CESVM formulation which is a one-class setting is a suitable anomaly detection approach in the WSNs domain. The proposed CESVM-DR detection scheme contains two phases: training and detection phase, as shown in [Figure 1](#sensors-21-08017-f001){ref-type="fig"}. The first phase is conducted offline meanwhile the testing phase is conducted online to classify the new data measurement into normal or anomalous data measurements. Further explanation of the training and detecting phase of the proposed CESVM-DR will be conducted in the next section.
3.1. Description of Proposed CESVM-DR Scheme {#sec3dot1-sensors-21-08017}
This section described the proposed CESVM-DR anomaly detection scheme which consists of the training and the detection phase as shown in [Figure 2](#sensors-21-08017-f002){ref-type="fig"}. The first stage is used to learn the normal behaviour of sensor data at every sensor node in offline mode. Ref. \[[@B53-sensors-21-08017]\] stated that to improve the CESVM scheme with a low-rank representation of the gram matrix for use in distributed detection algorithms with lower communication overhead. Therefore, the proposed anomaly detection classifier adapts a dimension reduction method to reduce the data dimension. It is carried out first by selecting data observations with the size of m to obtain the centered-ellipsoid effective radius R in a specific period. This method of collecting the size of data observations in a specific period has been adapted in several online anomaly detection schemes such as \[[@B52-sensors-21-08017],[@B54-sensors-21-08017],[@B55-sensors-21-08017],[@B56-sensors-21-08017],[@B57-sensors-21-08017]\]. After the data measurement is standardized by mean and standard deviation, CCIPCA is applied to reduce the dimension of the data measurements. Then, the effective radii R will be calculated using Equation (1). All the computed parameters which are mean ($u$), standard deviations ($\sigma$), Eigenvector ($V$), and Eigenvalue ($D$) are stored at each node to be used in the next phase which is detection phase. $$\left. Md~\left( x \right) = \right\|\left. \sqrt{m}{~\mathsf{\Lambda}}^{- 1}{~\mathsf{R}}^{\mathsf{T}}{~\mathsf{K}}_{c}^{i} \right\|$$
### 3.1.1. Training Phase (Offline) {#sec3dot1dot1-sensors-21-08017}
As mentioned earlier, CESVM is used as a classifier to build the normal reference model in this proposed anomaly detection scheme. The nature of an ellipse is based on the covariance of the dataset, thus CESVM is suitable for sensor data where multivariate attributes may induce a certain correlation. For instance, the readings of humidity sensors are correlated to the readings of temperature sensors. In addition, computational complexity, especially computing of reduced eigenvalue and eigenvector for radius calculation in ellipsoidal CESVM motivates the design of lightweight detection techniques. In this study, dimension reduction technique namely CCIPCA proposed by \[[@B54-sensors-21-08017]\] as the solution to obtain both eigenvalue and eigenvector to be used in anomaly detection model. The proposed model, CESVM-DR, is illustrated in [Figure 3](#sensors-21-08017-f003){ref-type="fig"}.
The procedures of the training phase are described as follows:Raw data measurements are collected at each of the sensor nodes to build the normal reference model.The collected data are standardized using mean, µ and standard deviations, σ using mean-centered value.The dimension reduction based on the CCIPCA algorithm is applied to reduce the data dimension and a suitable number of the principal component is chosen.The minimum effective radius, R is calculated based on a calculation of R = $\left\| \sqrt{m}~\Lambda^{- 1}~R^{T}~K_{c}^{i} \right\|$. This parameter is known as the normal reference model to be used in the detection phase.All calculated parameters including σ, µ, V, D, and R are stored in the node. The Eigenvector (V) and Eigenvalue (D) are calculations taken from calculating the centered kernel matrix of the training data.
At the sensor node, all the parameters calculated in the training phase are regarded as the normal state. They will be used to build the normal reference model. The normal reference model is constructed offline, similar to the methods of \[[@B7-sensors-21-08017],[@B15-sensors-21-08017],[@B51-sensors-21-08017],[@B57-sensors-21-08017]\]. The detailed pseudocode algorithm for the training phase of this scheme is shown in Algorithm 1. **Algorithm 1:** Pseudocode algorithm for the training phase of proposed CESVM-DR Scheme**Input:**$S_{Test}$ // $a~{matrix}~\left( n \times m \right.$) of sensor measurements collected from specific time period\
**Output:** are mean $\left( u \right)$, standard deviations $\left( \sigma \right)$, Eigenvector $\left( V \right)$ Eigenvalue $\left( D \right)$ and minimum effective radius $\left( R \right)$ 1.**Do** the following step: 2.Standardize $S_{Test}$ using mean $\left( u \right)$, standard deviations $\left( \sigma \right)$3.Apply CCIPCA on Standardize $S_{Train}$ to obtain Eigenvector $\left( V \right)$ Eigenvalue $\left( D \right)$4.Calculate minimum effective radius (R):$\left. R = \right\|\left. \sqrt{m}~\mathsf{\Lambda}^{- 1}~\mathsf{R}^{\mathsf{T}}~\mathsf{K}_{c}^{i} \right\|$5.Store the normal reference model $\left( {u~,\sigma~,~V,~D,~R} \right)$ to be used on detection phase6.**End**
### 3.1.2. Detection Phase (Online) {#sec3dot1dot2-sensors-21-08017}
For the detection phase, new data measurement will be detected as normal or anomalous. Using the stored reference model obtained from the training phase, the decision function is calculated as shown in Equation (2). $$f~\left( x \right) = sgn\left( {\max(R - Md\left( x \right)} \right)$$
From this decision, the new measurement will be classified as anomalous if the reading is negative and vice versa where $V$ and $D$ are equivalent to $P$ and $\Lambda$. Negative results indicate that the reading is larger than effective radii, $R$ which represents the normal behaviour of training data thus the data is classified as anomalous. [Figure 4](#sensors-21-08017-f004){ref-type="fig"} shows the flowchart of the detection phase of the proposed CESVM-DR anomaly detection scheme. The pseudo-code algorithm for the detecting phase of the proposed CESVM-DR scheme shows in Algorithm 2. **Algorithm 2:** Pseudocode algorithm for the detection phase of proposed CESVM-DR Scheme**Input:**$S_{Test},u,\sigma,V,D$ and $R$ // $S_{Test}~a~matrix~\left( {n \times m} \right)$ of real time sensor measurements\
**Output:** Normal or Anomalous type of class WSN data\
1.***Do*** the following step: 2.Standardize $S_{Test}$ using same mean $\left( u \right)$, standard deviations $\left( \sigma \right)$ from training phase3.Calculate decision function $\mathit{f}~\left( \mathit{x} \right)$: $f~\left( x \right)~ = ~sgn\left( {\max(R - Md\left( x \right)} \right)$4.Compared the decision function $\mathit{f}~\left( \mathit{x} \right)$ value with $R$ calculated in training phase to class the measurement as normal or anomalous as following condition:\
*If* $\mathit{f}~\left( \mathit{x} \right)$ \> $\mathit{R}$ *then*\
*Class* = *Anomaly*\
*Class = Normal*\
The procedure of the testing phase is described as follow:New data observations of m size collected from the sensor nodes are standardized to the calculation in the training phase using mean (µ) and standard deviation (σ) of the normal reference model.The distance of each new measurement is calculated as described in Equation (1), using the stored normal reference parameters which are Eigenvector (V) and Eigenvalue (D). The measure similarity between data is based on decision functionThese new data measurements are classified as normal or anomalous using the decision function in Equation (2).
The new data measurements are classified as anomalous if the decision function is indicated as negative, meaning their distances from the center is larger than the distances of the normal reference model. Otherwise, it is normal.
In the proposed lightweight CESVM-DR anomaly detection scheme, the complexity is reduced by incorporating the CCIPCA algorithm to minimize the computation complexity of the CESVM algorithm. Therefore, the high communication cost due to the broadcast of the entire covariance matrix among the nodes of the network is reduced by applying CCIPCA to the proposed CESVM-DR scheme especially dealing with multivariate data. To evaluate the detection effectiveness, the performance measures which are represented by detection rate (DR), detection accuracy, and false alarm rate (FNR and FPR) are analysed. These performance measures are used in other anomaly detection models including in \[[@B7-sensors-21-08017],[@B15-sensors-21-08017],[@B19-sensors-21-08017]\]. Meanwhile, the computational complexity and memory utilization, and communication overhead are used to evaluate detection efficiency.
4. Experimental Design {#sec4-sensors-21-08017}
This section explains the process of experiment setup including preprocessing and data labelling. Data labelling techniques used to label the unlabeled data as well as the data processing procedure will also be discussed in this section.
4.1. Preprocessing {#sec4dot1-sensors-21-08017}
Before data labelling, raw data has been undergone the pre-processing process. Raw data collected from sensor nodes is standardized to transform into a standard format using the mean and standard deviation. During the standardization process, the observation data are centered to avoid biased estimation as mentioned in the previous section. The new standardized data can be calculated as illustrated by Equation (3). $$x_{new} = \frac{x - \mu}{\sigma}$$
Every data measurement in the training dataset is standardized using Equation (3). The parameters *µ* and *σ* are the mean and standard deviation of the training dataset. Both *µ* and *σ* are stored in the sensor nodes and will be used to standardize the new data measurements of the testing dataset during the online detection. The CCIPCA dimension reduction scheme will then be applied to the data instances to reduce data dimensionality. The reduced data will then be used as the input for the CESVM classifier.
4.2. Datasets and Data Labeling {#sec4dot2-sensors-21-08017}
The datasets used to evaluate the proposed CESVM-DR detection scheme are obtained from GSB, IBRL, LUCE, PDG, and NAMOS datasets. These datasets have been used in several WSN researches included in several WSN researches included in \[[@B7-sensors-21-08017],[@B14-sensors-21-08017],[@B15-sensors-21-08017],[@B19-sensors-21-08017],[@B28-sensors-21-08017]\] GSB dataset was labelled using simulated-based labelling technique while histogram labelling technique was applied to IBRL, LUCE, PDG, and NAMOS dataset.
Similar to the study in \[[@B57-sensors-21-08017]\], simulated-based labelling was created in this paper. The simulated-based labelling approach is used to label the data measurements taken from a small cluster of GSB sensor deployment. Data measurements were extracted from nodes N25, N28, N29, N31, and N32 are named D1, D2, D3, D4, and D5 respectively. For each dataset, artificial anomalies were randomly generated. The statistical properties of the normal data, such as mean and standard deviation, are computed and used to construct artificial anomalies. The statistical characteristics measured by the mean and standard deviation of both normal and generated artificial anomalies for datasets are presented in [Table 1](#sensors-21-08017-t001){ref-type="table"} (Ambient temperature and relative humidity are selected as an example). Following the study \[[@B57-sensors-21-08017]\], artificial anomalies were created randomly using statistical parameters (see [Table 1](#sensors-21-08017-t001){ref-type="table"}) that differ slightly from the properties of the normal data based on these properties. The artificial anomalies generated randomly based on the statistical properties were injected into the normal data to be used in the experiments.
The artificial anomalies based simulated-based labeling approach is generated as follows:The normal data measurements are collected from a real-life dataset with the size of $m \times n$ where 𝑚 and 𝑛 represent the number of data measurements and the number of variables respectively. The mean $ui$ and standard deviation $\sigma i$ of the collected data measurements are calculated with $i = 1,~2,\ldots,~n$.The new *µ* and σ values to generate artificial anomalies are selected by adding $ui$ and $\sigma i$ with the preferred amount of deviation to produce slightly different mean and standard deviation from normal values.Based on the selected new µ and σ values, the artificial anomalies are produced based on normal random distribution function, *f* as follow: *Artificial* *anomalies* = *f* ( *µ*, *σ*, *m*, *n*).
The experiments have been conducted with histogram-based data labelling using IBRL, LUCE, PDG, and NAMOS datasets. In the histogram-based labelling approach, datasets are plotted using histogram-based, and anomalous data instances are labelled with visual inspection based on the normality regions of the dataset as in [Figure 5](#sensors-21-08017-f005){ref-type="fig"}. This labelling technique has been used in \[[@B7-sensors-21-08017],[@B51-sensors-21-08017],[@B58-sensors-21-08017],[@B59-sensors-21-08017],[@B60-sensors-21-08017],[@B61-sensors-21-08017]\] to label the unlabeled dataset. From visual investigation on [Figure 5](#sensors-21-08017-f005){ref-type="fig"}, different scenarios on selecting training and testing size are investigated to measure the performance of detection effectiveness of proposed CESVM-DR. The detailed performance result for each dataset is discussed in the next sections.
4.3. Testing Procedures {#sec4dot3-sensors-21-08017}
The experiments were conducted in two stages. A regularization parameter (v) was tested in the first stage to determine the probability of outliers in the data. In general, a high detection rate resulted when the parameter v is set to a large value, yet this led to a greater false alarm rate \[[@B16-sensors-21-08017]\]. As the number of outliers is unknown in the dataset, hence, technique's robustness is assessed utilizing parameter *v*. The robustness performance can be determined, regardless of the v value as the detection rate reading is higher while the false alarm rate is low. For this experiment, the value of v is varied between 0.05 and 0.1 which indicates the value of outliers from 5% to 10%. Meanwhile, the test use three kernel functions as follow:Linear function: $$kLinear\left( {x1,~x2} \right) = \left( {x1 \cdot x2} \right)$$
Radial basis function (RBF)
where $\sigma$ is the width of the kernel function.
where $r$ is the width of the kernel function.
Based on the results obtained, the best kernel function with an acceptable parameter *v* among the three will be used in the second stage of the experiment. 250 normal measurements were selected from the GSB dataset in 10 runs while 10 percent (10%) artificial anomalies were randomly generated based on the simulated-based.
4.4. Performance Evaluation {#sec4dot4-sensors-21-08017}
In this experiment, the proposed CESVM-DR scheme was evaluated in terms of effectiveness and efficiency. The detection effectiveness is analyzed in terms of the detection rate (DR), detection accuracy, false-positive rate (FPR), and false-negative rate (FNR) of the datasets mentioned. Meanwhile, the efficiency is analyzed by measuring the computational complexity and memory utilization, and communication overhead. The effectiveness of the proposed CESVM-DR scheme is evaluated using both simulated-based and histogram-based labelling types while the efficiency is evaluated by analyzing the big O notations tested schemes.
For evaluation, the proposed CESVM-DR scheme is compared with other related CESVM anomaly detection schemes using simulated-based labelling. As the core anomaly detection classifier is adopted from CESVM \[[@B15-sensors-21-08017]\] it is used as a benchmark against the proposed CESVM-DR scheme. In addition, the proposed CESVM-DR is compared with the EOOD scheme \[[@B16-sensors-21-08017]\] and (kPCA) \[[@B19-sensors-21-08017]\]. The evaluation is examined using the RBF kernel function with the kernel width of 2 because it is the most stable kernel width among many experimented values in this study.
5. Results and Analysis {#sec5-sensors-21-08017}
The proposed CESVM-DR scheme is evaluated by comparing its performance in terms of the effectiveness (DR, FPR, FNR, and Accuracy) and efficiency (Big *O* notations of Computational Complexity, Memory Utilization, and Communication Overhead) with the related work using both datasets, the simulated-based and histogram-based labelling types as follows.
5.1. Effectiveness Evaluation {#sec5dot1-sensors-21-08017}
The effectiveness evaluation has been conducted by evaluating the proposed scheme with the related work using both datasets, the simulated-based and histogram-based labelling types as follows.
### 5.1.1. Accuracy Evaluation Using the Simulated-Based Data Labelling {#sec5dot1dot1-sensors-21-08017}
The proposed CESVM-DR scheme is compared with other related CESVM anomaly detection schemes using simulated-based labelling. As the core anomaly detection classifier is adopted from CESVM \[[@B15-sensors-21-08017]\] it is used to be the benchmark against the proposed CESVM-DR scheme. Meanwhile, another related CESVM anomaly detection scheme proposed by \[[@B28-sensors-21-08017]\] called the EOOD scheme is used to evaluate the proposed scheme. The latest anomaly detection model based on kernel PCA (kPCA) was introduced by \[[@B19-sensors-21-08017]\] another anomaly detection scheme used to validate the experimental results. The evaluation is examined using the RBF kernel function with a kernel width of 2 as the most stable kernel width results in the previous section. [Figure 6](#sensors-21-08017-f006){ref-type="fig"} summarizes the average of the accuracy performance (effectiveness) of the tested scheme compared with the proposed CESVM-DR scheme while [Table 2](#sensors-21-08017-t002){ref-type="table"} presents the results in detail.
As shown in [Figure 6](#sensors-21-08017-f006){ref-type="fig"} and [Table 2](#sensors-21-08017-t002){ref-type="table"}, the proposed CESVM-DR scheme outperforms all of the CESVM schemes in all experiments while maintaining a stable 1.2% FPR and 3.92% FNR. On the other hand, EOOD (local) and kPCA (local) outperform some of the datasets compared to CESVM-DR in terms of detection rate and FNR. However, due to higher FPR reported in the EOOD (local) scheme, affects the detection accuracy as compared to the CESVM-DR scheme. It indicates that both the CESVM schemes and kPCA used the same Mahalanobis distance in the algorithm to classify the anomalous data. This distance measure considers the attribute correlation thus can be useful to detect multivariate datasets. As CESVM-DR, CESVM and EOOD are based on the ellipsoidal formulation that also considers multivariate and attributes correlations which separated the normal and abnormal class within the ellipse geometric formulation. Meanwhile, the proposed CESVM-DR using CCIPCA to produce the eigenvector matrix and their corresponding eigenvalues give the advantage to the performance measure results. EOOD on the other hand, model hyper-ellipsoid SVM in the input space and fix the center of hyperellipsoid at the origin. Meanwhile, kPCA is using PCA to detect the anomalous is the only scheme not based on the CESVM algorithm. Therefore, this scheme has no parameters to be tuned.
A test of significance, namely a *t*-test, was used to evaluate the statistically significant difference of accuracy, DR, FPR, and FNR between CESVM-DR with CESVM, EOOD (local), and kPCA (local) anomaly detection schemes. The results show that the difference between the proposed and all tested schemes are significant with all studied performance measures across all the datasets in favour of the proposed CESVM-DR scheme except with DR of EOOD (Local) and kPCA schemes with datasets D4 and D5. However, EOOD (Local) and kPCA schemes failed to strike a balance between FPR and DR which is achieved with significance by the proposed CESVM-DR scheme.
### 5.1.2. Accuracy Performance Result Using Histogram-Based Dataset {#sec5dot1dot2-sensors-21-08017}
The proposed CESVM-DR scheme was benchmarked against other related anomaly detection schemes in PCCAD \[[@B31-sensors-21-08017]\], DWT + SOM \[[@B59-sensors-21-08017]\], and DWT + OCSVM \[[@B58-sensors-21-08017]\] as the same histogram-based data samples were used in these researches. The performance evaluation is presented in [Figure 7](#sensors-21-08017-f007){ref-type="fig"} and [Table 3](#sensors-21-08017-t003){ref-type="table"}.
From [Table 3](#sensors-21-08017-t003){ref-type="table"}, considering the proposed CESVM-DR, the detection rate of 100% and the false-negative rate of 0% are reported in both IBRL and NAMOS datasets. This is due to both datasets were containing univariate data features. Meanwhile, as illustrated in [Figure 5](#sensors-21-08017-f005){ref-type="fig"}a,b short and constant anomalies are present in IBRL and NAMOS datasets respectively, thus the proposed anomaly detection schemes successfully reported better results compared to the PDG dataset in which noise anomalies were presented. For IBRL datasets, the false positive rate of the proposed CESVM-DR is slightly higher than DWT + SOM and PCCAD. On the other hand, DWT + OCSVM and the proposed CESVM-DR schemes are OCSVM based classifiers that result in slightly high FPR. In contrast, the proposed CESVM-DR schemes outperformed all three detection schemes when the NAMOS dataset is used. Meanwhile, varying results are obtained in the PDG dataset for all schemes. Again, DWT + OCSVM and the proposed CESVM-DR scheme reported higher results in terms of detection rate and false-negative rate compared to DWT + SOM and PCCAD schemes.
However, the proposed CESVM-DR scheme reported a high false-positive rate and low detection accuracy compared to other schemes. The false-positive rate is mainly concerned as it represents the normal data which is classified as anomalous data thus affecting the accuracy performance. The datasets PDG exhibited the highest false-positive rate as compared to other datasets. As the PDG dataset is taken from Patrouille des Glaciers the outdoor and extreme environment dataset shows more dynamic datasets compared to other datasets. As shown in [Figure 5](#sensors-21-08017-f005){ref-type="fig"}c, which illustrates measurements from the PDG dataset, the noise measurements are very similar to the normal measurements. Such noises affect the performance of anomaly detection. Furthermore, the dynamic data changes require the tuning of such parameters to cope with these changes. Other reasons include that the cause of the reading used in the training dataset does not reflect the current situation of the new measurement during the detection is performed. Moreover, the normal reference model must be selected carefully in order which describe the overall behavioural data. Therefore, the normal reference model must be updated from time to time to ensure the effective results of the detection performance and false alarm rate.
5.2. Efficiency Evaluation {#sec5dot2-sensors-21-08017}
The efficiency of the anomaly detection model can be measured based on memory utilization, computational complexity, and communication overhead. The efficiency evaluation of the proposed CESVM-DR is compared with CESVM, EOOD, PCCAD, kPCA, DWT + SVM, and DWT + SOM schemes the same as a comparison in effectiveness evaluation. The efficiency evaluation will be evaluated in Big O notation. The efficiency evaluation results are shown in [Table 4](#sensors-21-08017-t004){ref-type="table"} and the description of the parameters used are listed in [Table 5](#sensors-21-08017-t005){ref-type="table"}.
From [Table 4](#sensors-21-08017-t004){ref-type="table"} and [Table 5](#sensors-21-08017-t005){ref-type="table"}, the proposed CESVM-DR is more efficient due to the few factors that are included with the linear optimization compared with the baseline CESVM. That is, the memory complexity CESVM-DR scheme is $O\left( {mn + nd} \right)$ where $d < p$ and d represent the reduced dimension of the data vector and $m < d$. Thus, $O~\left( {mn + nd} \right)$ is equivalent to the $O\left( {nd} \right)$. With regards to computational complexity, the proposed CESVM-DR is formulated as a linear optimization problem, then it is more feasible for implementation on WSNs \[[@B38-sensors-21-08017]\]. That is, the dimensional reduction using CCIPCA added the feasibility of the proposed scheme for implementation on WSNs. In terms of the communication overhead, the proposed CESVM-DR scheme doesn't require any communication to perform the anomaly detection and thus, it is efficient in terms of energy consumption, which is the common design issue for anomaly detection in WSN. The following subsections present a detailed analysis of the efficiency evaluation.
### 5.2.1. Memory Utilization {#sec5dot2dot1-sensors-21-08017}
The proposed CESVM-DR operates in two phases: training and testing. The computation is performed during the training phase, which comprises data processing utilizing mean ($\mu$) and standard deviation ($\sigma$) parameters, and is kept to be used in the subsequent phase. Then, Eigenvalue ($\Lambda$) and the corresponding Eigenvector ($P$) which are calculated using CCIPCA are also stored in the sensor. Radius, R is calculated to determine the cen- tered hyper-ellipsoid border based on calculated eigenvalue ($\Lambda$) and corresponding ei- genvector (P).
For memory utilization, the baseline CESVM keeps the eigenvalues, $P$, and eigenvectors, $\Lambda$ after the linear optimization is done, thus the complexity is represented by $O\left( {mn + np} \right)$. In the calculation, m represents a low-rank approximation of Kernel Gram of RBF kernel function, data observation amounts are denoted by $n$ and $p$ is the data vector's dimension, where $p < n$. Furthermore, the memory complexity of the proposed CESVM-DR is $O\left( {mn + nd} \right)$ where $d < p$ and d represent the reduced dimension of the data vector. The EOOD system is primarily concerned with storing in the memory the observations of the sliding window's size as $O\left( {np} \right)$. Due to the assumption that $n > p$, storage overhead for other parameters like the covariance matrix, which has a cost of $O\left( p^{2} \right)$, is insignificant. The PCCAD does not involve any Kernel Gram calculation, therefore, the memory utilization is only $O\left( {nd} \right)$. As the other schemes operate at the base station and sensor nodes are involved in collecting the data, therefore only $O$(𝑛) of memory is utilized. Meanwhile, kPCA yet involved Mahalanobis kernel thus memory utilization represents as $O\left( {k + np} \right)$ where k represents as Mahalanobis kernel.
The memory utilization in the proposed CESVM-DR is driven from baseline CESVM while the reduced dimension has been applied using CCIPCA which has less memory usage. Because CESVM is formulated using linear optimization, it only requires the de-termination of a radius and this gives benefits to memory utilization. PCCAD used CCIPCA to reduce the data dimension as our proposed CESVM-DR which also reduced memory utilization. Meanwhile, no dimension reduction is involved in both EOOD and kPCA.
### 5.2.2. Computational Complexity {#sec5dot2dot2-sensors-21-08017}
As mentioned earlier, the proposed CESVM-DR operates in the training and testing phase where the training phase is done in an offline manner while the testing phase is done in an online manner. Therefore, the computational complexity of the CESVM-DR is evaluated in the testing phase only. During the testing phase, the calculation is done by (1) standardize the new data measurements using stored ($\mu$) and ($\sigma$) parameter; (2) calculate the distance measure ($Md\left( x \right)$) for every new data measurement based on stored $\Lambda$ and $P$; (3) compare the distance measured with the radius $R$ to classify the new measurement as either normal or anomalous.
As the calculation of CCIPCA, $O\left( N \right)$ is done in the training phase where $N$ is several variables, therefore a total computational complexity of CESVM-DR is $O\left( {N\left( {m^{2}d} \right) + dn^{2}} \right)$ which $O\left( n^{2} \right)$ represents a kernel matrix (also called a Gram matrix) and $d$ represents the reduced dimension of the data vector. Meanwhile, the computational complexity of CESVM scheme involves the computation of a kernel matrix and the complexity of calculation the Eigen-decomposition is $O\left( n^{3} \right)$. However, the eigenvalues decay exponentially for a wide variety of kernels such as the RBF. Therefore, the total computational complexity of CESVM is represented as $O\left( {n^{2} + m^{2}n} \right)$ where $m < n$ that represents the low-rank approximation of the kernel Gram matrix. On the other hand, the computational complexity of EOOD mainly depends on solving a linear optimization problem, which is represented as $O\left( P \right)$, as well as computing covariance matrix, which is represented as $O\left( {mp^{2}} \right)$. Meanwhile, computational complexity in kPCA, involved the calculation of PCs with a complexity of $O\left( {np^{2}} \right)$.
Meanwhile, as the calculation of PCCAD only involves the calculation of dissimilarity measure based on stored parameters $\Lambda$ and $P$ calculated in the training phase thus the computational complexity is represented by $O~\left( N \right)$. On the other hand, DWT + SOM and DWT + SVM computational complexity are considered encoding the data observation using DWT at each node while the detection using SOM and OCSVM is done at the base station. Therefore, the complexity of applying DWT at each node is represented by $O\left( e \right)$. Considering applying anomaly detection for SOM and OCSVM in an online manner will generate $O\left( l \right)$ and $O\left( n^{3} \right)$ respectively. Therefore, the total computational complexity is $O\left( {e + l} \right)$ and $O\left( {m + n^{3}} \right)$ for DWT + SOM and DWT + CESVM respectively.
The proposed CESVM-DR is based on the CESVM baseline scheme which evolved on the calculation of kernel gram matrix. The linear optimization problem formulation in the proposed CESVM-DR scheme makes it more feasible for WSNs application \[[@B38-sensors-21-08017]\]. Furthermore, due to the reduced dimensions proposed in the CESVM-DR schemes the computational complexity of the CESVM is minimized. Although EOOD is based on the hyper-ellipsoidal SVM, it still involved the covariance matrix calculation same as the proposed CESVM-DR. The idea of EOOD is proposed to model the hyper-ellipsoid SVM in the input space, instead of the model in the feature space to reduce the complexity. Meanwhile, PCCAD and kPCA schemes are derived from the PCA algorithm. Both schemes are tuned to suit one class PCA while PCCAD involves dimension reduction and kPCA is based on kernel computational. Meanwhile, Discrete Wavelet Transform (DWT) is integrated into both DWT + SOM and DWT + OCSVM schemes as the data compression approach. In DWT + SOM and DWT + OCSVM schemes, the whole compressed data is sent to the base station for detection. Thus, both DWT + SOM and DWT + OCSVM are also utilizing the reduction of data size technique without losing significant features of the data. However, the limitation of both schemes is adopted batch learning that can affect the computational complexity.
### 5.2.3. Communication Overhead {#sec5dot2dot3-sensors-21-08017}
Communication overhead represents the amount of data communication with the network either between sensor nodes or communication between the sensor nodes and the cluster head or base station. As the anomaly detection is done in the local node, no communication overhead is incurred for the proposed CESVM-DR. The same goes for PCCAD and EOOD where detection is done at the sensor nodes. Meanwhile, the baseline CESVM scheme is based on a centralized anomaly detection where the whole set of data measurements is communicated to the base station. This is represented as $O\left( {np} \right)$ when communication is done between a pair of sensor nodes. The CH receives data vectors periodically from sensors in kPCA detection model, thus communication overhead to transmit the whole data is represented as $O\left( {np} \right)$. For DWT + SOM and DWT + CESVM, communication of wavelet coefficient to the central node is represented as $O\left( {mk} \right)$ where $k$ represents the wavelet coefficient.
6. Conclusions {#sec6-sensors-21-08017}
Designing an effective anomaly detection scheme for WSNs is crucial yet challenging due to the limited resources. The aim is to prolong the sensor connectivity by reducing energy consumption and improving memory utilization while maintaining accurate data at the base station. Due to the ability of unsupervised classification technique to classify unlabeled data as normal or anomalous, the One-Class Support Vector Machine (OCSVM) technique is used as the classifier to design the anomaly detection scheme. The OCSVM variants namely the Centered hyper-Ellipsoidal Support Vector Machine (CESVM) has been formulated based on a linear programming approach while considering multivariate data is used as OSVM kernel to reduce computation costs. However, the parameter tuning to perform the anomaly detection must be tuned properly to suit the datasets for better performance results especially regularization parameter in dynamic data. The proposed lightweight anomaly detection scheme is more efficient and effective compared with the baseline scheme centered hyper-ellipsoidal Support Vector Machine. The complexity of the baseline centered hyper-ellipsoidal Support Vector Machine is further reduced by incorporating of the Candid Covariance-Free Incremental Principal Component Analysis (CCIPCA) algorithm to minimize the computation complexity of the CESVM algorithm. Thus, by applying CCIPCA algorithm the high communication cost due to the broadcasting of the entire covariance matrix among the nodes of the network is reduced in the proposed lightweight anomaly detection scheme. Results of the experiments show higher consistency in detection accuracy and detection rate in all of the experiments either using multivariate or univariate datasets. The comparable false alarm rate is reported throughout the evaluation which was performed with the other anomaly detection schemes. In terms of detection efficiency, with the incorporation of CCIPCA dimension reduction techniques, the communication complexity is reduced compared to the original CESVM anomaly detection scheme.
One of the limitations of the proposed lightweight anomaly detection scheme is the ability to globally assure the real anomalous nature of normal events during the anomaly detection process. The effectiveness and efficiency of the proposed anomaly detection scheme can be further improved by designing the distributed anomaly detection using spatial correlation of sensor nodes in the cluster to construct a global normal reference. Meanwhile, dynamic changes in deployed environments have an impact on the effectiveness of anomaly detection models. As the reference normal model becomes rigid over time, adaptive learning of the model is required to ensure the quality of sensor measurements.
The authors would like to acknowledge Taif University Researchers Supporting Project number (TURSP-2020/292) Taif University, Taif, Saudi Arabia.
Conceptualization, N.M.Z., A.Z. and M.A.R.; methodology, N.M.Z., A.Z. and M.A.R.; software, A.Z. and F.S.; validation, A.Z., F.A.G., E.H.A. and F.S.; formal analysis, N.M.Z. and A.Z.; investigation, N.M.Z. and M.A.R.; resources, A.Z., E.H.A. and F.S.; data curation, M.A.R., F.S. and F.A.G.; writing---original draft preparation, N.M.Z.; writing---review and editing, N.M.Z., A.Z. and F.A.G.; visualization, N.M.Z., A.Z.; supervision, A.Z. and M.A.R.; project administration, A.Z. and E.H.A.; funding acquisition, E.H.A. All authors have read and agreed to the published version of the manuscript.
This work is supported by Taif University Researchers Supporting Project number (TURSP-2020/292) Taif University, Taif, Saudi Arabia.
For more information on datasets used in the experiments, please visit:GSB, Grand-St-Bernard (GSB) dataset, 2007. <http://lcav.epfl.ch/cms/lang/en/pid/86035>, Accessed date (20 April 2018)IBRL, Intel Berkeley Research Lab Dataset, 2004. <http://db.csail.mit.edu/labdata/> labdata.html, Accessed date (26 September 2017)PDG, Patrouille des Glaciers dataset, 2008. <http://lcav.epfl.ch/cms/lang/en/pid/86035>, Accessed date (23 April 2016)LUCE, Lausanne Urban Canopy Experiment, 2007. <http://lcav.epfl.ch/cms/lang/en/pid/86035>, Accessed date (24 January 2018)NAMOS, Networked Aquatic Microbial Observing System Dataset, 2006. <http://robotics.usc.edu/~namos/data/>, Accessed date (12 October 2017).
The authors declare no conflict of interest regarding the publication of this paper.
::: {#sensors-21-08017-f001 .fig}
The Overview of Proposed CESVM-DR anomaly detection scheme.
::: {#sensors-21-08017-f002 .fig}
The training and detection phase of the proposed CESVM-DR anomaly detection scheme.
::: {#sensors-21-08017-f003 .fig}
Flowchart of Training Phase for the CESVM-DR Model.
::: {#sensors-21-08017-f004 .fig}
Flowchart for Detection Phase in the proposed CESVM-DR Scheme.
::: {#sensors-21-08017-f005 .fig}
Histogram plots for (**a**) IBRL, (**b**) LUCE, (**c**) PDG and (**d**) NAMOS Dataset.
::: {#sensors-21-08017-f006 .fig}
Average Performance Comparisons Accuracy and DR (**left**) while FPR and FNR (**right**).
::: {#sensors-21-08017-f007 .fig}
Average Performance Comparisons Accuracy and DR (**left**) while FPR and FNR (**right**).
::: {#sensors-21-08017-t001 .table-wrap}
Statistical characteristics for normal and generated artificial anomalies for GSB datasets.
Dataset Variable Normal Anomalies
--------- ---------------------- -------- ----------- -------- --------
D1 Ambient temperature\ 5.26\ 8.28\ 7.75\ 9.90\
Relative humidity 25.43 0.99 33.83 0.86
D2 Ambient temperature\ 3.61\ 7.44\ 5.39\ 9.00\
Relative humidity 14.24 1.97 20.88 4.11
D3 Ambient temperature\ 3.29\ 6.86\ 5.33\ 9.77\
Relative humidity 20.27 0.74 27.52 1.00
D4 Ambient temperature\ 4.56\ 8.15\ 7.69\ 10.02\
Relative humidity 10.22 2.94 15.14 5.09
D5 Ambient temperature\ 3.37\ 7.92\ 10.65\ 11.60\
Relative humidity 24.71 1.29 33.08 1.34
::: {#sensors-21-08017-t002 .table-wrap}
Performance comparison between the proposed CESVM-DR scheme and related anomaly detection schemes using simulated labelling with a kernel width of 2.
Measure Scheme D1 D2 D3 D4 D5 Average
-------------- ---------- ------ ------ ------ ------ ------- -----------
DR (%) CESVM-DR 96.4 92 92 100 100 96.08
CESVM 74.8 85.2 82 78.8 80.8 80.32
EOOD (local) 100 100 100 100 100 100
kPCA(local) 100 100 100 100 100 100
FPR (%) CESVM-DR 1.2 1.2 1.2 1.2 1.2 **1.2**
CESVM 1.2 1.2 1.2 1.2 1.2 1.2
EOOD (local) 32.7 32.7 40.9 34.5 30.5 34.26
kPCA(local) 7.4 37.6 47.2 35.4 7.4 27
FNR (%) CESVM-DR 3.6 8 8 0 0 **3.92**
CESVM 25.2 14.8 18 21.2 19.2 19.68
EOOD (local) 0 0 0 0 0 0
kPCA(local) 0 0 0 0 0 0
Accuracy (%) CESVM-DR 98.6 98.2 98.2 98.9 98.9 **98.56**
CESVM 96.6 97.6 97.3 97 97.2 97.14
EOOD (local) 70.3 70.3 62.8 68.6 72.3 68.86
kPCA(local) 93.3 65.3 57.1 64 63.6 68.66
::: {#sensors-21-08017-t003 .table-wrap}
The Comparison Proposed of Effectiveness Evaluation with Other Related Anomaly Detection Schemes Using Histogram-Based Labelling.
Dataset Model DR ACC FPR FNR
----------- ------------- ------ ------ ------ -----
IBRL DWT + OCSVM 100 98.3 1.9 0
DWT + SOM 100 99 1.09 0
PCCAD 100 99.7 0.3 0
CESVM-DR 100 98.4 1.6 0
LUCE DWT + OCSVM 100 98.3 1.9 0
DWT + SOM 100 99 1.09 0
PCCAD 100 99.9 0.09 0
CESVM-DR 100 98 2 0
PDG DWT + OCSVM 99.7 97.6 2.6 0.3
DWT + SOM 83 97.8 0.5 16.5
PCCAD 97.9 96.7 3.5 2.1
CESVM-DR 99.1 78.6 25.8 0.01
NAMOS DWT + OCSVM 100 88.6 12.8 0
DWT + SOM 100 99.4 0.5 0
PCCAD 100 90.2 11.5 0
CESVM-DR 100 100 0 0
::: {#sensors-21-08017-t004 .table-wrap}
The efficiency evaluation between CESVM-DR and other schemes.
Scheme Memory Utilization Computational Complexity Communication Overhead
------------- ------------------------------ ------------------------------------------------------- ------------------------
CESVM $O~\left( {mn + np} \right)$ $O\left( {n^{2} + m^{2}n} \right)$ $O\left( {np} \right)$
EOOD $O\left( {np} \right)$ $O\left( {P + mp^{2}} \right)$ \-
PCCAD $O\left( {nd} \right)$ $O\left( {Nd} \right)$ \-
kPCA $O\left( {k + np} \right)$ $O\left( {np^{2}} \right)$ $O\left( {np} \right)$
DWT + SOM $O~\left( n \right)$ $O\left( {e + l} \right)~\left( {online} \right)$ $O\left( {mk} \right)$
DWT + OCSVM $O~\left( n \right)$ $O\left( {e + s^{3}} \right)~\left( {online} \right)$ $O\left( {mk} \right)$
CESVM-DR $O~\left( {mn + nd} \right)$ $O~\left( {P + m^{2}d + dn^{2}} \right)$ \-
::: {#sensors-21-08017-t005 .table-wrap}
The description of efficiency parameter.
*m* Low-rank approximation of the kernel Gram matrix
*n* Number of the data observations
*p* The dimension of the data vector
*d* The reduced dimension of the data vector
*P* linear optimization problem calculation
*N* The calculation of CCIPCA
*e* applying anomaly detection for DWT
*s* applying anomaly detection online for OCSVM
*l* applying anomaly detection for SOM
*k* communication of wavelet coefficient to the central node
|
Loss-of-function of cell cycle checkpoints is frequent in tumors \[[@R1], [@R2]\]. Because such tumors have increased reliance on the remaining elements of cell cycle control, targeting the kinases that regulate cell cycle checkpoints has been proposed as an anti-cancer therapeutic strategy \[[@R2]--[@R5]\]. Currently, ten selective small molecule inhibitors of the cell-cycle checkpoint kinases CHEK1, CHEK2, or WEE1 have been tested in clinical trials, and many more are in preclinical development \[[@R2], [@R6], [@R7]\]. These compounds have shown clinical activity either in combination with DNA damaging chemotherapy or as single agents in several tumor types \[[@R2], [@R4], [@R5], [@R8]--[@R10]\]. Recently, WEE1 inhibitors have been explored in combination with CHEK1 and CHEK2 inhibitors \[[@R11]--[@R13]\] and also histone deacetylase (HDAC) inhibitors \[[@R14]\].
It has been proposed that checkpoint kinase inhibitors may be most active in tumors with defects in specific aspects of DNA damage repair, including homologous recombination (HR), the Fanconi Anemia pathway, or *TP53* loss-of-function \[[@R15]--[@R17]\]. Nonetheless, much remains unknown about the genetic predictors of activity for these compounds. At present, a number of clinical trials involving checkpoint kinase inhibitors are underway \[[@R2], [@R18]\], but these are being performed without use of biomarker stratification to pre-select patients most likely to respond to therapy. On the other hand, the recent report of a remarkable and possibly curative response to the CHEK1 and CHEK2 (CHEK1/2) inhibitor AZD7762 in a small-cell tumor with *RAD50* mutation illustrates what is possible when a targeted therapy is given to a susceptible tumor \[[@R19]\]. This case highlights the importance of using molecular markers to prospectively identify patients with susceptible tumors so that they can be put on effective therapy.
One general strategy for identifying markers of response to a particular drug is to screen for synthetic-lethal genetic interactions with the drug target \[[@R20], [@R21]\]. Two genes are said to be 'synthetic lethal' if simultaneous disruption of both genes results in cellular death, whereas independent disruption of either gene is tolerated \[[@R22]\]. Cancers with mutations in tumor suppressor genes (TSG) that are synthetically lethal with therapeutic targets such as CHEK1 should be particularly sensitive to inhibition of that target. Consequently, such mutations become markers for selection of patients most likely to respond to targeted therapy. The recent FDA approval of the PARP1 inhibitor olaparib, specifically for ovarian cancer patients harboring *BRCA1* or *BRCA2* mutation, demonstrates the clinical viability of this strategy \[[@R23]\].
Here, we identify synthetic-lethal genetic interactions with CHEK1 in order to stratify tumors with an increased sensitivity to checkpoint kinase inhibition. We identify the human gene RAD17 Homolog (*RAD17*) to be synthetically lethal with both AZD7762 as well as MK-1775, an inhibitor of WEE1. When *RAD17* expression is suppressed, the combination of AZD7762 and MK-1775 shows a potent synergistic toxicity associated with a marked accumulation of γH2AX.
Chemogenetic profiling of AZD7762 identifies synthetic lethal interactions with *RAD17* and other DNA repair genes {#s2_1}
To identify genes with a synthetic lethal relationship to AZD7762, a chemogenetic screen was performed in HeLa cells against a panel of 112 known or suspected TSG ([Supplementary Table 1](#SD1){ref-type="supplementary-material"}). Each of the 112 TSG was knocked down with siRNA either in the presence of AZD7762 (high or low dose) or dimethylsulfoxide (DMSO) solvent control. At a stringent cutoff (5 sigma below mean of non-silencing controls), 8 genes were identified for synthetic lethal interaction with AZD7762 (Figure [1A](#F1){ref-type="fig"}). The top four hits (*WEE1*, *CHEK1*, *CDC6* and *CDC73*) were TSGs with well-known functions related to cell cycle regulation. These included CHEK1 itself, a direct target of AZD7762, as is typical in chemogenetic screens \[[@R24]\]. WEE1, another checkpoint kinase known to complement CHEK1-mediated regulation of cell cycle, also displayed a strong synthetic lethal interaction with AZD7762 \[[@R11], [@R12], [@R25]\]. Comparing the AZD7762 screen to a similar chemo-genetic screen with the CHEK1 inhibitor Gö6976 \[[@R16]\], two of the hits with Gö6976, *BRCA2* and *RAD23B* also trended towards being synthetically lethal with AZD7762. Two other hits with Gö6976, *HDAC1* and *HDAC6* were tested but not found to be synthetically lethal with AZD7762. Likely the differences in the AZD7762 and Gö6976 screens is related to inhibition of kinases other than CHEK1. Gö6976 is known to inhibit JAK2 \[[@R26]\], which was been reported to be synergistic with HDAC inhibition \[[@R27]\].
::: {#F1 .fig}
###### Chemogenetic profiling identifies synthetic lethal interactors with AZD7762
**A.** Rank-ordered results of 112 TSG screened for synthetic lethal interaction with AZD7762, hit genes annotated to DNA repair highlighted in red, hit genes annotated to cell cycle highlighted in green. **B.**, **C.** Incidence of *RAD17* mutation and homozygous deletion in various cohorts (MSKCC - Memorial Sloan Kettering Cancer Center, Mich - University of Michigan, TCGA - The Cancer Genome Atlas, UHK - University of Hong Kong). **D.** Distribution of all missense (green) and truncating (red) *RAD17* mutations reported in TCGA, purple indicates both missense and truncating mutations have been found at a particular nucleotide. Height of bar represents number of mutations observed at a given position. **E.** Synthetic Genetic Array performed in *S. cerevisiae* with *Δrad17*, *Δdun1* and *Δrad17Δdun1* double knockout, each point represents one experimental replicate, \*\*\* indicates ANOVA *p* \< 0.0001. **F.** Spot dilution assay performed in *S. cerevisiae* with *Δrad17*, *Δdun1* and *Δrad17Δdun1* double knockout. **G.** Cell lines from Project Achilles with *CHEK1/2* mutation or homozygous deletion are more sensitive to knockdown of either *RAD17* or *WEE1* relative to cell lines with wild type *CHEK1/2*, error bars represent +/− SEM, *p* values for *t*-test as indicated.
The next four hits with AZD7762 (*BLM*, *RFC1*, *RAD17* and *FZR1*) were all novel interactions involving TSGs functioning in the DNA damage response. Bloom syndrome protein (BLM), a RecQ family DNA helicase, is phosphorylated by both CHEK1 and CHEK2 and is known to participate in HR, telomere maintenance, and DNA replication \[[@R28], [@R29]\]. Germline mutation in *BLM* is the cause of Bloom syndrome, a rare disease associated with cancer predisposition \[[@R28]\]. Fizzy-related protein homolog (FZR1) activates and regulates substrate specificity of the anaphase-promoting complex/cyclosome (APC/C), and by doing so is thought to regulate multiple cell cycle events including G1/G0 maintenance, initiation of DNA replication and DNA damage response \[[@R30]\]. Replication factor C subunit 1 (RFC1) is a DNA-dependent ATPase known to be involved in clamp loading during DNA replication and repair \[[@R31]\]. First characterized in the fission yeast *Schizosaccheromyces pombe* \[[@R32]\], *RAD17* contains DNA binding motifs similar to *RFC1* and is known to be an important sensor of DNA damage and essential for ATR-mediated cell-cycle arrest in response to DNA damage \[[@R33]\]. RAD17 localizes to areas of DNA damage and recruits the MRN complex to Double Strand Breaks (DSB), promoting HR \[[@R34]\]. In the context of human cancer, it has been shown that depletion of RAD17 sensitizes cancer cell lines to DNA damaging chemotherapy \[[@R35]\], and that down-regulation of RAD17 by certain gain-of-function *TP53* mutations leads to the accumulation of DNA damage \[[@R36]\].
Loss-of-function of the tumor suppressor *RAD17* is frequent in human cancers {#s2_2}
Next, we investigated the incidence of mutation or homozygous deletion in human tumors for each of our hits. Query of the cBioPortal for Cancer Genomics \[[@R37], [@R38]\] indicated that *RAD17* is the most frequently altered of the four TSGs with a pan-cancer incidence of 1.9% ([Supplementary Figure 1](#SD1){ref-type="supplementary-material"}). *RAD17* is frequently deleted in adenoid cystic carcinoma (13.3%) and prostate adenocarcinoma (13.1%, 5.9%) and frequently mutated in pancreatic adenocarcinoma (7.0%) and stomach adenocarcinoma (4.5%) (Figure [1B](#F1){ref-type="fig"} and [1C](#F1){ref-type="fig"}). Mutations in *RAD17* are spread relatively evenly throughout the 681 amino-acid length of the gene, and 10 of the 58 observed mutations (17.2%) are frameshift, nonsense, or splicing mutations (Figure [1D](#F1){ref-type="fig"}). This diffuse pattern and frequency of truncating mutations are consistent with *RAD17* functioning as a TSG \[[@R39]\]. A recent pan-cancer analysis of all tumor exomes currently included in The Cancer Genome Atlas (TCGA)\[[@R40]\] found somatic mutations occur in *RAD17* at an overall rate of 1.0% and homozygous deletions at a rate of 0.9%, which, given an annual incidence of approximately 1.7 million new cancer cases in the United States \[[@R41]\], equates to over 31,500 new patients per year with tumors involving *RAD17* loss-of-function.
*CHEK1/2* - *RAD17* interaction is conserved across species and cancer cell lines {#s2_3}
Given the demonstrated utility of cross-species modeling for prediction of chemogenetic interactions \[[@R42], [@R43]\], we sought to determine if the orthologous genes to *RAD17* and the checkpoint kinases had a synthetic-lethal relationship in the budding yeast *Saccharomyces cerevisiae.* Sequence alignment was performed to identify the following best matches: human *RAD17* with sc*RAD17*; human *CHEK1* with sc*CHK1*, and human *CHEK2* with sc*DUN1* ([Supplementary Table 2](#SD1){ref-type="supplementary-material"}) \[[@R44]\]. These yeast orthologs were tested in a Synthetic Genetic Array (SGA), in which the *rad17Δdun1Δ* double knockout had significantly smaller colonies relative to either single deletion (Figure [1E](#F1){ref-type="fig"}). Interestingly, the *rad17Δchek1Δ* interaction did not score as a hit in this in this assay. The *rad17Δdun1Δ* interaction was further tested in a yeast spot dilution assay. The double knockout of *rad17Δdun1Δ* showed less colony formation relative to either *rad17Δ* or *dun1Δ* single deletion or the wild type stain (Figure [1F](#F1){ref-type="fig"}), confirming that *rad17Δ* and *dun1Δ* have a synthetic lethal relationship.
To determine if the interaction between *CHEK1/2* and *RAD17* was also present across a diverse set of cancer cell lines we analyzed data generated from Project Achilles, a cancer cell-line based functional genomic screen in which over 11,000 genes were knocked down with shRNA in 102 cell lines \[[@R45]\]. Since the majority of these 102 cells lines were profiled for mutations at panel of 1651 genes as part of the Cancer Cell Line Encyclopedia (CCLE) \[[@R46]\] we were able to identify 10 of the 102 as having either mutation or homozygous deletion of *CHEK1* or *CHEK2*. Of note, none of the cell lines had *RAD17* homozygous deletion, and *RAD17* mutation status was not assessed in this dataset. We found that cell lines with disruption of *CHEK1/2* had significantly greater sensitivity to shRNA mediated knockdown of *RAD17* relative to cell lines without *CHEK1/2* alteration (normalized viability 0.73 vs. 1.0, *p* \< 0.0003, Figure [1G](#F1){ref-type="fig"}). Two of the three cell lines most sensitive to *RAD17* knockdown were GP2D and LS411N, both colon cancer cell lines harboring *CHEK1* mutation. The other top hit was Colo704, an ovarian cancer cell line with homozygous deletion of *CHEK2* ([Supplementary Table 3](#SD1){ref-type="supplementary-material"}). *CHEK1/2* altered cell lines were also more sensitive to knockdown of *WEE1* (normalized viability 0.55 vs. 0.96, *p* \< 3.0 x10^−8^, Figure [1G](#F1){ref-type="fig"}). These data in conjunction with the yeast findings suggest that the interaction between *CHEK1/2* and *RAD17* is general to eukaryotic cells and not specific to a particular genetic background.
*RAD17* functionally interacts with multiple checkpoint kinases {#s2_4}
To further explore the relationship between *RAD17* and the checkpoint kinases, we created stable knockdown cell lines using lentiviral shRNA constructs targeting *RAD17* in HeLa cells, a human cancer cell line derived from a cervical adenocarcinoma, as well as LN428, a human cancer cell line derived from glioblastoma multiforme \[[@R47]\]. Both cell lines have inactive p53; HeLa by the effect of human papillomavirus (HPV) gene E6, and LN428 by somatic mutation. Effectiveness of gene knockdown was confirmed at the mRNA level by RT-qPCR, and at the protein level by both immunofluorescence and western blot ([Supplementary Figure 2](#SD1){ref-type="supplementary-material"}). The dual CHEK1/2 inhibitor AZD7762 (chemical structures shown in [Supplementary Figure 3](#SD1){ref-type="supplementary-material"}) was significantly more toxic to HeLa cells with *RAD17* knockdown relative to non-targeting controls (F-test *p* \< 0.0001, Figure [2A](#F2){ref-type="fig"} and [2C](#F2){ref-type="fig"}, Table [1](#T1){ref-type="table"}). AZD7762 was also significantly more toxic to *RAD17* knockdowns in LN428 cells (F-test *p* \< 0.0001, Figure [2D](#F2){ref-type="fig"}, [Supplementary Figure 4A](#SD1){ref-type="supplementary-material"}). Additionally we performed 2way ANOVA to assess what portion of the difference in viability was due to *RAD17* knockdown. In HeLa cells 19.5% of the variation was from *RAD17* effect (*p* \< 0.0001) and 13.7% from interaction between RAD17 effect and dose of drug (*p* \< 0.0001), for LN428 these percentages were 38.6% and 4.3% respectively (*p* \< 0.0001, [Supplemental Table 4](#SD1){ref-type="supplementary-material"}). The WEE1 inhibitor MK-1775 was significantly more toxic to *RAD17* knockdowns relative to non-silencing control in clonogenic assays in both HeLa and LN428 cells (F-test and ANOVA *p* \< 0.0001, Figure [2B](#F2){ref-type="fig"}-[2E](#F2){ref-type="fig"}, [Supplementary Figure 4b](#SD1){ref-type="supplementary-material"}).
::: {#F2 .fig}
###### *RAD17* knockdown is synthetically lethal with CHEK1, CHEK2, and WEE1 inhibition
**A., B.** HeLa cells with either stable knockdown (HeLa/RAD17-KD) or non-targeting shRNA (HeLa/SCR) were treated with either AZD7762 or MK-1775 in clonogenic assay, error bars represent +/− SD, \* indicates *p* \< 0.05 for *t*-test comparing SCR and RAD17-KD at that dose. **C.** Images of clonogenic plates from HeLa cells treated with either AZD7762 or MK-1775. **D., E.** IC~50~ values determined from non-linear fit of data from clonogenic experiments for AZD7762 and MK-1775 in HeLa and LN428 cells, error bars represent +/− 95% CI, \*\* indicates *p* \< 0.0001 for extra sum-of-squares F test to comparing each RAD17-KD to SCR.
::: {#T1 .table-wrap}
###### IC50 values from clonogenic assays
IC50 (nM) ratio relative to SCR
------------------ ------- ----------- ----------------------- ------ ----- -----
AZD7762 HeLa 180 50 50 3.5 3.5
MK-1775 HeLa 280 110 120 2.6 2.3
MK-8776 HeLa 3700 1900 1800 2.0 2.1
LY2603618 HeLa 5800 1100 710 5.1 8.2
BML-277 HeLa 4200 3000 3200 1.4 1.3
AZD-MK1775 combo HeLa 41 14 11 2.9 3.8
AZD7762 LN428 450 65 230 6.9 1.9
MK-1775 LN428 420 170 86 2.5 4.9
AZD-MK1775 combo LN428 97 67 31 1.5 3.1
Several structurally distinct checkpoint kinase inhibitors were tested to determine if the observed synthetic lethality was an on-target effect. *RAD17* knockdown sensitized HeLa cells to the CHEK1 selective inhibitors MK-8776 and LY2603618 ([Supplementary Figure 4c and d](#SD1){ref-type="supplementary-material"}, Table [1](#T1){ref-type="table"}). The CHEK2 selective inhibitor BML-277 also showed greater toxicity to HeLa cells with *RAD17* knockdown, although the magnitude of the synthetic lethal effect was less than that seen with CHEK1 inhibitors ([Supplementary Figure 4e and f](#SD1){ref-type="supplementary-material"}). *CHEK1*, *CHEK2*, and *WEE1* were also knocked down transiently using siRNA. The cytotoxic effect of *WEE1* knockdown was significantly greater in LN428/RAD17-KD cells than controls (26.8% vs. 60.2% normalized viability, *p* = 0.017, [Supplementary Figure 4g](#SD1){ref-type="supplementary-material"}). As single knockdowns, both *CHEK1* and *CHEK2* had a mild effect on viability, trending towards *RAD17* knockdowns being more sensitive. LN428/RAD17-KD cells were significantly more sensitive to simultaneous knockdown of *CHEK1* and *CHEK2* than LN428/SCR control (50.9% vs. 89.6% normalized viability, *p* = 0.011, [Supplementary Figure 4g](#SD1){ref-type="supplementary-material"}). Overall, these results demonstrate that *RAD17* has a synthetic lethal relationship with each of the checkpoint kinases *CHEK1*, *CHEK2*, and *WEE1*.
Combined CHEK1/2 and WEE1 inhibition causes synergistic toxicity in the setting of *RAD17* loss-of-function {#s2_5}
Given prior reports of synergy between CHEK1 and WEE1 inhibitors in lymphoma \[[@R48]\], leukemia \[[@R11]\], and solid tumor \[[@R12], [@R49]\] cell lines, we suspected that simultaneous inhibition of CHEK1 and WEE1 might further magnify the synthetic lethal effect with *RAD17* knockdown. Indeed, the combination of AZD7762 with an equal dose of MK-1775 was more toxic to *RAD17* knockdown cells than non-silencing controls in both HeLa (F-test and ANOVA *p* \< 0.0001, Figure [3a](#F3){ref-type="fig"}) and LN428 cells (F-test and ANOVA *p* \< 0.0001, Figure [3B](#F3){ref-type="fig"}). The absolute IC~50~ concentration was approximately four-fold lower for the combination relative to the IC~50~ concentrations of either AZD7762 or MK-1775 alone (Table [1](#T1){ref-type="table"}). However, the magnitude of the synthetic lethal effect, that is the ratio of wild type IC~50~ to *RAD17* knockdown IC~50~, was essentially the same for the combination relative to either single molecule. The combination of AZD7762 with MK-1775 was synergistic in both *RAD17* knockdown cell lines but not in non-silencing controls for all doses tested (Figure [3C](#F3){ref-type="fig"}). Additionally we tested the ATR inhibitor VX-970, which is currently in Phase I/II clinical testing in combination with topotecan \[[@R50]\]. *RAD17* knockdown sensitized both HeLa and LN428 cells to VX-970, reducing IC50 by approximately 3 fold (F-test and ANOVA *p* \< 0.005, [Supplemental Figure 5a and b](#SD1){ref-type="supplementary-material"}). The combination of AZD7762 with VX-970 was also more potent in HeLa cells with *RAD17* knockdown (F-test and ANOVA *p* \< 0.0001, [Supplemental Figure 5c](#SD1){ref-type="supplementary-material"}). Interestingly, the combination of AZD7762 with VX-970 was synergistic in both HeLa cells with *RAD17* knockdown as well as non-targeting controls ([Supplementary Figure 5d](#SD1){ref-type="supplementary-material"}).
::: {#F3 .fig}
###### Dual inhibition with AZD7762 and MK-1775 results in synergistic toxicity in *RAD17* knockdown cell lines
**A.**, **B.** Clonogenic assay combining both AZD7762 and MK-1775 in HeLa cells and LN428 cells error bars represent +/− SD, \* indicates *p* \< 0.05 for *t*-test comparing SCR and RAD17-KD at that dose. **C.** Log Combinatorial Index as determined by method of Chou & Talalay from HeLa clonogenic experiment, values less than zero indicate synergy, values above zero indicate antagonism. **D.** IC~50~ values determined from non-linear fit of data from clonogenic experiments, error bars represent +/− 95% CI, \*\* indicates *p* \< 0.0001 for extra sum-of-squares F test to comparing each RAD17-KD to SCR.
Given that evidence of forced mitotic entry has been observed as soon as 8 hours after treatment with WEE1 inhibitors \[[@R13]\], we suspected that transient CHEK1/2-WEE1 inhibition would be sufficient to kill *RAD17* knockdown cells. A pulse-dose exposure of AZD7762 with MK-1775 for 72 hours was only slightly less toxic than continuous exposure and again demonstrated a synthetic lethal effect with *RAD17* knockdown (Figure [3D](#F3){ref-type="fig"}). This suggests that intermittent dosing of CHEK1 or WEE1 inhibitors could be a viable therapeutic strategy in certain susceptible tumors.
*RAD17* synthetic lethal effect with checkpoint kinases is associated with increase in γH2AX accumulation {#s2_6}
*RAD17* is known to participate in cell cycle regulation by activating the S-phase checkpoint \[[@R51]\] in addition to its role in DNA damage repair \[[@R34]\]. We sought to determine which function was mediating the observed synthetic lethal effect with checkpoint kinase inhibition using a high-throughput immunofluorescence assay to measure phosphorylation of histone H2AX at Ser139 (γH2AX), an established marker of DNA damage \[[@R52]\]. It has previously been reported that inhibition of CHEK1 or WEE1 causes accumulation of γH2AX \[[@R2], [@R7], [@R12]\]. We found that chemical inhibition of CHEK1/2 with AZD7762 resulted in a dose dependent increase in γH2AX, with significantly greater induction of γH2AX seen in *RAD17* knockdown samples relative to non-silencing controls in both HeLa (*p* \< 0.05, Figure [4A](#F4){ref-type="fig"}) and LN428 cell lines (*p* \< 0.05, [Supplementary Figure 6a](#SD1){ref-type="supplementary-material"}). Similarly, WEE1 inhibition with MK-1775 also resulted in a dose dependent increase in γH2AX with significantly greater induction of γH2AX seen in *RAD17* knockdown samples in both HeLa and LN428 cell lines (*p* \< 0.05, Figure [4A](#F4){ref-type="fig"} and [Supplementary Figure 6a](#SD1){ref-type="supplementary-material"}). Similar to its effect in clonogenic assay, the combination of both AZD7762 and MK-1775 was more potent than either single agent in terms of induction of γH2AX. The increase in γH2AX seen with combined treatment was greater in the setting of *RAD17* knockdown (*p* \< 0.05, Figure [4A](#F4){ref-type="fig"} and [Supplementary Figure 6a](#SD1){ref-type="supplementary-material"}). The CHEK1 selective inhibitors MK-8776, CHIR-124, and LY2603618 also increased γH2AX accumulation to a greater degree in cells with *RAD17* knockdown (*p* \< 0.05, Figure [4B](#F4){ref-type="fig"}). The CHEK2 selective inhibitor BML-277 induced less γH2AX than the CHEK1 inhibitors, but more γH2AX was observed in *RAD17* knockdown cells relative to non-silencing controls (*p* \< 0.05, Figure [4B](#F4){ref-type="fig"}). Transient knockdown of *CHEK1*, *CHEK2*, and *WEE1* produced results similar to chemical inhibitors. Knockdown of either *CHEK1* or *WEE1* led to significantly more γH2AX accumulation in *RAD17* knockdown cells (*p* \< 0.05, Figure [4C](#F4){ref-type="fig"}), however this effect was not seen with knockdown of *CHEK2*. These results confirm that the increase in γH2AX accumulation seen with AZD7762 and MK-1775 is due to the on-target effect of inhibition of CHEK1/2 or WEE1, respectively, and suggest the effect of AZD7762 is mediated primarily through inhibition of CHEK1.
::: {#F4 .fig}
###### *RAD17* knockdown exacerbates accumulation of DNA damage following checkpoint kinase inhibition
**A.** Percentage of HeLa cells staining positive for γH2AX by immunofluorescence when treated with AZD7762, MK-1775, or the combination of both, error bars represent +/− SD, \* indicates *p* \< 0.05 for *t*-test comparing each RAD17-KD to SCR at that dose. **B.** Similar experiment to **A.** except with MK-8776, BML-277, CHIR-124, and LY2603618. **C.** Percentage of LN428 cells staining positive for H2AX by immunofluorescence when treated with non-silencing siRNA (siNS) or siRNA targeting *CHEK1*, *CHEK2*, or *WEE1*, error bars represent +/− SD, \* indicates *p* \< 0.05 for *t*-test comparing each RAD17-KD to SCR at that dose. Scatter plots showing gating for H2AX positive cells for LN428/SCR **D.**, LN428/RAD17-KD1 **E.**, or LN428/RAD17-KD2 **F.** for samples treated with combination of AZD7762 and MK-1775 both at 200 nM. **G.** Bar graph showing average γH2AX intensity by FACS for population of HeLa or LN428 cells treated at given doses, error bars represent +/− 95% CI, \* indicates *p* \< 0.05 for *t*-test comparing each RAD17-KD to SCR at that dose.
DNA damage induction in response to checkpoint kinase inhibition was also assessed in a Fluorescence Activated Cell Sorting (FACS) assay. The addition of the combination of AZD7762 and MK-1775 resulted in greater accumulation of γH2AX in *RAD17* knockdown cells, consistent with the results of the immunofluorescence assay (Figure [4D](#F4){ref-type="fig"}-[4G](#F4){ref-type="fig"}, [Supplementary Figure 6b-d](#SD1){ref-type="supplementary-material"}). The observation that loss-of-function of *RAD17* exacerbates the γH2AX accumulation seen with CHEK1 or WEE1 inhibition suggests that RAD17\'s role in DNA repair is at least partially independent of the checkpoint kinases.
To evaluate the effect of *RAD17* knockdown on cell cycle progression we performed FACS. In contrast to its effect on γH2AX accumulation, *RAD17* knockdown had minimal effect on progression through the G1-S or G2/M checkpoints. In LN428 and HeLa cells a dose-dependent accumulation of cells in the S or G2 phase was seen with AZD7762, MK-1775, and the combination of AZD7762 and MK-1775 (Figure [5A](#F5){ref-type="fig"}-[5C](#F5){ref-type="fig"}, [Supplementary Figure 6e-g](#SD1){ref-type="supplementary-material"}). However, the accumulation of cells in S or G2 phase was not increased by the knockdown of *RAD17* in the absence of checkpoint kinase inhibition (Figure [5D](#F5){ref-type="fig"}), or at doses near the IC~50~ concentration for these compounds (Figure [5E](#F5){ref-type="fig"}). At a dose of 200 nM, more than three times the IC~50~ for LN428/RAD17-KD1 cells or six times the IC~50~ for LN428/RAD17-KD2 cells, there was a greater percentage of cells in S or G2 phase in the *RAD17* knockdown cell lines relative to non-silencing control (Figure [5F](#F5){ref-type="fig"}). Similar results were seen in HeLa cells ([Supplementary Figure 6h-j](#SD1){ref-type="supplementary-material"}). These data suggest that in the setting of *RAD17* knockdown cells continue to cycle normally. The fact that cytotoxic doses of AZD7762 and MK-1775 do not cause accumulation of cells in S or G2 phase with or without *RAD17* indicates that loss of cell cycle regulation is not the primary mechanism causing cell death. This result is consistent with prior reports that WEE1 or CHEK1 inhibition can ultimately cause cell death by mitotic catastrophe \[[@R53], [@R54]\].
::: {#F5 .fig}
###### *RAD17* knockdown has minimal impact cell cycle regulation
**A**.-**C**. Bar graphs summarizing percentage of LN428 cells in either S or G2 phase when treated with either AZD7762, MK-1775, or both in combination at indicated doses. **D**.-**E**. Overlaid histograms of events by DNA content showing cell cycle distributions for LN428 cells treated with DMSO, AZD7762 and MK-1775 at 60 nM, or AZD7762 and MK-1775 at 200 nM.
Interaction of *RAD17* and checkpoint kinases in primary human tumor samples {#s2_7}
It has been demonstrated that co-disruption of synthetic lethal partners in a tumor is associated with better patient survival \[[@R55]\], presumably because these tumors are less robust to perturbations and thus more vulnerable to therapy. To assess whether there is evidence of interaction between *RAD17* and the checkpoint kinases in primary human tumors, we examined somatic mutation, copy number variation, and mRNA expression data from \~8000 biopsy specimens spanning multiple cancer types in TCGA. Tumors with *RAD17* homozygous deletion or mutation had significantly increased expression of both *CHEK1* and *CHEK2* relative to tumors without *RAD17* alteration (Mann-Whitney U test *p* = 1.0e-7 and 0.0017, respectively), with *WEE1* there was a non-significant trend toward increased expression (Figure [6A-6C](#F6){ref-type="fig"}). Given the overlapping roles of *RAD17* and the checkpoint kinases in repairing DNA damage we suspected that the observed overexpression of *CHEK1*, *CHEK2* and *WEE1* was a compensatory mechanism to prevent excessive DNA damage. To evaluate if this overexpression of checkpoint kinases is potentially clinically relevant, we next looked for an association with patient survival. At an overexpression cutoff of two sigma, the majority of TCGA patients had none of the three checkpoint kinases (*CHEK1*, *CHEK2* and *WEE1*) overexpressed. These patients had the best overall survival, and as the number of overexpressed checkpoint kinases increased, overall survival became progressively worse (Figure [6D](#F6){ref-type="fig"}). The number of checkpoint kinases overexpressed was significantly associated with survival as assessed by a Cox proportional hazards model (*p* \< 0.003 without covariates, *p* \< 0.008 with covariates age, stage, tumor type). The proportion of patients alive at five years ranged from 62% for those with no checkpoint kinase overexpression to 0% for the 24 patients overexpressing all three checkpoint kinases (Figure [6E](#F6){ref-type="fig"}). These results suggest that the synthetic lethal effect observed between *RAD17* and the checkpoint kinases *in vitro* may be functionally relevant *in vivo.*
::: {#F6 .fig}
###### Synthetic lethal interactions with checkpoint kinases in human tumor samples
**A**.-**C**.*CHEK1*, *CHEK2*, and *WEE1* are all over expressed in tumors with either homozygous deletion or mutation of *RAD17*. **D.** Kaplan-Meier plot of patients from TCGA stratified by overexpression of *CHEK1*, *CHEK2*, or *WEE1*. Red curve - patients with overexpression of none of *CHEK1*, *CHEK2*, or *WEE1*; blue curve - patients with overexpression of one of the three; green curve - overexpression of two of three; purple curve overexpression of all three. **E.** Proportion of patients alive at five years for same populations, error bars represent +/− 95% CI.
Small molecule inhibitors of either CHEK1 or WEE1 remain in clinical development, both as single agents and in combination with either DNA damaging or anti-metabolite chemotherapy \[[@R2], [@R4], [@R7]\]. Currently, these early phase trials are being performed without biomarker stratification due in part to a poor understanding of the molecular predictors of response to these therapies. Prior *in vitro* testing of CHEK1 inhibitors has found that only 10-15% of cancer cell lines are sensitive to isolated CHEK1 inhibition \[[@R56]\]. Assuming these cell lines are a reasonable surrogate for human tumors, it suggests that for each patient with a tumor sensitive to checkpoint kinase inhibition, as many as nine patients with resistant tumors will be treated with ineffective therapy. To address this need we identified several TSG involved in either DNA repair or cell cycle regulation to be synthetically lethal with the checkpoint kinase inhibitor AZD7762. Focusing on *RAD17*, we show in clonogenic assay that shRNA mediated knockdown of *RAD17* increases the sensitivity of either HeLa or LN428 cancer cells to both chemical inhibition or siRNA mediated knockdown of the checkpoint kinases *CHEK1*, *CHEK2* and *WEE1*. Evidence of the interaction between *RAD17* and *CHEK1/2* was also seen in a functional genomic screen involving a panel of over 100 cell lines and in the budding yeast *S. cerevisiae*.
The presence of a strong conserved genetic interaction between *RAD17* and the checkpoint kinases in human and yeast species separated by up to a billion years of evolution \[[@R22]\], suggests that this functional relationship is not just active in some conditions or cell states but may be fundamental for eukaryotic life. This supposition is supported by the fact that (excluding hyper-mutated tumors) there are no occurrences of tumors with mutations in both *RAD17* and either *CHEK1*, *CHEK2* and *WEE1* across all cancer types in TCGA. We suspect that the observed overexpression of *CHEK1*, *CHEK2* and *WEE1* in tumors with *RAD17* deletion or mutation is a compensatory response to impaired DNA damage repair. Tumors that overexpress checkpoint kinases should have greater fitness than those without compensatory overexpression, resulting in worse clinical outcomes for these patients, as we observed.
Synthetic lethal interactions are predicted to occur between genes that participate in independent, but complementary pathways, such as base excision repair and HR for the synthetic lethal pair *PARP1* and *BRCA1* \[[@R22]\]. Given that *CHEK1*, *CHEK2,* and *WEE1* play a role in the repair of DNA damage in addition to regulating cell cycle checkpoints \[[@R2], [@R18], [@R57]\], we suspected that the interaction with *RAD17* would involve one or both of these two functions. Our results suggest that it the role of *RAD17* in DNA damage repair, likely the recruitment of the MRN complex to DSB, which becomes essential in the setting of checkpoint kinase inhibition. This conclusion is supported by prior data in HeLa cells identifying that claspin-dependent activation of CHEK1 is independent of *RAD17* \[[@R58]\].
Although the compound AZD7762, which inhibits both CHEK1 and CHEK2, is no longer in clinical development due to cardiac toxicity \[[@R9]\], other selective inhibitors of CHEK1 including MK-8776 remain in clinical development. It is unknown if the cardiac issues seen with AZD7762 relate to dual CHEK1/2 inhibition or an off-target effect; regardless, our data on the selective CHEK1 inhibitors MK-8776, LY2603618, and CHIR-124 suggest that CHEK1 inhibition is sufficient to achieve a synthetic lethal interaction with *RAD17* loss-of-function. The selective CHEK1 inhibitors were not tried in combination with WEE1 inhibition in this study, but given a prior report of synergy between MK-8776 and MK-1775 in the majority of a set of 39 cancer cell lines \[[@R12]\], it is likely that a CHEK1 selective inhibitor would perform similarly to AZD7762 when combined with MK-1775 in the setting of *RAD17* loss-of-function. The combination of CHEK1 inhibitor and WEE1 inhibitor shows particular promise in *RAD17* mutant or deleted tumors, as the IC~50~ of these drugs in combination is four-fold lower than that of each drug individually. The fact that only a pulse-dose of CHEK1 and WEE1 inhibition was needed to achieve a synthetic lethal effect in *RAD17* knockdown cells suggests the possibility that this combination could be used as a long term maintenance therapy, free of traditional cytotoxic chemotherapy.
MATERIALS AND METHODS {#s4}
Chemo-genetic screen {#s4_1}
A dose-response curve for AZD7762 in HeLa cells was created prior to screening. HeLa cells were seeded at density of 500 cells per well in 384 well plates, after 72 hours of drug exposure viability was measured using the Cell Titer Glow (Promega) viability regent. Prism v6.05 (GraphPad Software) was used to fit non-linear regression to create a dose-response curve which determined IC~20~ (0.22 μM) and IC~40~ (0.4 μM) doses. For the chemo-genetic screen cells were transfected by wet reverse method using Lipofectamine (Life Technologies). Each gene was targeted by four individual siRNA constructs pooled in the same well; three replicates were performed on separate plates for each dose. Correlation of replicates was 0.97 indicating excellent reproducibility ([Figure S1B-D](#SD1){ref-type="supplementary-material"}). Synthetic lethal interactions were scored by first normalizing for the viability effect of gene knockdown in the presence of only dimethyl-sulfoxide (DMSO) solvent, then comparing these normalized values for each gene to panel of non-silencing controls to determine Z-score. Since the Z-scores for the IC~20~ and IC~40~ doses were highly correlated (r = 0.87, *p* \< 0.0001, [Figure S1A](#SD1){ref-type="supplementary-material"}) they were averaged to create a single value for each of the 112 genes screened.
cBioPortal analysis {#s4_2}
Data from all available cohorts on cBioPortal ([www.cbioportal.org](http://www.cbioportal.org)) excluding cell lines was last downloaded on 6/1/15.
Sequence alignment {#s4_3}
The online version of Clustal W, version 2.1 was used to perform sequence alignment.
Yeast spot dilution and synthetic genetic array assay {#s4_4}
Yeast mutant strains were constructed by the pinning robot ROTOR (Singer Instruments) using SGA technology \[[@R59]\]. Colony sizes were quantified and normalized using Colony Analyzer to assess viability \[[@R60]\]. For spot dilution assays, cells were grown to mid-log in rich media (YPAD). Aliquots of 10-fold serial dilutions were spotted on rich media (YPAD) and grown for 2 days at 30°C.
Project achilles analysis {#s4_5}
Raw shRNA viability data was downloaded from Cheung *et al*, 2011 \[[@R45]\]. Viability for each gene was determined by averaging the values of five independent constructs.
Generation of lentiviral knockdown cell lines {#s4_6}
The shuttle vectors for expression of shRNA targeting each gene were purchased from Sigma (St. Louis, MO). Lentiviruses were prepared in collaboration with the UPCI Lentiviral facility. Lentiviral particles were generated by co-transfection of 4 plasmids (the shuttle vector plus three packaging plasmids: pMD2.g (VSVG), pVSV-REV and PMDLg/pRRE) into 293-FT cells using FuGene 6 Transfection Reagent (Roche). 10,000 cells were seeded into a 6-well plate 24 hours before transduction. Cells were transduced for 18 hours at 32°C and then cultured for 8 hours at 37°C. Next, the cells were transduced a second time at 32°C for 18 hours with the lentiviruses containing the same shRNA, and then cultured for 24 hours at 37°C. Cells were selected by culturing in growth media with 1.0 μg/mL puromycin for two weeks to obtain stable knockdown cells. For each gene, five individual shRNAs targeting each gene were used to generate five independent knockdown cell lines. The cell lines with the highest level of knockdown were selected for future studies.
Determination of gene knockdown level (RT-qPCR) {#s4_7}
Gene expression (mRNA) was measured by quantitative reverse transcription-PCR (qRT-PCR) using an Applied Biosystems StepOnePlus system. Briefly, 80,000 cells were lysed and reverse transcribed using the Taqman Gene Expression Cells-to-CT kit (Applied Biosystems). Each sample was analyzed in duplicate using a Taqman Gene Expression Assay for human *RAD17* (Hs00607830\_m1) and normalized to the expression of human β-actin (Applied Biosystems). Expression (mRNA) was analyzed via the ΔΔCT method, results are reported as an average of two analyses +/− SE.
Determination of gene knockdown level (Immunofluorescence and western blot) {#s4_8}
Cells were seeded into clear bottom 384 well plates (Nunc), fixed with 4% formaldehyde, blocked with 2% bovine serum albumin in TBST, and stained with Hoechst and anti-RAD17 (Abnova) primary antibody followed by Alexa594 donkey anti-mouse secondary antibody. Plates were imaged with ImageXpress Micro automated epi-fluorescent microscope (Molecular Devices) and images were scored with MetaExpress analysis software (Molecular Devices). For western blot cells were lysed with RIPA buffer and prepared for SDS-PAGE using NuPAGE kit (Invitrogen). Same anti-RAD17 (Abnova) primary antibody was used as in immunofluorescence assays.
Clonogenic assays {#s4_9}
Cells were counted using Scepter automated cell counter (Millipore) and between 800-2000 cells were seeded per plate. Cells were treated with small molecule inhibitors or DMSO solvent control for 9 days (HeLa) or 10 days (LN428). Consistent with standard protocol a cut off of 50 cell was used as threshold to define a colony \[[@R61]\]. Canon Rebel T3i digital camera was used to create a digital image of each plate, colonies were then scored using a custom Matlab script calibrated against manually counted control plates for each cell line. Number of colonies per plates was normalized to number of colonies on plates treated only with DMSO solvent, each lentiviral modified cell line was normalized independently. IC~50~ concentrations were determined by performing four parameter non-linear regression using Prism v6.05 software. IC~50~ concentrations compared to each other using extra sum-of-squares F test. Pulse-dose experiments were performed by exchanging media to remove drugs after 72 hours of exposure with colony formation measured after an additional seven additional days of growth. The method of Chou and Talalay was used to measure synergistic effects of drug combination \[[@R62]\].
γH2AX immunofluorescence assay {#s4_10}
250-500 cells were seeded into clear bottom 384 well plates (Nunc) and treated with either siRNA, kinase inhibitors, or controls. After incubation with either siRNA or small molecule inhibitor for 48-72 hours cells were fixed with 4% formaldehyde, blocked with 2% bovine serum albumin in TBST, and stained with Hoechst and FITC conjugated anti- γ-H2AX antibody (Millipore). Plates were imaged with ImageXpress Micro automated epi-fluorescent microscope (Molecular Devices) and images were scored with MetaExpress analysis software (Molecular Devices). At baseline without any pharmacological or genetic intervention, there was a non-significant trend towards more cells scoring positive for γH2AX in RAD17-KD cell lines relative to non-silencing control.
FACS assay {#s4_11}
400,000 - 500,000 cells were plated in 10 cm dishes and allow to attach overnight before being treated with small molecules the next day. After 48 hrs of drug exposure cells were harvested by incubating with trypsin for 5 min. Trypsin was neutralized with serum containing media and then cells were pelleted and re-suspended in ice cold 70% ETOH and stored at −20 C. On day of FACS run cells were washed once with PBS and incubated with FITC conjugated anti- γ-H2AX antibody (Millipore) per manufacturer protocol. Cells were then suspended in DNA staining buffer (Sodium citrate 0.1%, Triton-X 100 0.3%, propridium iodide 0.1 mg/mL, ribonuclease A 0.2 mg/mL in distilled water) and run on FACS machine (B&D LSRII, BD Biosciences). FACS data was analyzed with FlowJo v10.0.8 (Tree Star, Inc). Cell cycle analysis was performed using the Watson (univariate) method with constraint of equal CV for 2N and 4N peaks \[[@R63]\]. At baseline, approximately 40% of cells were in S or G2 phase for both RAD17-KD and non-silencing cell lines in both the HeLa and LN428 background.
TCGA analysis {#s4_12}
Data for TCGA cohort were obtained from the Genome Data Analysis Center (GDAC) Firehose website, latest data were downloaded from the 4/2/15 standard data and analyses run.
SUPPLEMENTARY MATERIAL FIGURES AND TABLES {#s5}
We would like to thank Dr. James Gray for assistance with automated microscopy, Dr. Gordon Bean for assistance with clonogenic image scoring algorithm, Dr. Charles Gabbert for accommodation in Pittsburg, and Dr. Serah Choi for suggestions on assays.
**CONFLICTS OF INTEREST**
Dr. Sobol has received compensation as a scientific consultant for Trevigen, Inc. All other authors declare no conflict of interest.
JPS, RS, HvA, RWS and TI conceived of and designed the study. JPS, RS, JL, EJ, SMS, ABG, KL, VS, JLZ, KK, DP and HY performed experiments. AMG and JPS performed statistical analyses of TCGA and Project Achilles data. JPS, RS, EJ, HvA, RWS and TI analyzed data. JPS, RS, HvA, RWS, and TI wrote the paper.
Research reported in this publication was supported by grants from the National Institute of Environmental Health Sciences (NIEHS) grant ES014811 to T.I. and the National Institute of Health (NIH) \[CA148629 and GM087798\] to R.W.S. J.P.S. was funded in part by grant(s) from the Marsha Rivkin Center for Ovarian Cancer Research and a Conquer Cancer Foundation of ASCO Young Investigator Award. R. Srivas is a Damon Runyon Fellow supported by the Damon Runyon Cancer Research Foundation (DRG-2187-14). Support for the UPCI Lentiviral (Vector Core) Facility was provided in part by the Cancer Center Support Grant from the National Institutes of Health \[P30CA047904\].
|
package com.github.restup.controller.settings;
import com.github.restup.controller.ExceptionHandler;
import com.github.restup.controller.content.negotiation.ContentNegotiator;
import com.github.restup.controller.interceptor.RequestInterceptor;
import com.github.restup.controller.request.parser.RequestParser;
import com.github.restup.registry.ResourceRegistry;
public class BasicControllerSettings implements ControllerSettings {
private final ResourceRegistry registry;
private final ContentNegotiator contentNegotiator;
private final RequestInterceptor requestInterceptor;
private final RequestParser requestParser;
private final ExceptionHandler exceptionHandler;
private final String defaultMediaType;
private final String mediaTypeParam;
protected BasicControllerSettings(ResourceRegistry registry, ContentNegotiator contentNegotiator,
RequestInterceptor requestInterceptor, RequestParser requestParsers,
ExceptionHandler exceptionHandler, String defaultMediaType, String mediaTypeParam) {
super();
this.registry = registry;
this.contentNegotiator = contentNegotiator;
this.requestInterceptor = requestInterceptor;
requestParser = requestParsers;
this.exceptionHandler = exceptionHandler;
this.defaultMediaType = defaultMediaType;
this.mediaTypeParam = mediaTypeParam;
}
@Override
public String getDefaultMediaType() {
return defaultMediaType;
}
@Override
public String getMediaTypeParam() {
return mediaTypeParam;
}
@Override
public ResourceRegistry getRegistry() {
return registry;
}
@Override
public ContentNegotiator getContentNegotiator() {
return contentNegotiator;
}
@Override
public RequestInterceptor getRequestInterceptor() {
return requestInterceptor;
}
@Override
public RequestParser getRequestParser() {
return requestParser;
}
@Override
public ExceptionHandler getExceptionHandler() {
return exceptionHandler;
}
}
|
Position adjustment device, rotating machine provided with same, and position adjustment method
ABSTRACT
A position adjustment device is provided with an eccentric pin and a push rod. The eccentric pin has a rotating shaft part, and an eccentric shaft part inserted into an end in a circumferential direction of a lower-half inside member. The push rod is inserted into the lower-half inside member from an end surface in the circumferential direction of the lower-half inside member, the push rod being able to come into contact with the eccentric shaft part within the lower-half inside member. The rotating shaft part has a columnar shape with a rotational axis line. The eccentric shaft part is formed with: a side peripheral surface that comes into contact with the inner peripheral surface of an eccentric shaft hole in the lower-half inside member into which the eccentric shaft part is inserted, and a rod contact surface that comes into contact with the push rod.
TECHNICAL FIELD
The present invention relates to a position adjustment device that adjusts the position in the vertical direction of a lower-half inside member that forms the lower half of a ring-shaped inside ring disposed on the inner peripheral side of a lower-half outside member, relative tothe lower-half outside member that forms the lower half of a cylindrical outside cylinder, a rotating machine provided with the same, and a position adjustment method.
This application claims priority based on Japanese Patent Application No. 2014-12768 filed in Japan on Jan. 27, 2014, of which the contents are incorporated herein by reference.
BACKGROUND ART
Rotating machines, such as steam turbines, gas turbines, compressors,and the like, include a rotor shaft, a cylindrical casing with the rotor shaft at the center thereof, and a ring-shaped vane ring disposed on the inner peripheral side of the casing with the rotor shaft at the center thereof. In such a rotating machine, the cylindrical casing and the ring-shaped vane ring are divided into a plurality of parts in thecircumferential direction, from the point of view of assembly, and the like.
Patent Document 1 below discloses a steam turbine that includes the rotor shaft, the casing, and the vane ring. In this steam turbine, the cylindrical casing is configured from an upper-half casing and a lower-half casing, and the vane ring is configured from an upper-halfvane ring and a lower-half vane ring. This steam turbine further includes a support fitting for adjusting the position of the lower-halfvane ring relative to the lower-half casing.
The support fitting includes a columnar insert section, and a columnarprojecting section that is eccentric to the insert section. At each end portion of the lower-half vane ring in the circumferential direction a hole is formed sunk from the outer peripheral side towards the inner peripheral side, and at each end portion of the lower-half casing in thecircumferential direction a notch that is depressed from the inner peripheral side towards the outer peripheral side is formed at a position corresponding to the hole of the lower-half vane ring. Thecolumnar insert section is inserted into the hole of the lower-half vanering so that it can rotate about the central axis thereof as the center,and the columnar projecting section is disposed in the notch of thelower-half casing.
When the support fitting is rotated about the central axis of the projecting section as the center, the insert section that is eccentric to the projecting section revolves about the central axis of the projecting section as the center. Therefore, when the support fitting is rotated about the central axis of the projecting section as the center,the lower-half vane ring into which the insert section of the support fitting is inserted moves relative to the lower-half casing in a direction perpendicular to the central axis of the projecting section.
With the technology disclosed in Patent Document 1, when the support fitting is rotated about the central axis of the projecting section asthe center, as described above, the lower-half vane ring moves relative to the lower-half casing, and the position of the lower-half vane ring is adjusted relative to the lower-half casing.
CITATION LIST Patent Document
Patent Document 1: Japanese Unexamined Patent Application Publication No. S63-170505A
SUMMARY OF INVENTION Technical Problem
With the technology disclosed in Patent Document 1, a tool for rotating the support fitting is necessary. The tool could be, for example, a hexagonal wrench. In this case, a hexagonal wrench hole that is depressed towards the insert section is formed on the end surface of the columnar projecting section, the end of the hexagonal wrench is inserted into the hexagonal wrench hole, the hexagonal wrench is manipulated, andthe support fitting is rotated. Therefore, with the technology disclose din Patent Document 1, it is necessary to increase the dimension in the radial direction of the notch of the lower-half casing in which the projecting section of the support fitting is disposed, to provide space to install the tool in the projecting section of the support fitting.Therefore, if this support fitting is adopted, it is necessary to increase the outer diameter of the casing that forms the outsidecylinder, in order to provide space for the tool. In other words, withthe technology disclosed in Patent Document 1, there is the problem thatthe size of the outside cylinder is increased.
The present invention provides a position adjustment device that adjusts the position in the vertical direction of a lower-half inside member that forms the lower half of an inside ring, relative to a lower-half outside member that forms the lower half of an outside cylinder, without increasing the size of the outside cylinder, and a rotating machine provided with the same.
Solution to Problem
According to a first aspect of the present invention, a positionadjustment device that adjusts, relative to a lower-half outside member that forms a lower half of a cylindrical outside cylinder with a rotor axis line as the center, a position in a vertical direction of a lower-half inside member that forms a lower half of a ring-shaped inside ring disposed on an inner peripheral side of the outside cylinder and having the rotor axis line as the center, includes: an eccentric pin that includes a rotating shaft part rotatably supported at an end in acircumferential direction of the lower-half outside member, and an eccentric shaft part inserted into an end in a circumferential direction of the lower-half inside member, the eccentric shaft part rotatingintegrally with rotation of the rotating shaft part; and
a push rod inserted into the lower-half inside member from an end surface in the circumferential direction of the lower-half inside member, the push rod being able to come into contact with the eccentric shaft part within the lower-half inside member. The rotating shaft part has a columnar shape with a rotational axis line that extends in a horizontal direction and in a direction perpendicular to the rotor axisline as the center. The eccentric shaft part is formed with a side peripheral surface that comes into contact with an inner peripheral surface of an eccentric shaft hole in the lower-half inside member into which the eccentric shaft part is inserted, and that has as the center an eccentric axis line that is parallel to the rotational axis line with an offset therebetween, and a rod contact surface that comes into contact with the push rod.
In the position adjustment device, the eccentric shaft part of theeccentric pin revolves about the rotational axis line as the center asthe eccentric pin is rotated. Therefore, it is possible to move thelower-half inside member, into which the eccentric shaft part is inserted, in the vertical direction perpendicular to the rotational axisline, relative to the lower-half outside member. Also, in the positionadjustment device, the eccentric pin is rotated about the rotational axis line by inserting the push rod into the lower-half inside member from an end surface in the circumferential direction of the lower-halfinside member, and pressing the rod contact surface of the eccentric pin with the push rod. Therefore, in the position adjustment device, it isnot necessary to engage the tip of a tool from the outside in the radial direction of the eccentric pin and manipulate this tool in order to rotate the eccentric pin about the rotational axis line.
Therefore, in the position adjustment device, it is not necessary to increase the outer diameter of the outside cylinder in order to provide tool space on the outside in the radial direction of the eccentric pin.
Here, in the position adjustment device, a female thread may be formed on an inner peripheral surface of a rod hole in the lower-half inside member into which the push rod is inserted. A male thread capable of mating with the female thread of the rod hole may be formed on an outer periphery of the push rod.
In this position adjustment device, by adjusting the amount that thepush rod is screwed in, the amount that the push rod is pressed in is changed, so the position of the lower-half inside member in the vertical direction can be adjusted relative to the lower-half outside member.Therefore, in the position adjustment device, the position of thelower-half inside member in the vertical direction relative to thelower-half outside member can be more simply, accurately, and finely adjusted than by adjusting the amount that simple rods without male threads formed on the outer periphery thereof are pressed in. Moreover,in this position adjustment device, when the relative positionadjustment operation is completed and the push rod is left as it is, the amount that the push rod is pressed in does not change as long as thepush rod is not rotated.
Also, in any of the position adjustment devices described above, thepush rod may include a first push rod that comes into contact with apart of the eccentric shaft part on one side of the eccentric axis line,and a second push rod that comes into contact with a part of theeccentric shaft part on the other side of the eccentric axis line.
In this position adjustment device, the eccentric pin can be rotated inthe rotational direction to the one side and to the other side about theeccentric axis line. In addition, if the male thread is formed on the outer periphery of the push rods, when the relative position adjustment operation is completed and the two push rods are left as they are, aslong as each push rod is not rotated, the amount that each push rod is pressed in does not change, so the eccentric pin does not rotate.Therefore, after the relative position adjustment operation is completed, it is not necessary to carry out a separate operation to stop the rotation of the eccentric pin, so the working time can be shortened.
Also, in any of the position adjustment devices described above, theeccentric shaft part may include a columnar part having the eccentric axis line as the center, and a notched columnar part formed in acolumnar shape with the eccentric axis line as the center and having thesame diameter as the columnar part, a part of the column of the notchedcolumnar part being notched. The side peripheral surface of theeccentric shaft part may be a side peripheral surface of the columnarpart and the notched columnar part, and the rod contact surface of theeccentric shaft part may be a surface formed by notching the column.
Also, in the position adjustment device in which the eccentric shaft part has the columnar part and the notched columnar part, the rod contact surface of the eccentric shaft part may be a curved surface thatis gently recessed towards the side peripheral surface from the notchedside of the column in a direction perpendicular to the rotational axisline.
In this position adjustment device, the contact characteristics betweenthe tip of the push rod and the rod contact surface can be maintained,even when the eccentric pin is rotated about the rotational axis line asthe center.
Also, any of the position adjustment devices described above may further include a support block which is disposed on the end of the lower-half outside member, and in which a rotating shaft hole is formed into whichthe rotating shaft part of the eccentric pin is inserted so that the rotating shaft part can rotate about the rotational axis line.
In this position adjustment device, the eccentric pin can be smoothly rotated about the rotational axis line.
Also, the position adjustment device that includes the support block may further include a fixing fitting that fixes the support block to thelower-half inside member.
According to a second aspect of the present invention, a rotating machine includes: any of the position adjustment devices described above; a casing as the outside cylinder; a vane ring as the inside ring;and a rotor disposed within the casing that rotates about the rotor axisline as the center.
According to a third aspect of the present invention, a positionadjustment method using any of the position adjustment devices described above for adjusting a position in a vertical direction of the lower-halfinside member relative to the lower-half outside member, includes:inserting the eccentric shaft part of the eccentric pin into theeccentric shaft hole of the lower-half inside member; rotatablysupporting the rotating shaft part of the eccentric pin at an end in acircumferential direction of the lower-half outside member; inserting the push rod into the lower-half inside member from an end surface in acircumferential direction of the lower-half inside member; and pressing the rod contact surface of the eccentric shaft part with a tip of thepush rod to rotate the eccentric pin about the rotational axis line asthe center.
Here, in this position adjustment method, the lower-half inside member may be temporarily supported before supporting the rotating shaft partof the eccentric pin; the eccentric pin may be rotated with the push rod with the lower-half inside member temporarily supported; after rotating the eccentric pin, the temporary support of the lower-half inside member may be removed, and the rotating shaft part of the eccentric pin may be supported at an end in the circumferential direction of the lower-half outside member.
With this method, the eccentric pin is rotated with the lower-halfinside member in the temporarily supported condition, so the load of thelower-half inside member is not applied to the eccentric pin, and theeccentric pin can be easily rotated.
Advantageous Effects of Invention
According to the position adjustment device, the rotating machine provided with the same, and the position adjustment method as described above, it is possible to adjust the position in the vertical direction of the lower-half inside member that forms the lower half of the inside ring, relative to the lower-half outside member that forms thelower-half of the outside cylinder, without increasing the size of the outside cylinder.
BRIEF DESCRIPTION OF DRAWINGS
FIG. 1 is a cross-sectional view illustrating a steam turbine of an embodiment according to the present invention.
FIG. 2 is a cross-sectional view taken along the line II-II of FIG. 1.
FIG. 3 is an exploded perspective view illustrating the main portion ofa position adjustment device according to the embodiment of the present invention.
FIG. 4 is a cross-sectional view of the position adjustment device according to the embodiment of the present invention.
FIG. 5 is a cross-sectional view around the position adjustment device in a steam turbine assembly process (part 1) according to the embodiment of the present invention.
FIG. 6 is a cross-sectional view around the position adjustment device in a steam turbine assembly process (part 2) according to the embodiment of the present invention.
FIG. 7 is a cross-sectional view around the position adjustment device in a steam turbine assembly process (part 3) according to the embodiment of the present invention.
FIG. 8 is a cross-sectional view around the position adjustment device in a position adjustment process according to the embodiment of the present invention.
FIG. 9 is an explanatory view (part 1) illustrating the operation of moving a lower-half vane ring in the vertical direction relative to a lower-half casing in the embodiment of the present invention.
FIG. 10 is an explanatory view (part 2) illustrating the operation of moving the lower-half vane ring in the vertical direction relative tothe lower-half casing in the embodiment of the present invention.
FIG. 11 is a cross-sectional view of the steam turbine in a steam turbine assembly process (part 4) according to the embodiment of the present invention.
FIG. 12 is a front view illustrating an eccentric pin in a first modification according to the present invention.
FIG. 13 is a front view illustrating an eccentric pin in a second modification according to the present invention.
DESCRIPTION OF EMBODIMENTS
The following describes in detail an embodiment of a position adjustment device and a rotating machine provided with the same according to the present invention, with reference to the drawings.
The rotating machine according to the present embodiment is a steam turbine. As illustrated in FIGS. 1 and 2, the steam turbine includes a rotor 1 that rotates about a rotor axis line Ar extending in thehorizontal direction as the center, a ring-shaped vane ring (inside ring) 5 disposed on the outer peripheral side of the rotor 1 and having the rotor axis line Ar as the center, a cylindrical casing (outsidecylinder) 10 disposed on the outer peripheral side of the vane ring 5and having the rotor axis line Ar as the center, and a positionadjustment device 20 (see FIG. 2) that adjusts the position of the vanering 5 relative to the casing 10.
Hereinafter, the direction in which the rotor axis line Ar extends is referred to as the rotor axis direction Da, and the radial direction with respect to the rotor axis line Ar is referred to simply as the radial direction Dr. Of the directions perpendicular to the rotor axisline Ar, the vertical direction is referred to as the vertical direction Dv, and the horizontal direction is referred to as the horizontal direction Dh. Also, the direction around the rotor axis line Ar is referred to as the circumferential direction Dc.
The rotor 1 includes a rotor shaft 2 that extends in the rotor axis direction Da with the rotor axis line Ar as the center, and a plurality of blades 3 aligned on the rotor shaft 2 in the circumferentialdirection Dc and fixed to the rotor shaft 2.
A plurality of vanes 9 aligned in the circumferential direction Dc is provided on the inner peripheral side of the ring-shaped vane ring 5 at positions on the upstream side of the blades 3 of the rotor 1. In the steam turbine, the cylindrical space between the outer peripheral side of the rotor shaft 2 and the ring-shaped vane ring 5, in other words the space in which the blades 3 and the vanes 9 are disposed, forms the steam flow path. The ring-shaped vane ring 5 includes an upper-half vanering 6 x on the upper side relative to the rotor shaft 2, and a lower-half vane ring (lower-half inside member) 6 y on the lower side thereof. The upper-half vane ring 6 x and the lower-half vane ring 6 y extend in the circumferential direction Dc, and at their respective ends in the circumferential direction Dc they are connected by bolts or the like. In this case a dividing surface 7 x, which is the end surface ofthe upper-half vane ring 6 x in the circumferential direction Dc, and a dividing surface 7 y, which is the end surface of the lower-half vanering 6 y in the circumferential direction Dc, are in mutual contact.Also, the ring-shaped casing 10 includes an upper-half casing 11 x onthe upper side relative to the rotor shaft 2, and a lower-half casing(lower-half outside member) 11 y on the lower side thereof. The upper-half casing 11 x and the lower-half casing 11 y extend in thecircumferential direction Dc, and at their respective ends in thecircumferential direction Dc they are mutually connected by bolts or the like. In this case a dividing surface 12 x, which is the end surface ofthe upper-half casing 11 x in the circumferential direction Dc, and a dividing surface 12 y, which is the end surface of the lower-half casing11 y in the circumferential direction Dc, are in mutual contact. A groove 15 that is depressed from the inner peripheral side towards the outer peripheral side is formed at both ends of the lower-half casing 11y in the circumferential direction Dc. As illustrated in FIGS. 3 and 4,the groove 15 is demarcated by a groove bottom surface 15 a that faces to the upper side, and a groove side surface 15 b that faces towards the inner peripheral side.
In the present embodiment, the casing 10 forms an outside cylinder, andthe lower-half casing 11 y forms a lower-half outside member. Also, the vane ring 5 forms an outside ring, and the lower-half vane ring 6 y forms a lower-half inside member.
As illustrated in FIG. 2, the position adjustment device 20 is provided in the groove 15 at one end of the lower-half casing 11 y in thecircumferential direction Dc and in the groove 15 at the other end. As illustrated in FIGS. 3 and 4, the position adjustment device 20 include san eccentric pin 21, two push bolts (push rods) 31 whose tips come into contact with the eccentric pin 21, a support block 41 that rotatablysupports the eccentric pin 21 within the groove 15 of the lower-half casing 11 y, a block fixing bolt (fixing fitting) 35 that fixes the support block 41 to the lower-half vane ring 6 y, a lower liner 51disposed between the support block 41 and the groove bottom surface 15 aof the groove 15, a liner fixing bolt 52 that fixes the lower liner 51within the groove 15 of the lower-half vane ring 6 y, and an upper liner53 disposed above the support block 41.
The eccentric pin 21 includes a rotating shaft part 22 formed in acolumnar shape with a rotational axis line Ac extending in thehorizontal direction and in a direction perpendicular to the rotor axisline Ar as the center, and an eccentric shaft part 23 having a side peripheral surface 26 with an eccentric axis line Ad parallel to the rotational axis line Ac with an offset therebetween as the center and a bolt contact surface (rod contact surface) 27 that comes into contact with the push bolt 31. The rotating shaft part 22 and the eccentric shaft part 23 are formed integrally. The eccentric shaft part 23includes a columnar part 24 with the eccentric axis line Ad as the center, and a notched columnar part 25 formed in a columnar shape withthe eccentric axis line Ad as the center, having the same diameter asthe columnar part 24, and having a notch formed in a part of the column.The notched columnar part 25 is formed in a half-columnar shape. A plane of the half column that includes the eccentric axis line Ad forms the bolt contact surface 27. Also, the side peripheral surface 26 of theeccentric shaft part 23 is the side peripheral surface of the columnarpart 24 and the side peripheral surface of the notched columnar part 25.
A hexagonal wrench hole 32 or the like (see FIG. 4) into which, forexample, the tip of a hexagonal wrench is inserted is formed at one endin the longitudinal direction of the push bolt 31. There are two push bolts 31 for one eccentric pin 21.
The block fixing bolt 35 includes a screw part 36 and a bolt head 37. A male thread is formed on the screw part 36. A hexagonal wrench hole 38or the like (see FIG. 4) into which, for example, the tip of a hexagonal wrench is inserted is formed in the bolt head 37.
The support block 41 includes a pin support part 42 in which a columnarrotating shaft hole 43 into which the rotating shaft part 22 of theeccentric pin 21 is rotatably inserted is formed, and a fixing part 45in which a bolt insertion hole 46 into which the screw part 36 of the block fixing bolt 35 is inserted and a head housing hole 47 into whichthe bolt head 37 is inserted are formed. The fixing part 45 is positioned above the pin support part 42, and is formed integrally withthe pin support part 42. The rotating shaft hole 43 penetrates the pin support part 42 in the horizontal direction Dh. Also, the head housing hole 47 is recessed in the horizontal direction Dh from the outer surface of the fixing part 45. The bolt insertion hole 46 penetrates the fixing part 45 in the horizontal direction Dh from the bottom surface ofthe head housing hole 47 of the fixing part 45. The inner diameter ofthe head housing hole 47 is larger than the outer diameter of the bolt head 37 of the block fixing bolt 35. Also, the inner diameter of the bolt insertion hole 46 is larger than the outer diameter of the screw part 36 of the block fixing bolt 35. Therefore, in the state in whichthe screw part 36 of the block fixing bolt 35 is completely inserted into the bolt insertion hole 46 of the support block 41, the block fixing bolt 35 is capable of a certain amount of movement in a direction perpendicular to the axis of the block fixing bolt 35 relative to the support block 41.
The width in the horizontal direction Dh of the fixing part 45 of the support block 41 is smaller than the width in the horizontal direction Dh of the pin support part 42 of the support block 41. Also, the width in the horizontal direction Dh of the fixing part 45 is slightly smaller than the width in the horizontal direction Dh of the groove 15 of thelower-half casing 11 y, and substantially the same as the width in thehorizontal direction Dh of the groove 15. The surface of the fixing part45 in the horizontal direction Dh on the lower-half vane ring 6 y side is coplanar with the surface of the pin support part 42 in thehorizontal direction Dh on the lower-half vane ring 6 y side. Therefore,when the support block 41 is accommodated within the groove 15 of thelower-half casing 11 y, a gap is produced between the fixing part 45 onthe lower-half casing 11 y side in the horizontal direction Dh and the groove side surface 15 b of the groove 15. The upper liner 53 is disposed in this gap. In this case the top surface of the upper liner 53is substantially coplanar with the dividing surface 12 y of thelower-half casing 11 y. On the other hand, the width in the horizontal direction Dh of the lower liner 51 is the same as the width in thehorizontal direction Dh of the groove 15 of the lower-half casing 11 y.As stated previously, the lower liner 51 is disposed between the pin support part 42 of the support block 41 and the groove bottom surface 15a of the groove 15.
A columnar eccentric shaft hole 16 into which the eccentric shaft part23 of the eccentric pin 21 is rotatably inserted, a push bolt hole (rod hole) 17 into which the push bolt 31 can be inserted, and a fixing bolt hole 19 into which the screw part 36 of the block fixing bolt 35 can be screwed are formed in the ends of the lower-half vane ring 6 y in thecircumferential direction Dc. The eccentric shaft hole 16 is recessed from the outer periphery of the lower-half vane ring 6 y towards the rotor shaft 2 side in the horizontal direction Dh. The push bolt hole 17is recessed vertically downwards from the dividing surface 7 y of thelower-half vane ring 6 y, and penetrates to the eccentric shaft hole 16.A female thread 18 that can mate with the push bolt 31 is formed on the inner peripheral surface of the push bolt hole 17. Two push bolt holes17 are formed for one eccentric shaft hole 16, the same number as thenumber of the push bolts 31. Of the two push bolt holes 17, one push bolt hole 17 is formed on one side of the eccentric axis line Ad in the rotor axis direction Da, and the other push bolt hole 17 is formed onthe other side of the eccentric axis line Ad in the rotor axis direction Da. The fixing bolt hole 19 is recessed from the outer periphery of thelower-half vane ring 6 y towards the rotor shaft 2 side in thehorizontal direction Dh. Therefore, the direction in which the fixing bolt hole 19 is recessed and the direction in which the eccentric shaft hole 16 is recessed are the same. A female thread that can mate with the screw part 36 of the block fixing bolt 35 is formed on the inner peripheral surface of the fixing bolt hole 19.
Next, a method of assembling the steam turbine, and a method of adjusting the position of the lower-half vane ring 6 y relative to thelower-half casing 11 y using the position adjustment device are described.
First, as illustrated in FIG. 5, the eccentric pin 21 is installed onthe lower-half vane ring 6 y, and the support block 41 is temporarily fixed to the lower-half vane ring 6 y. At this time, the eccentric shaft part 23 of the eccentric pin 21 is inserted into the eccentric shaft hole 16 of the lower-half vane ring 6 y. Next, the rotating shaft part22 of the eccentric pin 21 is inserted into the rotating shaft hole 43of the support block 41. Then, the screw part 36 of the block fixing bolt 35 is inserted into the bolt insertion hole 46 of the support block41, and the screw part 36 is lightly screwed into the fixing bolt hole19 of the lower-half vane ring 6 y. At this stage, the screw part 36 ofthe block fixing bolt 35 is not securely screwed into the fixing bolt hole 19 of the lower-half vane ring 6 y, so that the support block 41 isin such a state that it can move a certain amount relatively in a direction perpendicular to the direction in which the block fixing bolt35 extends. Note that here the eccentric shaft part 23 of the eccentric pin 21 is inserted into the eccentric shaft hole 16 of the lower-halfvane ring 6 y, and then the rotating shaft part 22 of the eccentric pin21 is inserted into the rotating shaft hole 43 of the support block 41.However, conversely the rotating shaft part 22 of the eccentric pin 21may be inserted into the rotating shaft hole 43 of the support block 41,and then the eccentric shaft part 23 of the eccentric pin 21 may be inserted into the eccentric shaft hole 16 of the lower-half vane ring 6y.
Next, as illustrated in FIG. 6, the lower liner 51 is fixed to the groove bottom surface 15 a of the groove 15 of the lower-half casing 11y using the liner fixing bolt 52.
Next, as illustrated in FIG. 7, the lower-half vane ring 6 y to whichthe eccentric pin 21 and the support block 41 have been installed is assembled onto the lower-half casing 11 y on which the lower liner 51has been installed.
In the state in which the lower-half vane ring 6 y has been assembled onto the lower-half casing 11 y, the lower-half vane ring 6 y issupported by the lower-half casing 11 y via the eccentric pin 21, the support block 41, and the lower liner 51.
Next, as illustrated in FIG. 8, after setting a dial gauge 90, the push bolt 31 is screwed into the push bolt hole 17 of the lower-half vanering 6 y. In setting the dial gauge 90, the dial gauge 90 is installed on a gauge stand 91, and the gauge stand 91 is placed on the dividing surface 12 y of the lower-half casing 11 y. In addition, the measurement probe of the dial gauge 90 is brought into contact with the dividing surface 7 y of the lower-half vane ring 6 y, so that it is possible to measure the amount of positional deviation of the lower-half vane ring 6y in the vertical direction Dv relative to the lower-half casing 11 y using the dial gauge 90. In screwing the push bolt 31 into the push bolt hole 17, the end of a hexagonal wrench is inserted into the hexagonal wrench hole 32 of the push bolt 31, and the push bolt 31 is rotated.
Next, the amounts that the two push bolts 31 are screwed into theirrespective push bolt holes 17 are adjusted as appropriate while checking the amount of deviation, which is indicated by the dial gauge 90, of the dividing surface 7 y of the lower-half vane ring 6 y relative to the dividing surface 12 y of the lower-half casing 11 y. When the two push bolts 31 are screwed into their respective push bolt holes 17, the tips of the push bolts 31 contact the bolt contact surface 27 of theeccentric pin 21, as illustrated in FIGS. 9 and 10. In addition, whenthe amounts that the two push bolts 31 are screwed into their respective push bolt holes 17 are adjusted, the bolt contact surface 27 of theeccentric pin 21 is pressed by the push bolts 31, and the eccentric shaft part 23 of the eccentric pin 21 rotates about the eccentric axisline Ad as the center. Also, the rotating shaft part 22 of the eccentric pin 21 is formed integrally with the eccentric shaft part 23, so it rotates about the eccentric axis line Ad as the center. In the process of rotating about the eccentric axis line Ad as the center, the rotating shaft part 22 rotates within the rotating shaft hole 43 of the support block 41. The rotating shaft part 22 and the support block 41 are supported by the lower-half casing 11 y, so they do not move relative tothe lower-half casing 11 y. Therefore, taking the rotating shaft part 22that does not move relative to the lower-half casing 11 y as reference,the eccentric shaft part 23 revolves about the rotational axis line Ac of the rotating shaft part 22 as the center, in accordance with the rotation of the rotating shaft part 22. Therefore, the lower-half vanering 6 y into which the eccentric shaft part 23 is inserted moves in the direction perpendicular to the rotational axis line Ac in accordance with the revolution of the eccentric shaft part 23. On the other hand,the rotating shaft part 22 of the eccentric pin 21 and the support block41 do not move relative to the lower-half casing 11 y, as stated previously. Note that, as illustrated in FIG. 8, although the support block 41 is installed on the lower-half vane ring 6 y using the block fixing bolt 35, as stated previously, the support block 41 is temporarily fixed so as to be capable of a certain amount of movement relative to the lower-half vane ring 6 y, so the support block 41 moves relative to the lower-half vane ring 6 y, but does not move relative tothe lower-half casing 11 y.
When, as a result of adjusting the amount that the two push bolts 31 are screwed into their respective push bolt holes 17, the amount of deviation indicated by the dial gauge 90, in other words the amount of positional deviation of the lower-half vane ring 6 y in the vertical direction Dv relative to the lower-half casing 11 y, is within a target amount of deviation, the two push bolts 31 are each screwed in a certain amount so that the tips of the two push bolts 31 are securely in contact with the bolt contact surface 27 of the eccentric pin 21. As a result,the eccentric pin 21 cannot rotate about the rotational axis line Ac.Then, the block fixing bolt 35 is securely screwed into the lower-halfvane ring 6 y, and the support block 41 is securely fixed to thelower-half vane ring 6 y.
Next, as illustrated in FIG. 4, the upper liner 53 is disposed in the gap between the lower-half casing 11 y side of the fixing part 45 in thehorizontal direction Dh and the groove side surface 15 b of the groove15 of the lower-half casing 11 y.
This completes the adjustment of the position of the lower-half vanering 6 y in the vertical direction Dv relative to the lower-half casing11 y.
Note that the operation of adjusting the position of the lower-half vanering 6 y relative to the lower-half casing 11 y by manipulating the two position adjustment devices 20 may be performed by carrying out the adjustment operation by manipulating one of the position adjustment devices 20 and carrying out the adjustment operation by manipulating theother of the position adjustment devices 20 at the same time, or after completing the adjustment operation by manipulating one of the positionadjustment devices 20, the adjustment operation by manipulating theother of the position adjustment devices 20 may be carried out.
Next, as illustrated in FIG. 11, the rotor 1 is assembled onto thelower-half casing 11 y onto which the lower-half vane ring 6 y has been assembled. The rotor 1 is rotatably supported on the lower-half casing11 y via bearings (not illustrated on the drawings) provided on thelower-half casing 11 y.
Next, as illustrated in FIG. 2, the upper-half vane ring 6 x is placed on the lower-half vane ring 6 y so that the dividing surface 7 x of the upper-half vane ring 6 x comes into contact with the dividing surface 7y of the lower-half vane ring 6 y, and the ends of the upper-half vanering 6 x in the circumferential direction Dc are connected to the ends of the lower-half vane ring 6 y in the circumferential direction Dc with bolts or the like.
Next, the upper-half casing 11 x is placed on the lower-half casing 11 yso that the dividing surface 12 x of the upper-half casing 11 x comes into contact with the dividing surface 12 y of the lower-half casing 11y, and the ends of the upper-half casing 11 x in the circumferentialdirection Dc are connected to the ends of the lower-half casing 11 y inthe circumferential direction Dc with bolts or the like.
This completes the assembly of the steam turbine.
In the above, after completing the adjustment of the position of thelower-half vane ring 6 y in the vertical direction Dv relative to thelower-half casing 11 y, the rotor 1 is assembled onto the lower-half casing 11 y onto which the lower-half vane ring 6 y has been assembled.However, after assembling onto the lower-half casing 11 y the lower-halfvane ring 6 y onto which the eccentric pin 21 and the support block 41have been installed, the rotor may be assembled onto the lower-half casing 11 y before completing the adjustment of the position of thelower-half vane ring 6 y in the vertical direction Dv relative to thelower-half casing 11 y.
As described above, in the present embodiment, the push bolts 31 that enter into the lower-half vane ring 6 y from the dividing surface 7 y ofthe lower-half vane ring 6 y press on the bolt contact surface 27 of theeccentric pin 21, and rotate the eccentric pin 21 about the rotational axis line Ac. Therefore, in the present embodiment, it is not necessaryto engage the tip of a tool with the eccentric pin 21 from the outside in the radial direction of the eccentric pin 21 and manipulate this tool in order to rotate the eccentric pin 21 about the rotational axis line Ac. Therefore, in the present embodiment, it is not necessary to increase the dimension of the groove 15 or increase the outer diameter of the casing 10 in order to provide tool space on the outside in the radial direction of the eccentric pin 21. In other words, in the present embodiment, the position of the lower-half vane ring 6 y in the vertical direction Dv relative to the lower-half casing 11 y can be adjusted without increasing the size of the casing 10.
Also, in the present embodiment, the position of the lower-half vanering 6 y in the vertical direction Dv relative to the lower-half casing11 y can be adjusted by adjusting the amount that the push bolts 31 are screwed in. Therefore, in the present embodiment, the position of thelower-half vane ring 6 y in the vertical direction Dv relative to thelower-half casing 11 y can be more simply, accurately, and finely adjusted than by adjusting the amount that simple rods without male threads formed on the outer periphery thereof are pressed in.
In addition, in the present embodiment, the position of the lower-halfvane ring 6 y in the vertical direction Dv relative to the lower-half casing 11 y is adjusted while screwing the two push bolts 31 into thelower-half vane ring 6 y, so when the adjustment is complete, theeccentric pin 21 cannot rotate due to the two push bolts 31. Therefore,in the present embodiment, it is not necessary to carry out a separate operation to stop the rotation of the eccentric pin 21, so the working time can be shortened.
First Modification of the Eccentric Pin
Next, a first modification of the eccentric pin will be described with reference to FIG. 12.
An eccentric pin 21 a of the present modification also includes, as withthe eccentric pin 21 of the embodiment described above, the rotating shaft part 22 formed in a columnar shape with the rotational axis line Ac as the center, and an eccentric shaft part 23 a having the side peripheral surface 26 with the eccentric axis line Ad as the center anda bolt contact surface 27 a that comes into contact with the push bolt31. In the embodiment as described above, a plane that includes theeccentric axis line Ad forms the bolt contact surface 27, but in the present modification a plane that does not include the eccentric axisline Ad but is parallel to the eccentric axis line Ad forms the bolt contact surface 27 a.
In this way, the bolt contact surface 27 a may be a plane that does not include the eccentric axis line Ad.
Second Modification of the Eccentric Pin
A second modification of the eccentric pin will be described with reference to FIG. 13.
An eccentric pin 21 b of the present modification also includes, as withthe eccentric pin 21 of the embodiment described above, the rotating shaft part 22 formed in a columnar shape with the rotational axis line Ac as the center, and an eccentric shaft part 23 b having the side peripheral surface 26 with the eccentric axis line Ad as the center anda bolt contact surface 27 b that comes into contact with the push bolt31. In the previously described embodiment and the first modification,the bolt contact surfaces 27, 27 a were planes, but in the present modification the bolt contact surface 27 b is a curved surface that is gently recessed from the notched side of the eccentric pin 21 b towards the side peripheral surface 26 side.
By making the bolt contact surface 27 b a gently recessed curved surface in this way, even when the eccentric pin 21 b is rotated about the rotational axis line Ac as the center, the contact characteristics between the tips of the push bolts 31 and the bolt contact surface 27 b can be maintained.
Other Modifications
In the embodiment as described above, the female thread 18 is formed onthe inner peripheral surface of the push bolt hole 17, which is the rod hole, and the male thread is formed on the push bolt 31, which is thepush rod, to mate with the push bolt hole 17. However, the female thread need not be formed on the inner peripheral surface of the rod hole, andthe male thread need not be formed on the push rod.
Even if such push rods are used, the rod contact surface of theeccentric pin can be pressed with the push rods, so the position of thelower-half vane ring 6 y in the vertical direction Dv relative to thelower-half casing 11 y can be adjusted without increasing the size ofthe casing 10, in the same way as the embodiment described above.
However, if such a push rod is used, it is not possible to adjust the position of the lower-half vane ring 6 y in the vertical direction Dv relative to the lower-half casing 11 y by adjusting the amount that thepush rod is screwed in, so it is difficult to accurately and finely adjust the relative position. Also, if such a push rod is used, afterthe adjustment is completed, it is necessary to additionally carry out an operation to fix the push rod so that it does not move, or an operation to stop the rotation of the eccentric pin 21.
In the embodiment as described above, two push bolts 31, which are pushrods, are used. However, one push rod may be used. However, in this case the rotation direction of the eccentric pin 21 is limited to one direction only.
Also, before rotating the eccentric pin 21, the lower-half vane ring 6 y may be suspended slightly using a crane or the like so that thelower-half vane ring 6 y does not touch the rotor 1, in other words thelower-half vane ring 6 y is temporarily supported, and in that state theeccentric pin 21 may be rotated. Then, the temporary support of thelower-half vane ring 6 y may be removed, so that the rotating shaft part22 and the support block 41 are supported by the lower liner 51 of thelower-half casing 11 y. According to this method, when adjusting by rotating the eccentric pin 31 the load of the lower-half vane ring 6 yis not applied to the eccentric pin 31, so the eccentric pin 31 can be easily rotated, and the push bolts 31 can be easily screwed in.
The position adjustment device 20 according to the embodiment as described above determines the position of the lower-half vane ring 6 y relative to the lower-half casing 11 y in the steam turbine. However,the embodiments of the present invention are not limited to this, andthe present invention may be applied to other rotating machines, such as gas turbines or compressors, provided that they include a rotor that rotates about the rotor axis line as the center, a cylindrical outsidecylinder having the rotor axis line as the center, and a ring-shaped inside ring disposed on the inner peripheral side of the outsidecylinder with the rotor axis line as the center, and that both the outside cylinder and the inside ring can be divided into an upper half and a lower half.
INDUSTRIAL APPLICABILITY
According to the position adjustment device, the rotating machine provided with the same, and the position adjustment method as described above, it is possible to adjust the position in the vertical direction of the lower-half inside member that forms the lower half of the inside ring, relative to the lower-half outside member that forms the lower half of the outside cylinder, without increasing the size of the outsidecylinder.
REFERENCE SIGNS LIST
- 1 Rotor- 2 Rotor shaft- 3 Blade- 5 Vane ring (inside ring)- 6 x Upper-half vane ring- 6 y Lower-half vane ring (lower-half inside member)- 7 x, 7 y Dividing surface (end surface in the circumferential direction)- 9 Vane- 10 Casing (outside cylinder)- 11 x Upper-half casing- 11 y Lower-half casing (lower-half outside member)- 12 x, 12 y Dividing surface- 15 Groove- 16 Eccentric shaft hole- 17 Push bolt hole (rod hole)- 18 Female thread- 19 Fixing bolt hole- 20 Position adjustment device- 21, 21 a, 21 b Eccentric pin- 22 Rotating shaft part- 23, 23 a, 23 b Eccentric shaft part- 24 Columnar part- 25 Notched columnar part- 26 Side peripheral surface- 27, 27 a, 27 b Bolt contact surface (rod contact surface)- 31 Push bolt (push rod)- 35 Block fixing bolt (fixing fitting)- 41 Support block- 43 Rotating shaft hole- 46 Bolt insertion hole- 47 Head housing hole- 51 Lower liner- 53 Upper liner
1. A position adjustment device that adjusts, relative to a lower-half outside member that forms a lower half of a cylindrical outside cylinder with a rotor axis line as the center, a position in a vertical direction of a lower-half inside member that forms a lower half of a ring-shaped inside ring disposed on an inner peripheral side of the outside cylinder and having the rotor axis line as the center, the position adjustment device comprising: an eccentric pin that includes a rotating shaft partrotatably supported at an end in a circumferential direction of thelower-half outside member, and an eccentric shaft part inserted into an end in a circumferential direction of the lower-half inside member, theeccentric shaft part rotating integrally with rotation of the rotating shaft part; and a push rod inserted into the lower-half inside member from an end surface in the circumferential direction of the lower-halfinside member, the push rod being able to come into contact with theeccentric shaft part within the lower-half inside member, wherein the rotating shaft part has a columnar shape with a rotational axis line that extends in a horizontal direction and in a direction perpendicular to the rotor axis line as the center, and the eccentric shaft part is formed with a side peripheral surface that comes into contact with an inner peripheral surface of an eccentric shaft hole in the lower-halfinside member into which the eccentric shaft part is inserted, and that has as the center an eccentric axis line that is parallel to the rotational axis line with an offset therebetween, and a rod contact surface that comes into contact with the push rod.
2. The positionadjustment device according to claim 1, wherein a female thread is formed on an inner peripheral surface of a rod hole in the lower-halfinside member into which the push rod is inserted, and a male thread capable of mating with the female thread of the rod hole is formed on an outer periphery of the push rod.
3. The position adjustment device according to claim 1, wherein the push rod includes a first push rod that comes into contact with a part of the eccentric shaft part on one side of the eccentric axis line, and a second push rod that comes into contact with a part of the eccentric shaft part on the other side of theeccentric axis line.
4. The position adjustment device according to claim 1, wherein the eccentric shaft part includes: a columnar part having the eccentric axis line as the center; and a notched columnarpart formed in a columnar shape with the eccentric axis line as the center and having the same diameter as the columnar part, a part of the column of the notched columnar part being notched, the side peripheral surface of the eccentric shaft part is a side peripheral surface of the columnar part and the notched columnar part, and the rod contact surface of the eccentric shaft part is a surface formed by notching the column.5. The position adjustment device according to claim 4, wherein the rod contact surface of the eccentric shaft part is a curved surface that is gently recessed towards the side peripheral surface from the notchedside of the column in a direction perpendicular to the rotational axisline.
6. The position adjustment device according to claim 1, further comprising a support block which is disposed on the end of thelower-half outside member, and in which a rotating shaft hole is formed into which the rotating shaft part of the eccentric pin is inserted sothat the rotating shaft part can rotate about the rotational axis line.7. The position adjustment device according to claim 6, further comprising a fixing fitting that fixes the support block to thelower-half inside member.
8. A rotating machine, comprising: the position adjustment device according to claim 1; a casing as the outsidecylinder; a vane ring as the inside ring; and a rotor disposed withinthe casing that rotates about the rotor axis line as the center.
9. A position adjustment method using the position adjustment device according to claim 1 for adjusting a position in a vertical direction ofthe lower-half inside member relative to the lower-half outside member,the method comprising: inserting the eccentric shaft part of theeccentric pin into the eccentric shaft hole of the lower-half inside member; supporting the rotating shaft part of the eccentric pin at an end in a circumferential direction of the lower-half outside member;inserting the push rod into the lower-half inside member from an end surface in a circumferential direction of the lower-half inside member;and pressing the rod contact surface of the eccentric shaft part with atip of the push rod to rotate the eccentric pin about the rotational axis line as the center.
10. The position adjustment method according to claim 9, wherein the lower-half inside member is temporarily supported before supporting the rotating shaft part of the eccentric pin; theeccentric pin is rotated with the push rod with the lower-half inside member temporarily supported; after rotating the eccentric pin, the temporary support of the lower-half inside member is removed, and the rotating shaft part of the eccentric pin is supported at an end in thecircumferential direction of the lower-half outside member.
|
Incorrect results when using BelongsToMany::sync with SoftDeletes on Pivot model
Laravel Version: 8.83.17
PHP Version: 7.4.30
Database Driver & Version: mysql 5.7
Description:
When using the sync method on a BelongsToMany relationship where the pivot table has SoftDeletes, I'm either not getting filtered results based on my deleted date column, or not able to correctly sync my relation.
With the following relationship config:
public function myRelation(): BelongsToMany
{
return $this->belongsToMany(
MyRelation::class,
'my_parent_my_relation_pivot_table',
'my_parent_id',
'my_relation_id',
'my_parent_id',
'my_relation_id',
)
->using(MyParentMyRelationPivotTable::class)
->withTimestamps()
->wherePivotNull('date_deleted');
}
The below will hard delete any records not in the array of ids to be synced:
$myParent->myRelation->sync([1, 2, 3]);
This is because in InteractsWithPivotTables, the value of using is ignored if any pivotWhereNulls are set, and falls back to a hard delete.
If I remove the wherePivotNull call, I then get an issue where, if there is ALREADY a record for a given id in the pivot table, but it is marked as deleted, a new record will NOT be added by sync, this is because the method InteractsWithPivotTables::getCurrentlyAttachedPivots does not take the value of using into account and therefore is unaware of the SoftDeletes scope on the model.
Steps To Reproduce:
Define a many to many relationship using a pivot model which has SoftDeletes
Use the sync method to add, remove, then add records back to the pivot table.
My bad, missed that!
For anyone else finding this via Google, I ended up using https://github.com/ddzobov/laravel-pivot-softdeletes for SoftDeletes with pivot tables
|
Monster infighting
Explanation
Specific mob behavior
Some mobs fight others for other reasons than retaliation, such as fighting natural enemies.
* Wolves attack skeletons, wither skeletons, and sheep unprovoked.
* Guardians and elder guardians attack squids.
* Llamas attack wolves.
* Polar bears attack foxes.
* Foxes attack chickens.
* Trader llamas attack all mobs that attack their wandering trader.
* All types of illagers and zombies (with one exception) attack all types of Villagers.
* Ocelots and cats attack chickens.
* Piglins occasionally hunt hoglins.
* Piglins and wither skeletons attack each other.
* Withers attack all mobs except undead mobs and Ghasts.
* Iron golems attack most hostile mobs except creepers.
* Snow golems attack most hostile mobs.
* Zoglins attack most mobs except creepers, ghasts and themselves.
* Vindicators named "Johnny" or have the tag set to true attack most mobs except illagers.
|
Centaur Patrol Unit
Members
* Brownbeard, an alligator centaur (ex-leader)
* Smooge, a regular centaur
* Chappe, a cow centaur
* Run, a spider centaur
* Fen Bock, a satyr
* A leopard centaur
* A giraffe centaur
* A doe centaur
* A rhinoceros centaur
* A tapir centaur
* A zebra centaur
* Regular centaurs
History
Site Navigation
Патрульный Взвод Кентавров Unité de Patrouille Centaure
|
Golf grip assembly process
ABSTRACT
A golf grip assembly process which includes coating a sleeve with a layer of soluble phenol-acetaldehyde resin over the inner surface thereof, and spraying a solvent over the layer of soluble phenol-acetaldehyde resin with before the insertion of a rod for the grip. The soluble phenol-acetaldehyde resin is dissolved by the solvent into a glue to fixedly secure the rod inside the sleeve, after the insertion of the rod into the sleeve and after the setting of the glue, so that the rod and the sleeve are incorporated into a unitary golf grip assembly.
BACKGROUND OF THE INVENTION
The present invention relates to a golf grip assembly process which is to coat a soluble phenol-acetaldehyde resin and spray a solvent over the resin before the insertion of a rod into the sleeve so that the rod can be easily inserted into the sleeve and incorporated therewith into a golf grip after drying.
FIGS. 1 and 2 illustrate two different golf grip assembly processes according to the prior art. In the assembly process of FIG. 1, a double-sided adhesive tape is wound round the rod by labor or machine. The outer stripping layer of the double-sided adhesive tape is removed from the rod and coated with a solvent, and then the sleeve is sleeved onto the rod forming into a golf grip. This assembly process is complicated and relatively expensive to finish. During the insertion of the rod into the sleeve, the adhesive tape may be curled up, causing an uneven outer surface on the golf grip (see FIG. 3). Further, replacing the golf grip is also complicated to perform.
In the assembly process of FIG. 2, an adhesive glue is squeezed into the sleeve, the rod is coated with a layer of solvent, and then the rod is inserted into the sleeve. Because the squeezing of the adhesive glue into the sleeve can not uniformly distribute the adhesive glue over the inner surface of the sleeve, less binding force is produced to secure the sleeve to the rod. When the rod is inserted into the sleeve, the adhesive glue may be partly squeezed out of the sleeve through a vent hole thereon to contaminate the outer surface of the sleeve.
SUMMARY OF THE INVENTION
The present invention has been accomplished to eliminate the aforesaid disadvantages and problems. It is therefore an object of the present invention to provide a golf grip assembly process which is easy to complete. It is another object of the present invention to provide a golf grip assembly process which requires less labor to complete. It is still another object of the present invention to provide a golf grip assembly process which provides constant quality.
According to the present invention, the golf grip assembly process is to coat the sleeve with a layer of soluble phenol-acetaldehyde resin and spraying a solvent over the resin before the insertion of the rod therein. The phenol-acetaldehyde resin is dissolved by the solvent into a glue to facilitate the insertion of the rod into the sleeve. After a 4-hour air drying process, the glue is set to fixedly secure the rod inside the sleeve, and therefore, the sleeve and the rod are formed into a golf grip assembly.
BRIEF DESCRIPTION OF THE DRAWINGS
FIG. 1 illustrates that the rod is wound with a double-sided adhesive tape according to a prior art golf grip assembly process;
FIG. 2 is a sectional view of a golf grip as constructed according to another prior art golf grip assembly process;
FIG. 3 is a sectional view of a golf grip as constructed according to the prior art golf grip assembly process of FIG. 1;
FIG. 4 is a flow chart of the present invention;
FIG. 5 is a perspective view of a rod according to the present invention;
FIG. 6 is a sectional view of a sleeve according to the present invention; and
FIG. 7 is a sectional view of a golf grip according to the present invention.
DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT
Referring to FIGS. 4, 5, 6 and 7, a golf grip assembly process according to the present invention comprises the following procedures in proper order:
1. Providing a rod 3 for the golf grip assembly (see FIG. 5);
2. Providing a sleeve 4 for the golf grip assembly and coating the inner surface 40 of the sleeve 4 with a layer of soluble phenol-acetaldehyde resin 41 (see FIG. 6);
3. Spraying a solvent over the layer of soluble phenol-acetaldehyde resin 41 in the sleeve 4 as well as the outer surface 30 of the rod 3 before inserting the rod 3 into the sleeve 4;
4. Inserting the rod 3 into the sleeve 4 immediately after the coating of solvent, causing the phenol-acetaldehyde resin 41 inside the sleeve 4 to be dissolved into a glue; and
5. Setting the glue by drying in the air for about four hours after the insertion of the rod 3 into the sleeve 4, so as to fixedly secure the rod 3 and the sleeve 4 into a unitary golf grip assembly (see FIG. 7).
I claim:
1. A method for making a golf grip assembly comprising the ordered steps of:a first step of providing a rod and a sleeve; a second step of coating an inner surface of said sleeve with a layer of soluble phenol-acetaldehyde resin; a third step of spraying a layer of solvent directly on an outer surface of said rod and on said layer of soluble phenol-acetaldehyde resin; a fourth step of inserting said rod into said sleeve immediately after said third step, said solvent dissolving said phenol-acetaldehyde resin into a glue; and a fifth step of setting said glue by air drying for about four hours to fixedly secure said rod to said sleeve and form a unitary golf grip assembly.
2. A method for making a golf grip assembly consisting the ordered steps of:a first step of providing a rod and a sleeve; a second step of coating an inner surface of said sleeve with a layer of soluble phenol-acetaldehyde resin; a third step of spraying a layer of solvent directly on an outer surface of said rod and on said layer of soluble phenol-acetaldehyde resin; a fourth step of inserting said rod into said sleeve immediately after said third step, said solvent dissolving said phenol-acetaldehyde resin into a glue; and a fifth step of setting said glue by air drying for about four hours to fixedly secure said rod to said sleeve and form a unitary golf grip assembly.
|
<?php
namespace ServiceBoiler\Prf\Site\Filters\FileType;
use ServiceBoiler\Repo\Contracts\RepositoryInterface;
use ServiceBoiler\Repo\Filter;
class ModelHasFilesFilter extends Filter
{
/**
* @var null
*/
private $id;
/**
* @var string
*/
private $morph;
function apply($builder, RepositoryInterface $repository)
{
if (!is_null($this->id) && !is_null($this->morph)) {
$builder = $builder->whereHas('files', function ($file) {
$file->whereFileableId($this->id)->whereFileableType($this->morph);
});
} else {
$builder->whereRaw('false');
}
return $builder;
}
/**
* @param string|int $id
* @return $this
*/
public function setId($id = null)
{
$this->id = $id;
return $this;
}
/**
* @param string $morph
* @return $this
*/
public function setMorph($morph = null)
{
$this->morph = $morph;
return $this;
}
}
|
Aircraft
R. WESTBURY AIRCRAFT Nov. 11, 1958 5 Sheets-Sheet 1 Filed NOV. 29, 1955 Nov. 11, 1958v R. WESTBURY 2,859,926
' AIRCRAFT Filed Nov. 29, 1955- s sheets-sheet 2 Nov.V 11, 1958 R, W5S-mum(v 2,859,926
AIRCRAFT Filed Nov. 29, 1955 A'I5 Sheets-Sheet 3 '5? [ucm/CAL' 5.5 6!
f 5mn/Auw@ @rf 0N .53 v J5] ,4l/70 f2/07 i 52 54] 00A/7km '79 95 95a, 76 A v 65 i V- Aun) .Smau/2m ,W7/RHA), AMM/nger t J0] 1 v .99 Aura ,f2/ar @0 l wow mss m rm' TRM/sauer@ 102 rR/M Maron Y 70 Ffa `.snm/MNM 2.
.90" O O O O O N O O S `0 o 50* 68 I 6` /"`9I 69 7: O o O o Q o N s O fig. .5. j@ 4 fli AIRCRAFT Roy Westbury, Bridgnorth, Salop, England, assignorit'- H. M. Hobson Limited, London,-England, a British company t Application November 29,1955', serial No. 549,737
Claims priority, application Great Britain Y December 3, 1954 1 0 Claims. (Cl. 244-76) tends to oscillate, particularly in yaw, from the desired.
purpose of'damping out these oscillations. 1
'It is ,accordingly convenient to employ for the actuation of'j each control surface a hydraulic servo motor, disposed^ near lthe'control surface and 'operablefby an electro-hydraulic actuator, to which', electric signals are applied ei the'rfas'the result o f manual movement of a pilots 4control member, or automatically, when the sy stern'is under automaticfpilot control, to adjust the position ofthe control surface.
It is, however, desirable to` provide a standby mechani cal link ag'efor use in operating the servo motor in the event of an electrical failure, the pilots operating member being normally uncoupled fromA the link age and means v being provided whereby, in Vtheevent of an undue discrepancy between the positions of the operating lever and the control surface, a lock can be engaged to couple the operating member'to the link age and the electrical signalling system can be 'rendered inoperative on the servo motor. However, itis undesirable that these results should ensueas thefresult of the discrepancy arising from the servo motor being unable to move the control surface to the position called for by thev pilots action, ei ther due to the servo motor being unable to develop course and an auto-stabilizer is usually provided for the sutiicient force to overcome the control surface hinge moment or due t the servo motor becoming velocity v saturated, i. e. being unable to execute with sufficient speed the movement demanded by the pilots action.
The invention accordingly provides, in an aircraft, a power operated flying controljsystem comprising a hydraulic servo motor, for actuating a control surface of the aircraft, which is operable by an electro-hydraulic actuator under control of an electrical signalling system and also by a mechani cal link age to move the control surface to positions selected by a pilots control member, said link age being v uncoupled fr-om the control member when the electric signalling system is in operatioma 'lock for coupling the control member tothe link age, a rst switch mechanism which-is diterentially operable by relative movement in opposite directions of the control member and the link age, a second switch mechanism which is. differentially operable by movement in opposite directions of the output l member of the electro-hydraulic actuator, and, changeover mechanism' operable by said switchmechanismsin the event of runaway of the actuator'but not as the result of insufficient movement of the control surface in the direction selected by the pilot, to
engage the lock'and yto disable the electrical signalling, system, thereby giving the pilot mechani cal control over the servo motor through the link age.l
The arrangement may be such that, in the event of failure of the electrical signal, the rst switch mechanism iii tis Patent-@- Patented Nev. 1 1 ,11255 is operated as the result of movement by the pilot of his control member in an instinctive attempt to l counteract the resultant runaway o'f the electro-hydraulic actuator. Alternatively, the mechani cal link age may be arranged to move inV unison with the control tions of the control surface and the control l member are sufficiently discrepant. In ei ther case, actuation v ofthe first switch mechanism will not be effective to cause op eration of the changeover-mechanism when the control surface is unable to move sufficiently in the direction selected by the pilot.
One embodiment of the invention will no w be described in detail, by way of example, with reference to the accom y pan ying drawings in which:
Figs. l and 1A collectively constitute a diagram ofthe complete i lying control system, showing the parts in the positions they occupy when the control surface is under electrical control.
Fig.- 2V is a circuit diagram.
Fig. 3 is a front elevation of the electro-mechani cal transducer and Fig. 4 is a similar view, showing the cover plate of the transducer removed.
Like reference numerals indicate like parts throughout the figures. Y
Figs. 1 and lA show the mechanism for actuating one control surface 10 of the aircraft, which may be assumed to be the elevator, under control of the pilots control member 11 (Fig. l). It will be understood that similar mechanism is employed for actuating the ailerons, and rudder. f
10 and also to a lever 44. The jack pistons are accommodated in cylinders 16, 16a in a cylinder block 17 pivoted at 18 to the aircraft structure. Associated with the cylinders 16, 16aare control valves 19, 19a, which'constitute the input member, of the servo motor and control the admission to the cylinders of liquid under pressure from separate sources connected to inlets 20, 20a respectively. Exhaust outlets 21, 21a are associated with-the two jack cylinders. The control valves 19, 19a are mounted on a common rod 22,' pivoted at 23 to a 'differential link 24. As will be readily seen, movement of the control valves from the neutral position shown will cause the jack pistons 13, 13a to move in the reverse direction to actuate the elevator 10.
The pilots control member 11 is connected to a lever 25, pivoted at.26, by a link age 38 incorporating nonlinear gearing 27 of the kind described in U. S. application No. 510,931, filed May 25, 1955. The lever 25 carries an arm 28 pivoted at 29 to the piston rod 30 4of .Zoperates as described in U. S. application No. 407,536,
led February l, 1954, now Patent No. 2,783,006, Feb-` ruary 26, 1957, to establish alternative connection ofthe signal line 35 to a pressure line-37 and to an exhaust line 9 so as to establish in the jack cylinder 32 a hydraulic pressure which increases with airspeed. The feel imv surface and to actuate the first switch mechanism automatically when the posi- The elevator 10 (Fig. lA) is pivoted at 12 and actuated by a hydraulic servo motor comprising two jack' parted to the control member 11 accordingly increases with airspeed Vand the non-linear gearing 27 operates, as described in U. S. application No. 510,931, to vary as a function of Vairspeed the travel of the control member required to produce unit displacement .of the control surface. The link age 38 is lpi voted. at 39 -to link 40y pivoted at 41 to a control is pivoted at 43 to the lever 44 whichis connected at93 to a link 45 pivoted to the upper end .46 of the'differential link 24. Y l v Associated with the link 40 is a backlash lock 47. Pistons 48, 48avloaded by springs 49, 49a seek to raise ther lock 47 to engage a lower end 51 Vof the link 4t), so eliminating .backlash between the control member 11 and the control rod 42. When, however, the system ris organised for operation of the servo motor under .control of electrical-signals ,from the control member 11, as shown, the lock 47 is disengaged and the control member 11-is uncoupled from the l control rod 42.
Turning now to Fig. 2, `it will be seen that the Y pilot is provided with an on switch 151,V actuation of which selects electrical signalling and, with an olf switch 52, actuation'of which disengages electrical signalling. On actuation ofthe switch 151, current is supplied from supply terminals 53 to a relay 54 and to solenoids 55, 56 and 56a. Operation of the relay 54 closes a switch 541 to maintain a holding circuit for the relay 54 and for -the three solenoids. Energization of the solenoids 56, 56a causes associated valves 57, 57a to moveto-the position shown in Fig. l, thereby admitting liquid under pressure from an inlet 58 along a line 158 to cylinders 5.9, 59a housing the `pistons 48, 48a, thereby depressing the pistons against their springs and moving the flock 47 to the disengaged position as shown. When the solenoids 56, 56a are de-energized, the valves 57, 57a move to their alternative positions in which they connect the cylinders 59, 59a to an exhaust line 60, so allowing the-,pistons 4.8`to engage the'lock 47. n
Energization of the solenoid 55 moves an associated valve 61 to the position shown in Fig. lA, thereby admitting pressure from the inlet 58 to a cylinder 62 and-moving the piston 63 to the right against a spring 64 as shown. This causes a bell crank 65, pivoted at v66,.,to rock clockwise and thereby, through a spring 106, to lift the differential link 2.4 to the position shown, in which its upper end abuts against a fixed fu lc rum 70 on the cylinder block 17. Movement of the bell crank to the position shown closes an auto-pilot hold-in switch 68, shown also in Fig. 2. When the solenoid 55 is de-energized, the valve 61 is moved to connect the-cylinder 62 to a line69 connected to the exhaust outlet 21, thereby allowing the spring 64 to rock the bell crank 65 counterclockwise to open the switch 68 and, through a link :67,
to lower the differential link 24 to a position in which its upper end 46 is free and a notch 71 at its lower end engages a fixed fu lc rum pin 72 on the cylinder block `17.
Energization `of the relay 54 also closes a switch 542, Fig. 2, thereby connecting to supply terminals 73, `three potentiometers 74, 75, 76.
When, as the result of closure of the switch V151, manual control with electrical signalling is selected, the pilots control member 11, subject to hydraulic feel, is free to move within the confines of the lost motion provided at the backlash lock, to rock the lever 25 about its pivot 26. A pick off 77 attached to the lever 25 co acts with the potentiometer 74 to send an electrical -signa'l to a magnetic amplifier 78. The magnetic amplifier is a device using saturable reactors to secure amplification. Such devices are described in the text book Magnetic Amplifiers, by H. F. Storm, published by John -Wiley & Sons Inc., New York, 1955. The control Surface carries a pick off 79 co acting with the vpotentiometer' 75. The amplier compares the signals from Vthe potentiometers 74, 75 which are respectively Y representative of the rod 42. The control mod .42i
notch y50 in the lock with thel Y positions of the control member, and the V control surface 1 parentwmovement of the v relay Valve 81 from-the-neutral z upper end, which is maintained simulator, to actuate a tappet '94a and tok open a ,rear
position shown will .cause Vthe :associated first :stage -ram 82 (which constitutes the output member of the z hydraulic actuator) Yto move in the reverse direction. `A ,pin .83, engagingthebase of a'V-shaped slot 84 in the differential link 24, then rocks ythe link about its upper fend 46 to displace the control-:valves 19, y19a of the duplicated main jack.
When the pilot moves h'is'lev'er 11 forwards, i. e. anticlockwise as seen in Fig. l, the transducer 80 shifts the -valve l81 to the right, 'thereby causing the rain' '82 and control valves 19, '19a to move to the left. "I'he main rams 13, 13a accordingly move to they right to`de-' press'theelevat'or 10. The ram 82 carries a pick olfSSj co acting with the potentiometer 76. During movement'v off the control surface, position feedback signals Vare transmitted from the potentiometer 75 and velocity feed# back signals are transmitted from the potentiometer 76Y to the amplifier 78. When the control surface has reached the position selected V by 'the pilot, the rst stage ram '82 land therefore the control valves 19, 19a "are returned to the `neutral position shown by the transducer 80. As -will be obvious, a similar sequence of events' takes place when the pilot moves his lever rearwardly, the l first y stage v control servomotor is l under electrical control, an auto stabilizer 186 is effective on ythe amplifier 78 to impart corrections tothe position ofthe control surface.
As shown in Figs. 3 and 4, the transducer 80 comprises i an armature'87 mounted on a' shaft 88 carrying an arm; 89 connected to the control valve 81. The armature`87 failure occasioned by seizure of ei ther a forward sign sensing switch 92 or a rear sign sensing switch "92a,
has moved his lever 11 forwards or rearward. When the switch 92 is opened, the control surface 10 will move i down, rocking the link 44 about its intermediate `pivot point 93 and shifting the-control rod 42 to the left. vThe link 40 will'accordingly 'be rocked clockwise about its stationary by the feel overload sensing switch 95a.
As will be apparent from Fig. 2, opening of the con- I tacts 92 and 95a will break the holding circuit to the `relay 54 and to the solenoids 55, 56, 56a. The system thus reverts automatically to mechani cal control. De-
energization of the relay 54 opens the switch 542 toV disconnect the potentiometers 74, 75, 76 from the supply. De-energization of the solenoids 56, 56a engages the lock 47 as already explained. De-energizaton of the solenoid 55,
ferential link 24 to its downward position. It is then 83 is now accommodated in the wide part of motor V by rocking the link 24 about the control rod 42, the link 24 acting as a follow 11p link to .restore the control valves v19, 19a to their neutral v position when the control surface has reached the position :selected by the pilot.
If .failure occurs when the v pilot has move'd his lever 11 rearwardly, the ram 82 will open the rearward sign valve 81 being `then 'moved to' thev left to cause the control surface 1'0 to rise.' While the 'from the v amplifier'"7.8fa1'e'k failure, or a hydraulic l the rst stage control" valve81,the first stage ram 82 will run away and open according as to whether the pilot also as already explained, moves the fd if- Y sensing switches 92a, andrthe'resultant upward movement of the control surface will cause the control rod 42 to swing the link 40 anti-clockwise to actuate a tappet 94 to open a forward overload sensing switch j 95. As will be clear from Fig. 2, this will break the holding circuit to the relay S4 and solenoids 55, 56 and 56a and cause reversion to mechani cal control.
The mechani cal link age thus acts as a reference against which 'the electrical link is continuously checked, an emergency system being automatically engaged when the discrepancy between the Y two exceeds a safe amount.
When however, the overload and sign sensing switches are actuated as the result of the control surface being unable to move sufliciently, or sufficiently rapidly, in the direction selected by the pilot switches of the same sign will be opened. Thus, Vin the case of forward movement of the lever 11 switches 92 and 95 will be opened, while switches 92aand 95a.will be opened in the ,case of rearward movement of the lever. As will be clear from Fig. 2, this will not break the holding circuit and reversion to mechani cal control will not occur.
If, while the electrical signalling system is in operation, the pilot desires tov place the servo mechanism under control of the auto-pilot he can do'so by operating an on switch 96 (Fig. 2). Auto-pilot control is removed by v operation of an off switch 97. When the on switch 96 is operated, and provided the switch 541 is closed to maintain the electrical signalling system in operation, a relay 98'is energised, to close a switch 981 to maintain a holding circuit ,for itself, to. open a switch 982 to deenergize the solenoids 56, 56a, to open a switch 983and to close a switch 984 see also (Fig. lA). On closure ofthe switch 984 the auto-pilot 99 is switched in to take over control of the system through the agency of the amplier 78 and transducer 80. As the result of de-energization of the solenoids 56, 56a the backlash lock 47 is engaged and the pilots-lever 1 1v is moved by the control rod 42 in unison with the control` surface. The auto-pilot 99 sends signals, via a low pass iilter 100 to a trim relay 101, so causing a trim motor 102 to rock the plate 34 about its pivot 26 to straighten the link age 28, 30, signals being fed back from a potentiometer 103 carried by the plate34 to the relay 101 to terminate the operation of the trim motor 102 when the link age has straightened.
In the event of failure when the system is under autopilot control, the control surface 10 will, since movement of the control rod 42 is desisted by the feel simulator, displace the upper end 46 of the differential link from abutment with the fu lc rum 70. This will rock the bell crank 65 and so open the switch 68. Since the switch 983 (Fig. 2) is now open, this will break the holding circuit and cause reversion to mechani cal control as already explained. A Y
If the change over system should fail to respond to a failure of the electrical system, the pilot can actuate an emergency cock 104 thereby connecting the cylinders 59, 59a and 62 to an exhaust outlet 10S, and causing the lock 47 to engage and the differential link 24 to move down to the position appropriate for mechani cal operation of the servo system.
If desired, provision may be made for automatic deenergization of the solenoid 56 when a given Mach number is attained, thereby allowing its piston 48 to move up to reduce the backlash in the mechani cal link age.
It is desirable that the inlets 20 and 58 should be connected to a common supply. Reversion from electrical V to manual control will then be automatic in the event of failure of the hydraulic supply pressure, since the piston 63 will then be moved to the left by its spring 64 to shift the differential link 24 to its alternative position as already explained.
What I claim as my invention and desire to secure by Letters Patent is:
l. A power operated flying control system for aircraft comprising api lots v control member, a Icontrol surface, a hydraulic servo'motor comprising an input member and iii' output member, said output'memb'er being coupled toV said control surface, an electro-hydraulic actuator having an input member and an output member, means` vfor connecting the output member'of the electro-hydraulic actuator toY the input member v of the hydraulic servo motor, an electrical signalling system operable by said control member to impart'm'ovement to the input member of l said actuator and thereby to ,move the control surface to positions selected by the control member, means for switching the electrical signalling system in to and out of operation,'a mechani cal link age for actuating the input member of said servo motor, a lock for coupling said link age to said control member, lock .controlling means controlled Vb'y'said switching means for engaging said lock when said electrical signalling system is out of operation and disengaging said lock when said electrical signalling system is in operation, a first electrical switch mechanism comprising'a pair of V switches which are arranged to be selectively operated by relative v movement in opposite directions of said control member and said link age, a second electrical switch,
mechanism comprising a pair of switches which arel arranged to be selectively operated by movement. vin opposite directions of the outputmembe'r vof the electrohydraulic actuator, andl changeover mechanism operable by said switch mechanisms when `said electrical A signalling system is in operation and in the event of runaway of said actuator and to disable said electrical signalling system and thereby cause said lock controlling means to engage said lock, said change over mechanism being unresponsive to -actuation of said switch mechanisms asthe result of'insufcient movement of the control surface in the direction selected by the control member.
k2. A flying v.control system as claimed in claim l, wherein said link age is connected to move in uni sion with` said control surface and to operate said first switch mechanism in the event of a predetermined discrepancy between the positions ofthe control `member and of the control surface. l v
3. A flying control system as claimed in claim 2, comprising an auto pilot, switch means operable to render said auto pilot effective to control through the electrical signalling system the position of the input member of said actuator and means responsive to operation of said switch means for engaging said lock.
4. A power operated flying control system for aircraft comprising a pilots control member, a control surface, a hydraulic servo motor comprising an input member and an output member, said output member being coupled to said control surface, an electro-hydraulic actuator having an input member and an output member, means for connecting the output member Vof the-electro-hydraulic actuator `to the input member of the hydraulic servo motor, an electrical sign z'tl ling` system operable by said control member to impart movement to the input member of said actuator and thereby to move the control surface to positions selected by the control member, means for switching the electrical signalling system into and out of operation, a mechani cal link age for actuating the input member of said servo motor, a second mechani cal link age connected to said control member, a lock for coupling said link ages together, means controlled by said switching means for engaging said lock when said electrical signalling system is out of operation and disengaging said lock when said electrical signalling system is in operation, a first switch mechanism comprising two switches between which said second link age is movable with backlash when said lock is disengaged, said` switches being selectively actuable by m-ovement in opposite directions to a predetermined extent of said second link age, a second switch mechanism comprising two switches which are selectively operableby'movement in opposite directions of the 'output member V of said actuator, and changeover mechanism operable by said switch A.mechanism when said electrical signalling system is in operation 'and in the event of runaway of'said actuator to engage said lock and to disable said electrical signalling system, said change over mechanism `being unresponsive to actuation of said Y input member of said k servo motor, a'differential link',
movable from a first position fin which it connects Vthe input member of the servo motor vto the output member of the actuator to 'a second position in which it connects said input member to said mechani cal link age, a. lock forV coupling` said link age to said 'input in eniber,V
means for ,switching the electrical signalling system A into and out of operation, lock controlling means controlled by said switching means for engaging said 'lock when said electrical signalling system is out of operation and disengaging said lock when said electrical signalling system is in operation, link controlling means c ontrolledby said switching mechanism for moving said differential link to its first position when said electrical signalling v system is in operation and to its second position when said electrical signalling system is out of operation, .a rst electrical switch mechanism comprising a pair of switches which are arranged'to 'be selectively/operated by relative movement in opposite directions of said ,control member and said link age, a second electrical 4switch mechanism 'comprising a pair of switches which are arranged to be selectively operated by movement in opposite directions .of the output member vof the electrohydraulic actuator, and changeover mechanism operable by said switch mechanisms when said electrical signalling system is in operation and in the event of runaway of-A said actuator to disconnect'the electrical signalling system from'a source of electrical supply and thereby cause said lock controlling means to engage' said lock and said 'link'controlling means to move said differential link to the second position, said changeover mechanism being unresponsive to actuation of said switch mechanisms as the result of insufficient movement of the controll surface in the direction selected by the control member. 6. A flying control system as claimed in claim. y5,
comprising an auto pilot, switch means operable 'to render said autopilot effective to control through k-the electrical signalling v system the position of the .inputv member of said actuator, means responsive to operation of said switch for engaging said lock, an auto pilot hold-in switch associated with said dierential link and arranged to b e operated, on movement V of said differential link to its secondfposition while said auto pilot is k effective, to disable said electrical signalling system. l
7. power operated flying control system for aircraft comprising a two-stage hydraulic servo motor each stage of which has -an input member Vand yan 4output member, an electrozmechani cal transducer ,for actuating the input member of theyiirst stage, a pilots control member, an
electrical signalling systemoperableby said/ control member to transmit signals Vto said transducer, a control surface connected Ato the output member of the second stage yand movable A thereby to positions selected by lthe control member, amechanica'l link age operable by said control member, means ,for switching the electrical signalling system into and out of operation, a differential link connected to the input member of the second stage, and means controlled by said :switching mechanism yfor automatically shifting saiddiiferential link-,to and from a rst position, occupied by said link'when said signalling system is in operation, to fa second position, .occupied b y said link when said sjlignallingsystem is out of operation, said link when in its first position .being connected to thefoutput member Aof the first stage and :pivoting about ahlirst fu'lc rum to impart movement to the .input member o'f heV second s tagevundercontrol of said output member'and, when in its second position, being disconnected from said output member and .pivoting about a second fu lc rum to'impart movement to the input mem-` ber of the second stage under control of said mech link age, -l
ani cal 8,' A .flying control system as ,claimed in claim 7,
wherein opposite ends of the differential ,link co act with i A said first v and 'second ,ful cra and comprising ,a pin and v slot .connection .between the differential link and the" output member of the first stage which is effective to rock said differential link only when said link is in its v first position. 9. A flying control system as claimed in claim 8, comprising a link connecting the mechani cal link age to thel' end ofthe differential link which pivots aboutthe second fu lc rum,
1'O.`A V flying control system as claimed in claim 7,
comprising a biased servo piston for controlling the p osition ofthe differential link, a valve for controlling communication between the servo piston, a source of fluid pressure ,and exhaust, and a relay associated with the electrical signalling system for controlling the position of .said valve.
References Cited in the le of this patent UNITED STATES PATENTS 2,673,314 McCallum Mar. 23, 1954 2,678,177 Chenery'et al. May 1l, 1'954 2,683,004 Alderson yet al. July 6, 1954 2,731,217 NoXon Jan. 17, 1956 v v FOREIGN PATENTS ,Great .Britain ..v Sept. l7, 1952
|
Halle, Merseburg, and Magdeburg, and, in Silesia, near Breslau.
Numbers vary from fifty to seventy head per diem for twenty guns, to 1, 800 or 2,000 head for ten or twelve guns. The best day's bag of one gun was that of 832 made by the Emperor in 1893 ^^ Neugatters leben (Baron W. Alvensleben), in the Prussian province of Saxony, near Magdeburg. A year previous the Emperor made the next best record in the neighbourhood at Barby (Herr von Dietze) with 700.
The ordinary plan of driving is to surround a square with a mixed line, from two to five beaters between each gun, each man slowly walking towards the centre, the whole forming a gradually narrowing
|
package xyz.cafeconleche.web.thebride.controller.rest;
import org.springframework.beans.factory.annotation.Autowired;
import org.springframework.hateoas.config.EnableHypermediaSupport;
import org.springframework.hateoas.config.EnableHypermediaSupport.HypermediaType;
import org.springframework.http.HttpStatus;
import org.springframework.http.ResponseEntity;
import org.springframework.web.bind.annotation.PathVariable;
import org.springframework.web.bind.annotation.RequestMapping;
import org.springframework.web.bind.annotation.RequestMethod;
import org.springframework.web.bind.annotation.RestController;
import xyz.cafeconleche.web.thebride.hateoas.resources.FollowResourceSupport;
import xyz.cafeconleche.web.thebride.service.FollowResourceService;
@RestController
@RequestMapping("/{username}/following")
@EnableHypermediaSupport(type = HypermediaType.HAL)
public class FollowingController {
@Autowired
private FollowResourceService followingResourceService;
@RequestMapping(value={"", "/"}, method=RequestMethod.GET)
public ResponseEntity<FollowResourceSupport> list(@PathVariable String username) {
FollowResourceSupport resourceSupport = followingResourceService.getFollowing(username);
if(resourceSupport == null){
return new ResponseEntity<FollowResourceSupport>(HttpStatus.NOT_FOUND);
}
return new ResponseEntity<FollowResourceSupport>(resourceSupport, HttpStatus.OK);
}
}
|
package txmgr
import (
"context"
"database/sql"
"fmt"
"sync"
"time"
"github.com/jpillora/backoff"
"github.com/pkg/errors"
"github.com/prometheus/client_golang/prometheus"
"github.com/prometheus/client_golang/prometheus/promauto"
"go.uber.org/multierr"
"gopkg.in/guregu/null.v4"
clienttypes "github.com/smartcontractkit/chainlink/v2/common/chains/client"
feetypes "github.com/smartcontractkit/chainlink/v2/common/fee/types"
txmgrtypes "github.com/smartcontractkit/chainlink/v2/common/txmgr/types"
"github.com/smartcontractkit/chainlink/v2/common/types"
"github.com/smartcontractkit/chainlink/v2/core/chains/evm/label"
"github.com/smartcontractkit/chainlink/v2/core/logger"
"github.com/smartcontractkit/chainlink/v2/core/services/pg"
"github.com/smartcontractkit/chainlink/v2/core/utils"
)
const (
// InFlightTransactionRecheckInterval controls how often the Broadcaster
// will poll the unconfirmed queue to see if it is allowed to send another
// transaction
InFlightTransactionRecheckInterval = 1 * time.Second
// TransmitCheckTimeout controls the maximum amount of time that will be
// spent on the transmit check.
TransmitCheckTimeout = 2 * time.Second
)
var (
promTimeUntilBroadcast = promauto.NewHistogramVec(prometheus.HistogramOpts{
Name: "tx_manager_time_until_tx_broadcast",
Help: "The amount of time elapsed from when a transaction is enqueued to until it is broadcast.",
Buckets: []float64{
float64(500 * time.Millisecond),
float64(time.Second),
float64(5 * time.Second),
float64(15 * time.Second),
float64(30 * time.Second),
float64(time.Minute),
float64(2 * time.Minute),
},
}, []string{"chainID"})
)
var ErrTxRemoved = errors.New("tx removed")
type ProcessUnstartedTxs[ADDR types.Hashable] func(ctx context.Context, fromAddress ADDR) (retryable bool, err error)
// TransmitCheckerFactory creates a transmit checker based on a spec.
type TransmitCheckerFactory[
CHAIN_ID types.ID,
ADDR types.Hashable,
TX_HASH, BLOCK_HASH types.Hashable,
SEQ types.Sequence,
FEE feetypes.Fee,
] interface {
// BuildChecker builds a new TransmitChecker based on the given spec.
BuildChecker(spec txmgrtypes.TransmitCheckerSpec[ADDR]) (TransmitChecker[CHAIN_ID, ADDR, TX_HASH, BLOCK_HASH, SEQ, FEE], error)
}
// TransmitChecker determines whether a transaction should be submitted on-chain.
type TransmitChecker[
CHAIN_ID types.ID,
ADDR types.Hashable,
TX_HASH, BLOCK_HASH types.Hashable,
SEQ types.Sequence,
FEE feetypes.Fee,
] interface {
// Check the given transaction. If the transaction should not be sent, an error indicating why
// is returned. Errors should only be returned if the checker can confirm that a transaction
// should not be sent, other errors (for example connection or other unexpected errors) should
// be logged and swallowed.
Check(ctx context.Context, l logger.Logger, tx txmgrtypes.Tx[CHAIN_ID, ADDR, TX_HASH, BLOCK_HASH, SEQ, FEE], a txmgrtypes.TxAttempt[CHAIN_ID, ADDR, TX_HASH, BLOCK_HASH, SEQ, FEE]) error
}
// Broadcaster monitors txes for transactions that need to
// be broadcast, assigns sequences and ensures that at least one node
// somewhere has received the transaction successfully.
//
// This does not guarantee delivery! A whole host of other things can
// subsequently go wrong such as transactions being evicted from the mempool,
// nodes going offline etc. Responsibility for ensuring eventual inclusion
// into the chain falls on the shoulders of the confirmer.
//
// What Broadcaster does guarantee is:
// - a monotonic series of increasing sequences for txes that can all eventually be confirmed if you retry enough times
// - transition of txes out of unstarted into either fatal_error or unconfirmed
// - existence of a saved tx_attempt
type Broadcaster[
CHAIN_ID types.ID,
HEAD types.Head[BLOCK_HASH],
ADDR types.Hashable,
TX_HASH types.Hashable,
BLOCK_HASH types.Hashable,
SEQ types.Sequence,
FEE feetypes.Fee,
] struct {
logger logger.Logger
txStore txmgrtypes.TransactionStore[ADDR, CHAIN_ID, TX_HASH, BLOCK_HASH, SEQ, FEE]
client txmgrtypes.TransactionClient[CHAIN_ID, ADDR, TX_HASH, BLOCK_HASH, SEQ, FEE]
txmgrtypes.TxAttemptBuilder[CHAIN_ID, HEAD, ADDR, TX_HASH, BLOCK_HASH, SEQ, FEE]
sequenceSyncer SequenceSyncer[ADDR, TX_HASH, BLOCK_HASH]
resumeCallback ResumeCallback
chainID CHAIN_ID
config txmgrtypes.BroadcasterChainConfig
feeConfig txmgrtypes.BroadcasterFeeConfig
txConfig txmgrtypes.BroadcasterTransactionsConfig
listenerConfig txmgrtypes.BroadcasterListenerConfig
// autoSyncSequence, if set, will cause Broadcaster to fast-forward the sequence
// when Start is called
autoSyncSequence bool
txInsertListener pg.Subscription
eventBroadcaster pg.EventBroadcaster
processUnstartedTxsImpl ProcessUnstartedTxs[ADDR]
ks txmgrtypes.KeyStore[ADDR, CHAIN_ID, SEQ]
enabledAddresses []ADDR
checkerFactory TransmitCheckerFactory[CHAIN_ID, ADDR, TX_HASH, BLOCK_HASH, SEQ, FEE]
// triggers allow other goroutines to force Broadcaster to rescan the
// database early (before the next poll interval)
// Each key has its own trigger
triggers map[ADDR]chan struct{}
chStop utils.StopChan
wg sync.WaitGroup
initSync sync.Mutex
isStarted bool
utils.StartStopOnce
parseAddr func(string) (ADDR, error)
}
func NewBroadcaster[
CHAIN_ID types.ID,
HEAD types.Head[BLOCK_HASH],
ADDR types.Hashable,
TX_HASH types.Hashable,
BLOCK_HASH types.Hashable,
SEQ types.Sequence,
FEE feetypes.Fee,
](
txStore txmgrtypes.TransactionStore[ADDR, CHAIN_ID, TX_HASH, BLOCK_HASH, SEQ, FEE],
client txmgrtypes.TransactionClient[CHAIN_ID, ADDR, TX_HASH, BLOCK_HASH, SEQ, FEE],
config txmgrtypes.BroadcasterChainConfig,
feeConfig txmgrtypes.BroadcasterFeeConfig,
txConfig txmgrtypes.BroadcasterTransactionsConfig,
listenerConfig txmgrtypes.BroadcasterListenerConfig,
keystore txmgrtypes.KeyStore[ADDR, CHAIN_ID, SEQ],
eventBroadcaster pg.EventBroadcaster,
txAttemptBuilder txmgrtypes.TxAttemptBuilder[CHAIN_ID, HEAD, ADDR, TX_HASH, BLOCK_HASH, SEQ, FEE],
sequenceSyncer SequenceSyncer[ADDR, TX_HASH, BLOCK_HASH],
logger logger.Logger,
checkerFactory TransmitCheckerFactory[CHAIN_ID, ADDR, TX_HASH, BLOCK_HASH, SEQ, FEE],
autoSyncSequence bool,
parseAddress func(string) (ADDR, error),
) *Broadcaster[CHAIN_ID, HEAD, ADDR, TX_HASH, BLOCK_HASH, SEQ, FEE] {
logger = logger.Named("Broadcaster")
b := &Broadcaster[CHAIN_ID, HEAD, ADDR, TX_HASH, BLOCK_HASH, SEQ, FEE]{
logger: logger,
txStore: txStore,
client: client,
TxAttemptBuilder: txAttemptBuilder,
sequenceSyncer: sequenceSyncer,
chainID: client.ConfiguredChainID(),
config: config,
feeConfig: feeConfig,
txConfig: txConfig,
listenerConfig: listenerConfig,
eventBroadcaster: eventBroadcaster,
ks: keystore,
checkerFactory: checkerFactory,
autoSyncSequence: autoSyncSequence,
parseAddr: parseAddress,
}
b.processUnstartedTxsImpl = b.processUnstartedTxs
return b
}
// Start starts Broadcaster service.
// The provided context can be used to terminate Start sequence.
func (eb *Broadcaster[CHAIN_ID, HEAD, ADDR, TX_HASH, BLOCK_HASH, SEQ, FEE]) Start(_ context.Context) error {
return eb.StartOnce("Broadcaster", func() (err error) {
return eb.startInternal()
})
}
// startInternal can be called multiple times, in conjunction with closeInternal. The TxMgr uses this functionality to reset broadcaster multiple times in its own lifetime.
func (eb *Broadcaster[CHAIN_ID, HEAD, ADDR, TX_HASH, BLOCK_HASH, SEQ, FEE]) startInternal() error {
eb.initSync.Lock()
defer eb.initSync.Unlock()
if eb.isStarted {
return errors.New("Broadcaster is already started")
}
var err error
eb.txInsertListener, err = eb.eventBroadcaster.Subscribe(pg.ChannelInsertOnTx, "")
if err != nil {
return errors.Wrap(err, "Broadcaster could not start")
}
eb.enabledAddresses, err = eb.ks.EnabledAddressesForChain(eb.chainID)
if err != nil {
return errors.Wrap(err, "Broadcaster: failed to load EnabledAddressesForChain")
}
if len(eb.enabledAddresses) > 0 {
eb.logger.Debugw(fmt.Sprintf("Booting with %d keys", len(eb.enabledAddresses)), "keys", eb.enabledAddresses)
} else {
eb.logger.Warnf("Chain %s does not have any keys, no transactions will be sent on this chain", eb.chainID.String())
}
eb.chStop = make(chan struct{})
eb.wg = sync.WaitGroup{}
eb.wg.Add(len(eb.enabledAddresses))
eb.triggers = make(map[ADDR]chan struct{})
for _, addr := range eb.enabledAddresses {
triggerCh := make(chan struct{}, 1)
eb.triggers[addr] = triggerCh
go eb.monitorTxs(addr, triggerCh)
}
eb.wg.Add(1)
go eb.txInsertTriggerer()
eb.isStarted = true
return nil
}
// Close closes the Broadcaster
func (eb *Broadcaster[CHAIN_ID, HEAD, ADDR, TX_HASH, BLOCK_HASH, SEQ, FEE]) Close() error {
return eb.StopOnce("Broadcaster", func() error {
return eb.closeInternal()
})
}
func (eb *Broadcaster[CHAIN_ID, HEAD, ADDR, TX_HASH, BLOCK_HASH, SEQ, FEE]) closeInternal() error {
eb.initSync.Lock()
defer eb.initSync.Unlock()
if !eb.isStarted {
return errors.Wrap(utils.ErrAlreadyStopped, "Broadcaster is not started")
}
if eb.txInsertListener != nil {
eb.txInsertListener.Close()
}
close(eb.chStop)
eb.wg.Wait()
eb.isStarted = false
return nil
}
func (eb *Broadcaster[CHAIN_ID, HEAD, ADDR, TX_HASH, BLOCK_HASH, SEQ, FEE]) SetResumeCallback(callback ResumeCallback) {
eb.resumeCallback = callback
}
func (eb *Broadcaster[CHAIN_ID, HEAD, ADDR, TX_HASH, BLOCK_HASH, SEQ, FEE]) Name() string {
return eb.logger.Name()
}
func (eb *Broadcaster[CHAIN_ID, HEAD, ADDR, TX_HASH, BLOCK_HASH, SEQ, FEE]) HealthReport() map[string]error {
return map[string]error{eb.Name(): eb.StartStopOnce.Healthy()}
}
// Trigger forces the monitor for a particular address to recheck for new txes
// Logs error and does nothing if address was not registered on startup
func (eb *Broadcaster[CHAIN_ID, HEAD, ADDR, TX_HASH, BLOCK_HASH, SEQ, FEE]) Trigger(addr ADDR) {
if eb.isStarted {
triggerCh, exists := eb.triggers[addr]
if !exists {
// ignoring trigger for address which is not registered with this Broadcaster
return
}
select {
case triggerCh <- struct{}{}:
default:
}
} else {
eb.logger.Debugf("Unstarted; ignoring trigger for %s", addr)
}
}
func (eb *Broadcaster[CHAIN_ID, HEAD, ADDR, TX_HASH, BLOCK_HASH, SEQ, FEE]) txInsertTriggerer() {
defer eb.wg.Done()
for {
select {
case ev, ok := <-eb.txInsertListener.Events():
if !ok {
eb.logger.Debug("txInsertListener channel closed, exiting trigger loop")
return
}
addr, err := eb.parseAddr(ev.Payload)
if err != nil {
eb.logger.Errorw("failed to parse address in trigger", "err", err)
continue
}
eb.Trigger(addr)
case <-eb.chStop:
return
}
}
}
func (eb *Broadcaster[CHAIN_ID, HEAD, ADDR, TX_HASH, BLOCK_HASH, SEQ, FEE]) newSequenceSyncBackoff() backoff.Backoff {
return backoff.Backoff{
Min: 100 * time.Millisecond,
Max: 5 * time.Second,
Jitter: true,
}
}
func (eb *Broadcaster[CHAIN_ID, HEAD, ADDR, TX_HASH, BLOCK_HASH, SEQ, FEE]) newResendBackoff() backoff.Backoff {
return backoff.Backoff{
Min: 1 * time.Second,
Max: 15 * time.Second,
Jitter: true,
}
}
func (eb *Broadcaster[CHAIN_ID, HEAD, ADDR, TX_HASH, BLOCK_HASH, SEQ, FEE]) monitorTxs(addr ADDR, triggerCh chan struct{}) {
defer eb.wg.Done()
ctx, cancel := eb.chStop.NewCtx()
defer cancel()
if eb.autoSyncSequence {
eb.logger.Debugw("Auto-syncing sequence", "address", addr.String())
eb.SyncSequence(ctx, addr)
if ctx.Err() != nil {
return
}
} else {
eb.logger.Debugw("Skipping sequence auto-sync", "address", addr.String())
}
// errorRetryCh allows retry on exponential backoff in case of timeout or
// other unknown error
var errorRetryCh <-chan time.Time
bf := eb.newResendBackoff()
for {
pollDBTimer := time.NewTimer(utils.WithJitter(eb.listenerConfig.FallbackPollInterval()))
retryable, err := eb.processUnstartedTxsImpl(ctx, addr)
if err != nil {
eb.logger.Errorw("Error occurred while handling tx queue in ProcessUnstartedTxs", "err", err)
}
// On retryable errors we implement exponential backoff retries. This
// handles intermittent connectivity, remote RPC races, timing issues etc
if retryable {
pollDBTimer.Reset(utils.WithJitter(eb.listenerConfig.FallbackPollInterval()))
errorRetryCh = time.After(bf.Duration())
} else {
bf = eb.newResendBackoff()
errorRetryCh = nil
}
select {
case <-ctx.Done():
// NOTE: See: https://godoc.org/time#Timer.Stop for an explanation of this pattern
if !pollDBTimer.Stop() {
<-pollDBTimer.C
}
return
case <-triggerCh:
// tx was inserted
if !pollDBTimer.Stop() {
<-pollDBTimer.C
}
continue
case <-pollDBTimer.C:
// DB poller timed out
continue
case <-errorRetryCh:
// Error backoff period reached
continue
}
}
}
// syncSequence tries to sync the key sequence, retrying indefinitely until success
func (eb *Broadcaster[CHAIN_ID, HEAD, ADDR, TX_HASH, BLOCK_HASH, SEQ, FEE]) SyncSequence(ctx context.Context, addr ADDR) {
sequenceSyncRetryBackoff := eb.newSequenceSyncBackoff()
if err := eb.sequenceSyncer.Sync(ctx, addr); err != nil {
// Enter retry loop with backoff
var attempt int
eb.logger.Errorw("Failed to sync with on-chain sequence", "address", addr.String(), "attempt", attempt, "err", err)
for {
select {
case <-eb.chStop:
return
case <-time.After(sequenceSyncRetryBackoff.Duration()):
attempt++
if err := eb.sequenceSyncer.Sync(ctx, addr); err != nil {
if attempt > 5 {
eb.logger.Criticalw("Failed to sync with on-chain sequence", "address", addr.String(), "attempt", attempt, "err", err)
eb.SvcErrBuffer.Append(err)
} else {
eb.logger.Warnw("Failed to sync with on-chain sequence", "address", addr.String(), "attempt", attempt, "err", err)
}
continue
}
return
}
}
}
}
// ProcessUnstartedTxs picks up and handles all txes in the queue
// revive:disable:error-return
func (eb *Broadcaster[CHAIN_ID, HEAD, ADDR, TX_HASH, BLOCK_HASH, SEQ, FEE]) ProcessUnstartedTxs(ctx context.Context, addr ADDR) (retryable bool, err error) {
return eb.processUnstartedTxs(ctx, addr)
}
// NOTE: This MUST NOT be run concurrently for the same address or it could
// result in undefined state or deadlocks.
// First handle any in_progress transactions left over from last time.
// Then keep looking up unstarted transactions and processing them until there are none remaining.
func (eb *Broadcaster[CHAIN_ID, HEAD, ADDR, TX_HASH, BLOCK_HASH, SEQ, FEE]) processUnstartedTxs(ctx context.Context, fromAddress ADDR) (retryable bool, err error) {
var n uint
mark := time.Now()
defer func() {
if n > 0 {
eb.logger.Debugw("Finished processUnstartedTxs", "address", fromAddress, "time", time.Since(mark), "n", n, "id", "broadcaster")
}
}()
err, retryable = eb.handleAnyInProgressTx(ctx, fromAddress)
if err != nil {
return retryable, errors.Wrap(err, "processUnstartedTxs failed on handleAnyInProgressTx")
}
for {
maxInFlightTransactions := eb.txConfig.MaxInFlight()
if maxInFlightTransactions > 0 {
nUnconfirmed, err := eb.txStore.CountUnconfirmedTransactions(fromAddress, eb.chainID)
if err != nil {
return true, errors.Wrap(err, "CountUnconfirmedTransactions failed")
}
if nUnconfirmed >= maxInFlightTransactions {
nUnstarted, err := eb.txStore.CountUnstartedTransactions(fromAddress, eb.chainID)
if err != nil {
return true, errors.Wrap(err, "CountUnstartedTransactions failed")
}
eb.logger.Warnw(fmt.Sprintf(`Transaction throttling; %d transactions in-flight and %d unstarted transactions pending (maximum number of in-flight transactions is %d per key). %s`, nUnconfirmed, nUnstarted, maxInFlightTransactions, label.MaxInFlightTransactionsWarning), "maxInFlightTransactions", maxInFlightTransactions, "nUnconfirmed", nUnconfirmed, "nUnstarted", nUnstarted)
select {
case <-time.After(InFlightTransactionRecheckInterval):
case <-ctx.Done():
return false, context.Cause(ctx)
}
continue
}
}
etx, err := eb.nextUnstartedTransactionWithSequence(fromAddress)
if err != nil {
return true, errors.Wrap(err, "processUnstartedTxs failed on nextUnstartedTransactionWithSequence")
}
if etx == nil {
return false, nil
}
n++
var a txmgrtypes.TxAttempt[CHAIN_ID, ADDR, TX_HASH, BLOCK_HASH, SEQ, FEE]
var retryable bool
a, _, _, retryable, err = eb.NewTxAttempt(ctx, *etx, eb.logger)
if err != nil {
return retryable, errors.Wrap(err, "processUnstartedTxs failed on NewAttempt")
}
if err := eb.txStore.UpdateTxUnstartedToInProgress(etx, &a); errors.Is(err, ErrTxRemoved) {
eb.logger.Debugw("tx removed", "txID", etx.ID, "subject", etx.Subject)
continue
} else if err != nil {
return true, errors.Wrap(err, "processUnstartedTxs failed on UpdateTxUnstartedToInProgress")
}
if err, retryable := eb.handleInProgressTx(ctx, *etx, a, time.Now()); err != nil {
return retryable, errors.Wrap(err, "processUnstartedTxs failed on handleAnyInProgressTx")
}
}
}
// handleInProgressTx checks if there is any transaction
// in_progress and if so, finishes the job
func (eb *Broadcaster[CHAIN_ID, HEAD, ADDR, TX_HASH, BLOCK_HASH, SEQ, FEE]) handleAnyInProgressTx(ctx context.Context, fromAddress ADDR) (err error, retryable bool) {
etx, err := eb.txStore.GetTxInProgress(fromAddress)
if err != nil {
return errors.Wrap(err, "handleAnyInProgressTx failed"), true
}
if etx != nil {
if err, retryable := eb.handleInProgressTx(ctx, *etx, etx.TxAttempts[0], etx.CreatedAt); err != nil {
return errors.Wrap(err, "handleAnyInProgressTx failed"), retryable
}
}
return nil, false
}
// This function is used to pass the queryer from the txmgr to the keystore.
// It is inevitable we have to pass the queryer because we need the keystate's next sequence to be incremented
// atomically alongside the transition from `in_progress` to `broadcast` so it is ready for the next transaction
func (eb *Broadcaster[CHAIN_ID, HEAD, ADDR, TX_HASH, BLOCK_HASH, SEQ, FEE]) incrementNextSequenceAtomic(tx pg.Queryer, etx txmgrtypes.Tx[CHAIN_ID, ADDR, TX_HASH, BLOCK_HASH, SEQ, FEE]) error {
if err := eb.incrementNextSequence(etx.FromAddress, *etx.Sequence, pg.WithQueryer(tx)); err != nil {
return errors.Wrap(err, "saveUnconfirmed failed")
}
return nil
}
// There can be at most one in_progress transaction per address.
// Here we complete the job that we didn't finish last time.
func (eb *Broadcaster[CHAIN_ID, HEAD, ADDR, TX_HASH, BLOCK_HASH, SEQ, FEE]) handleInProgressTx(ctx context.Context, etx txmgrtypes.Tx[CHAIN_ID, ADDR, TX_HASH, BLOCK_HASH, SEQ, FEE], attempt txmgrtypes.TxAttempt[CHAIN_ID, ADDR, TX_HASH, BLOCK_HASH, SEQ, FEE], initialBroadcastAt time.Time) (error, bool) {
if etx.State != TxInProgress {
return errors.Errorf("invariant violation: expected transaction %v to be in_progress, it was %s", etx.ID, etx.State), false
}
checkerSpec, err := etx.GetChecker()
if err != nil {
return errors.Wrap(err, "parsing transmit checker"), false
}
checker, err := eb.checkerFactory.BuildChecker(checkerSpec)
if err != nil {
return errors.Wrap(err, "building transmit checker"), false
}
lgr := etx.GetLogger(eb.logger.With("fee", attempt.TxFee))
// If the transmit check does not complete within the timeout, the transaction will be sent
// anyway.
checkCtx, cancel := context.WithTimeout(ctx, TransmitCheckTimeout)
defer cancel()
err = checker.Check(checkCtx, lgr, etx, attempt)
if errors.Is(err, context.Canceled) {
lgr.Warn("Transmission checker timed out, sending anyway")
} else if err != nil {
etx.Error = null.StringFrom(err.Error())
lgr.Warnw("Transmission checker failed, fatally erroring transaction.", "err", err)
return eb.saveFatallyErroredTransaction(lgr, &etx), true
}
cancel()
lgr.Infow("Sending transaction", "txAttemptID", attempt.ID, "txHash", attempt.Hash, "err", err, "meta", etx.Meta, "feeLimit", etx.FeeLimit, "attempt", attempt, "etx", etx)
errType, err := eb.client.SendTransactionReturnCode(ctx, etx, attempt, lgr)
if errType != clienttypes.Fatal {
etx.InitialBroadcastAt = &initialBroadcastAt
etx.BroadcastAt = &initialBroadcastAt
}
switch errType {
case clienttypes.Fatal:
eb.SvcErrBuffer.Append(err)
etx.Error = null.StringFrom(err.Error())
return eb.saveFatallyErroredTransaction(lgr, &etx), true
case clienttypes.TransactionAlreadyKnown:
fallthrough
case clienttypes.Successful:
// Either the transaction was successful or one of the following four scenarios happened:
//
// SCENARIO 1
//
// This is resuming a previous crashed run. In this scenario, it is
// likely that our previous transaction was the one who was confirmed,
// in which case we hand it off to the confirmer to get the
// receipt.
//
// SCENARIO 2
//
// It is also possible that an external wallet can have messed with the
// account and sent a transaction on this sequence.
//
// In this case, the onus is on the node operator since this is
// explicitly unsupported.
//
// If it turns out to have been an external wallet, we will never get a
// receipt for this transaction and it will eventually be marked as
// errored.
//
// The end result is that we will NOT SEND a transaction for this
// sequence.
//
// SCENARIO 3
//
// The network client can be assumed to have at-least-once delivery
// behavior. It is possible that the client could have already
// sent this exact same transaction even if this is our first time
// calling SendTransaction().
//
// SCENARIO 4 (most likely)
//
// A sendonly node got the transaction in first.
//
// In all scenarios, the correct thing to do is assume success for now
// and hand off to the confirmer to get the receipt (or mark as
// failed).
observeTimeUntilBroadcast(eb.chainID, etx.CreatedAt, time.Now())
return eb.txStore.UpdateTxAttemptInProgressToBroadcast(&etx, attempt, txmgrtypes.TxAttemptBroadcast, func(tx pg.Queryer) error {
return eb.incrementNextSequenceAtomic(tx, etx)
}), true
case clienttypes.Underpriced:
return eb.tryAgainBumpingGas(ctx, lgr, err, etx, attempt, initialBroadcastAt)
case clienttypes.InsufficientFunds:
// NOTE: This bails out of the entire cycle and essentially "blocks" on
// any transaction that gets insufficient_funds. This is OK if a
// transaction with a large VALUE blocks because this always comes last
// in the processing list.
// If it blocks because of a transaction that is expensive due to large
// gas limit, we could have smaller transactions "above" it that could
// theoretically be sent, but will instead be blocked.
eb.SvcErrBuffer.Append(err)
fallthrough
case clienttypes.Retryable:
return err, true
case clienttypes.FeeOutOfValidRange:
return eb.tryAgainWithNewEstimation(ctx, lgr, err, etx, attempt, initialBroadcastAt)
case clienttypes.Unsupported:
return err, false
case clienttypes.ExceedsMaxFee:
// Broadcaster: Note that we may have broadcast to multiple nodes and had it
// accepted by one of them! It is not guaranteed that all nodes share
// the same tx fee cap. That is why we must treat this as an unknown
// error that may have been confirmed.
// If there is only one RPC node, or all RPC nodes have the same
// configured cap, this transaction will get stuck and keep repeating
// forever until the issue is resolved.
lgr.Criticalw(`RPC node rejected this tx as outside Fee Cap`)
fallthrough
default:
// Every error that doesn't fall under one of the above categories will be treated as Unknown.
fallthrough
case clienttypes.Unknown:
eb.SvcErrBuffer.Append(err)
lgr.Criticalw(`Unknown error occurred while handling tx queue in ProcessUnstartedTxs. This chain/RPC client may not be supported. `+
`Urgent resolution required, Chainlink is currently operating in a degraded state and may miss transactions`, "err", err, "etx", etx, "attempt", attempt)
nextSequence, e := eb.client.PendingSequenceAt(ctx, etx.FromAddress)
if e != nil {
err = multierr.Combine(e, err)
return errors.Wrapf(err, "failed to fetch latest pending sequence after encountering unknown RPC error while sending transaction"), true
}
if nextSequence.Int64() > (*etx.Sequence).Int64() {
// Despite the error, the RPC node considers the previously sent
// transaction to have been accepted. In this case, the right thing to
// do is assume success and hand off to Confirmer
return eb.txStore.UpdateTxAttemptInProgressToBroadcast(&etx, attempt, txmgrtypes.TxAttemptBroadcast, func(tx pg.Queryer) error {
return eb.incrementNextSequenceAtomic(tx, etx)
}), true
}
// Either the unknown error prevented the transaction from being mined, or
// it has not yet propagated to the mempool, or there is some race on the
// remote RPC.
//
// In all cases, the best thing we can do is go into a retry loop and keep
// trying to send the transaction over again.
return errors.Wrapf(err, "retryable error while sending transaction %s (tx ID %d)", attempt.Hash.String(), etx.ID), true
}
}
// Finds next transaction in the queue, assigns a sequence, and moves it to "in_progress" state ready for broadcast.
// Returns nil if no transactions are in queue
func (eb *Broadcaster[CHAIN_ID, HEAD, ADDR, TX_HASH, BLOCK_HASH, SEQ, FEE]) nextUnstartedTransactionWithSequence(fromAddress ADDR) (*txmgrtypes.Tx[CHAIN_ID, ADDR, TX_HASH, BLOCK_HASH, SEQ, FEE], error) {
etx := &txmgrtypes.Tx[CHAIN_ID, ADDR, TX_HASH, BLOCK_HASH, SEQ, FEE]{}
if err := eb.txStore.FindNextUnstartedTransactionFromAddress(etx, fromAddress, eb.chainID); err != nil {
if errors.Is(err, sql.ErrNoRows) {
// Finish. No more transactions left to process. Hoorah!
return nil, nil
}
return nil, errors.Wrap(err, "findNextUnstartedTransactionFromAddress failed")
}
sequence, err := eb.getNextSequence(etx.FromAddress)
if err != nil {
return nil, err
}
etx.Sequence = &sequence
return etx, nil
}
func (eb *Broadcaster[CHAIN_ID, HEAD, ADDR, TX_HASH, BLOCK_HASH, SEQ, FEE]) tryAgainBumpingGas(ctx context.Context, lgr logger.Logger, txError error, etx txmgrtypes.Tx[CHAIN_ID, ADDR, TX_HASH, BLOCK_HASH, SEQ, FEE], attempt txmgrtypes.TxAttempt[CHAIN_ID, ADDR, TX_HASH, BLOCK_HASH, SEQ, FEE], initialBroadcastAt time.Time) (err error, retryable bool) {
lgr.With(
"sendError", txError,
"attemptFee", attempt.TxFee,
"maxGasPriceConfig", eb.feeConfig.MaxFeePrice(),
).Errorf("attempt fee %v was rejected by the node for being too low. "+
"Node returned: '%s'. "+
"Will bump and retry. ACTION REQUIRED: This is a configuration error. "+
"Consider increasing FeeEstimator.PriceDefault (current value: %s)",
attempt.TxFee, txError.Error(), eb.feeConfig.FeePriceDefault())
replacementAttempt, bumpedFee, bumpedFeeLimit, retryable, err := eb.NewBumpTxAttempt(ctx, etx, attempt, nil, lgr)
if err != nil {
return errors.Wrap(err, "tryAgainBumpFee failed"), retryable
}
return eb.saveTryAgainAttempt(ctx, lgr, etx, attempt, replacementAttempt, initialBroadcastAt, bumpedFee, bumpedFeeLimit)
}
func (eb *Broadcaster[CHAIN_ID, HEAD, ADDR, TX_HASH, BLOCK_HASH, SEQ, FEE]) tryAgainWithNewEstimation(ctx context.Context, lgr logger.Logger, txError error, etx txmgrtypes.Tx[CHAIN_ID, ADDR, TX_HASH, BLOCK_HASH, SEQ, FEE], attempt txmgrtypes.TxAttempt[CHAIN_ID, ADDR, TX_HASH, BLOCK_HASH, SEQ, FEE], initialBroadcastAt time.Time) (err error, retryable bool) {
if attempt.TxType == 0x2 {
err = errors.Errorf("re-estimation is not supported for EIP-1559 transactions. Node returned error: %v. This is a bug", txError.Error())
logger.Sugared(eb.logger).AssumptionViolation(err.Error())
return err, false
}
replacementAttempt, fee, feeLimit, retryable, err := eb.NewTxAttemptWithType(ctx, etx, lgr, attempt.TxType, feetypes.OptForceRefetch)
if err != nil {
return errors.Wrap(err, "tryAgainWithNewEstimation failed to build new attempt"), retryable
}
lgr.Warnw("L2 rejected transaction due to incorrect fee, re-estimated and will try again",
"etxID", etx.ID, "err", err, "newGasPrice", fee, "newGasLimit", feeLimit)
return eb.saveTryAgainAttempt(ctx, lgr, etx, attempt, replacementAttempt, initialBroadcastAt, fee, feeLimit)
}
func (eb *Broadcaster[CHAIN_ID, HEAD, ADDR, TX_HASH, BLOCK_HASH, SEQ, FEE]) saveTryAgainAttempt(ctx context.Context, lgr logger.Logger, etx txmgrtypes.Tx[CHAIN_ID, ADDR, TX_HASH, BLOCK_HASH, SEQ, FEE], attempt txmgrtypes.TxAttempt[CHAIN_ID, ADDR, TX_HASH, BLOCK_HASH, SEQ, FEE], replacementAttempt txmgrtypes.TxAttempt[CHAIN_ID, ADDR, TX_HASH, BLOCK_HASH, SEQ, FEE], initialBroadcastAt time.Time, newFee FEE, newFeeLimit uint32) (err error, retyrable bool) {
if err = eb.txStore.SaveReplacementInProgressAttempt(attempt, &replacementAttempt); err != nil {
return errors.Wrap(err, "tryAgainWithNewFee failed"), true
}
lgr.Debugw("Bumped fee on initial send", "oldFee", attempt.TxFee.String(), "newFee", newFee.String(), "newFeeLimit", newFeeLimit)
return eb.handleInProgressTx(ctx, etx, replacementAttempt, initialBroadcastAt)
}
func (eb *Broadcaster[CHAIN_ID, HEAD, ADDR, TX_HASH, BLOCK_HASH, SEQ, FEE]) saveFatallyErroredTransaction(lgr logger.Logger, etx *txmgrtypes.Tx[CHAIN_ID, ADDR, TX_HASH, BLOCK_HASH, SEQ, FEE]) error {
if etx.State != TxInProgress {
return errors.Errorf("can only transition to fatal_error from in_progress, transaction is currently %s", etx.State)
}
if !etx.Error.Valid {
return errors.New("expected error field to be set")
}
// NOTE: It's simpler to not do this transactionally for now (would require
// refactoring pipeline runner resume to use postgres events)
//
// There is a very tiny possibility of the following:
//
// 1. We get a fatal error on the tx, resuming the pipeline with error
// 2. Crash or failure during persist of fatal errored tx
// 3. On the subsequent run the tx somehow succeeds and we save it as successful
//
// Now we have an errored pipeline even though the tx succeeded. This case
// is relatively benign and probably nobody will ever run into it in
// practice, but something to be aware of.
if etx.PipelineTaskRunID.Valid && eb.resumeCallback != nil {
err := eb.resumeCallback(etx.PipelineTaskRunID.UUID, nil, errors.Errorf("fatal error while sending transaction: %s", etx.Error.String))
if errors.Is(err, sql.ErrNoRows) {
lgr.Debugw("callback missing or already resumed", "etxID", etx.ID)
} else if err != nil {
return errors.Wrap(err, "failed to resume pipeline")
}
}
return eb.txStore.UpdateTxFatalError(etx)
}
func (eb *Broadcaster[CHAIN_ID, HEAD, ADDR, TX_HASH, BLOCK_HASH, SEQ, FEE]) getNextSequence(address ADDR) (sequence SEQ, err error) {
return eb.ks.NextSequence(address, eb.chainID)
}
func (eb *Broadcaster[CHAIN_ID, HEAD, ADDR, TX_HASH, BLOCK_HASH, SEQ, FEE]) incrementNextSequence(address ADDR, currentSequence SEQ, qopts ...pg.QOpt) error {
return eb.ks.IncrementNextSequence(address, eb.chainID, currentSequence, qopts...)
}
func observeTimeUntilBroadcast[CHAIN_ID types.ID](chainID CHAIN_ID, createdAt, broadcastAt time.Time) {
duration := float64(broadcastAt.Sub(createdAt))
promTimeUntilBroadcast.WithLabelValues(chainID.String()).Observe(duration)
}
|
@hironytic
質問に答えていくと、Podの種を作ってくれる。
$ pod lib create [pod name]
↓ 実は初めて実行してみた😓
$ pod lib create Piyo
Cloning `https://github.com/CocoaPods/pod-template.git` into `Piyo`.
Configuring Piyo template.
------------------------------
To get you started we need to ask a few questions, this should only take a minute.
2015-07-04 21:25:09.912 defaults[82243:2285211]
The domain/default pair of (org.cocoapods.pod-template, HasRunbefore) does not exist
If this is your first time we recommend running through with the guide:
- http://guides.cocoapods.org/making/using-pod-lib-create.html
( hold cmd and double click links to open in a browser. )
Press return to continue.
What language do you want to use?? [ ObjC / Swift ]
>
objc
Would you like to include a demo application with your library? [ Yes / No ]
>
yes
Which testing frameworks will you use? [ Specta / Kiwi / None ]
>
specta
Would you like to do view based testing? [ Yes / No ]
>
yes
What is your class prefix?
> PY
Running pod install on your new library.
Analyzing dependencies
CocoaPods 0.38.0.beta.1 is available.
To update use: `gem install cocoapods --pre`
[!] This is a test version we'd love you to try.
For more information see http://blog.cocoapods.org
and the CHANGELOG for this version http://git.io/BaH8pQ.
Fetching podspec for `Piyo` from `../`
Downloading dependencies
Installing Expecta (1.0.0)
Installing Expecta+Snapshots (1.3.4)
Installing FBSnapshotTestCase (1.8.1)
Installing Piyo (0.1.0)
Installing Specta (1.0.2)
Generating Pods project
Integrating client project
[!] Please close any current Xcode sessions and use `Piyo.xcworkspace` for this project from now on.
Ace! you're ready to go!
We will start you off by opening your project in Xcode
open 'Piyo/Example/Piyo.xcworkspace'
To learn more about the template see `https://github.com/CocoaPods/pod-template.git`.
To learn more about creating a new pod, see `http://guides.cocoapods.org/making/making-a-cocoapod`.
|
IGEM:PennState/Labbook/GalenLynch/2007-6-13
June 13th, 2007: 9:30-5:00
* Ordered primers
* Assayed Enzymes to determine functionality
Galen Lynch's Lab Notebook
|
Muichiro Tokito
Muichirou Tokitou is a Demon Hunter and the Mist Pillar of the Demon Killing Corps. .
Personality
Natural Abilities
Swordsmanship
Breath of Mist Style
* 1) First form: Hanging sky, distant mist - A straightforward thrust attack.
Trivia
The "Mu"(無) is Tokitou's first name, Muichiro, contains the same kanji for "In" in "Infinity" (無限).
|
Whispering Pines Fire Rescue Department (North Carolina)
Fire Station - 16 Hardee Lane
* Engine 511 - 2012 Spartan Metro Star / Toyne (1500/1000)
|
# Picard
This is a singularity image to deploy the bamtools software.
This will produce a Singularity image (suitable for running in a cluster environment) using [https://hub.docker.com/r/broadinstitute/picard/](https://hub.docker.com/r/broadinstitute/picard/). We do this by way of a bootstrap file for the Docker image.
## 1. Install Singularity
Instructions can be found on the [singularity site](https://singularityware.github.io).
## 2. Bootstrap the image
sudo singularity create --size 4000 bamtools.img
sudo singularity bootstrap bamtools.img Singularity
## 3. Run commands
How to access the bamtools runtime executable?
./bamtools.img [args] ...
|
"""
Utility functions for making visuals.
"""
import os
import tempfile
import scipy.misc
from collections import namedtuple
from mpl_toolkits.axes_grid1 import make_axes_locatable
import numpy as np
# import seaborn as sns
import matplotlib.pyplot as plt
# The first dimension of values correspond to the x axis
HeatMap = namedtuple("HeatMap", ['values', 'x_values', 'y_values', 'info'])
VectorField = namedtuple("VectorField",
['values', 'dx_values', 'dy_values', 'x_values',
'y_values', 'info'])
def make_heat_map(eval_func, x_bounds, y_bounds, *, resolution=10, info=None, batch=False):
"""
:param eval_func: eval_func(x, y) -> value
:param x_bounds:
:param y_bounds:
:param resolution:
:param info: A dictionary to save inside the vector field
:return:
"""
if info is None:
info = {}
x_values = np.linspace(*x_bounds, num=resolution)
y_values = np.linspace(*y_bounds, num=resolution)
map = np.zeros((resolution, resolution))
if batch:
inputs = []
for i in range(resolution):
for j in range(resolution):
inputs.append([x_values[i], y_values[j]])
inputs = np.array(inputs)
map = eval_func(inputs).reshape((resolution, resolution))
else:
for i in range(resolution):
for j in range(resolution):
map[i, j] = eval_func(x_values[i], y_values[j])
return HeatMap(map, x_values, y_values, info)
def make_vector_field(eval_func, x_bounds, y_bounds, *, resolution=10,
info=None):
"""
:param eval_func: eval_func(x, y) -> value, dx, dy
:param x_bounds:
:param y_bounds:
:param resolution:
:param info: A dictionary to save inside the vector field
:return:
"""
if info is None:
info = {}
x_values = np.linspace(*x_bounds, num=resolution)
y_values = np.linspace(*y_bounds, num=resolution)
values = np.zeros((resolution, resolution))
dx_values = np.zeros((resolution, resolution))
dy_values = np.zeros((resolution, resolution))
for x in range(resolution):
for y in range(resolution):
value, dx, dy = eval_func(x_values[x], y_values[y])
values[x, y] = value
dx_values[x, y] = dx
dy_values[x, y] = dy
return VectorField(
values=values,
dx_values=dx_values,
dy_values=dy_values,
x_values=x_values,
y_values=y_values,
info=info,
)
def plot_heatmap(heatmap, fig=None, ax=None, legend_axis=None):
if fig is None:
fig = plt.gcf()
if ax is None:
ax = plt.gca()
p, x, y, _ = heatmap
im = ax.imshow(
np.swapaxes(p, 0, 1), # imshow uses first axis as y-axis
extent=[x.min(), x.max(), y.min(), y.max()],
cmap=plt.get_cmap('plasma'),
interpolation='nearest',
aspect='auto',
origin='bottom', # <-- Important! By default top left is (0, 0)
)
if legend_axis is None:
divider = make_axes_locatable(ax)
legend_axis = divider.append_axes('right', size='5%', pad=0.05)
fig.colorbar(im, cax=legend_axis, orientation='vertical')
return im, legend_axis
def plot_vector_field(fig, ax, vector_field, skip_rate=1):
skip = (slice(None, None, skip_rate), slice(None, None, skip_rate))
p, dx, dy, x, y, _ = vector_field
im = ax.imshow(
np.swapaxes(p, 0, 1), # imshow uses first axis as y-axis
extent=[x.min(), x.max(), y.min(), y.max()],
cmap=plt.get_cmap('plasma'),
interpolation='nearest',
aspect='auto',
origin='bottom', # <-- Important! By default top left is (0, 0)
)
x, y = np.meshgrid(x, y)
ax.quiver(x[skip], y[skip], dx[skip], dy[skip])
divider = make_axes_locatable(ax)
cax = divider.append_axes('right', size='5%', pad=0.05)
fig.colorbar(im, cax=cax, orientation='vertical')
def save_image(fig=None, fname=None):
if fname is None:
fname = tempfile.TemporaryFile()
if fig is not None:
fig.savefig(fname)
else:
plt.savefig(fname, format='png')
plt.close('all')
fname.seek(0)
img = scipy.misc.imread(fname)
fname.close()
return img
def sliding_mean(data_array, window=5):
"""
Smooth data with a sliding mean
:param data_array:
:param window:
:return:
"""
data_array = np.array(data_array)
new_list = []
for i in range(len(data_array)):
indices = list(range(max(i - window + 1, 0),
min(i + window + 1, len(data_array))))
avg = 0
for j in indices:
avg += data_array[j]
avg /= float(len(indices))
new_list.append(avg)
return np.array(new_list)
def average_every_n_elements(arr, n):
"""
Compress the array by a factor of n.
output[i] = average of input[n*i] to input[n*(i+1)]
:param arr:
:param n:
:return:
"""
return np.nanmean(
np.pad(
arr.astype(float),
(0, n - arr.size % n),
mode='constant',
constant_values=np.NaN,
).reshape(-1, n),
axis=1
)
def gif(filename, array, fps=10):
"""Creates a gif given a stack of images using moviepy
Notes
-----
works with current Github version of moviepy (not the pip version)
https://github.com/Zulko/moviepy/commit/d4c9c37bc88261d8ed8b5d9b7c317d13b2cdf62e
Usage
-----
>>> X = randn(100, 64, 64)
>>> gif('test.gif', X)
Parameters
----------
filename : string
The filename of the gif to write to
array : array_like
A numpy array that contains a sequence of images
fps : int
frames per second (default: 10)
"""
from moviepy.video.io.ImageSequenceClip import ImageSequenceClip
# ensure that the file has the .gif extension
fname, _ = os.path.splitext(filename)
filename = fname + '.gif'
# copy into the color dimension if the images are black and white
if array.ndim == 3:
array = array[..., np.newaxis] * np.ones(3)
# make the moviepy clip
clip = ImageSequenceClip(list(array), fps=fps)
clip.write_gif(filename, fps=fps)
return clip
|
Jeff Frick here with the Cube with John Furrier. We are on the ground at AT&T Park. We've come to where the action is. We've come to the home of innovation. What do you think, John? Last time we were here was April 2nd. The baseball season is halfway done, so we've come for an update. Yeah, I mean, I think AT&T Park and the Giants represent innovation there in the heart of San Francisco. San Francisco is booming with technology, and they're not strangers to technology, Jeff. We've been here before talking to Bill, CIO, and they have their acts together on technology. It's fun because who doesn't love baseball and sports and tech at the same time? So it's so much fun to be on the ground getting all the action. We've got some great interviews lined up. So we're going to make our way around the field. We've got some great guests, like I said, Bill, Shlal, the CIO of the Giants is going to kick things off, but there's a lot of great innovations that are going on here at AT&T. So keep it tuned and we'll be right back with our next guest for the short break.
|
import { rAF } from '../-private/concurrency-helpers';
import Motion, { type BaseOptions } from '../-private/motion';
import type Sprite from '../-private/sprite';
import Tween, { type TweenLike } from '../-private/tween';
import linear from '../easings/linear';
export default function opacity(
sprite: Sprite,
opts: Partial<OpacityOptions> = {},
) {
return new Opacity(sprite, opts).run();
}
/**
Animates in a sprite from 0% to 100% opacity.
```js
for (let sprite of insertedSprites) {
fadeIn(sprite)
}
```
@function fadeIn
@param {Sprite} sprite
@return {Motion}
*/
export function fadeIn(sprite: Sprite, opts: Partial<OpacityOptions> = {}) {
let innerOpts = Object.assign(
{
to: 1,
},
opts,
);
return opacity(sprite, innerOpts);
}
/**
Animates out a sprite from 100% to 0% opacity.
```js
for (let sprite of removedSprites) {
fadeOut(sprite)
}
```
@function fadeOut
@param {Sprite} sprite
@return {Motion}
*/
export function fadeOut(sprite: Sprite, opts: Partial<OpacityOptions> = {}) {
let innerOpts = Object.assign(
{
to: 0,
},
opts,
);
return opacity(sprite, innerOpts);
}
interface OpacityOptions extends BaseOptions {
from: number;
to: number;
easing: (time: number) => number;
}
export class Opacity extends Motion<OpacityOptions> {
prior: Opacity | null | undefined = null;
tween: TweenLike | null = null;
interrupted(motions: Motion[]) {
// SAFTEY: We just checked the types
this.prior = motions.find((m) => m instanceof this.constructor) as
| Opacity
| undefined;
}
/*
This motion defines "duration" as the time it takes to go all the
way from 0% to 100% (or 100% to 0%). So motions between values
closer than that take proportionately less time.
*/
*animate() {
let { sprite, duration, opts } = this;
let to =
opts.to != null
? opts.to
: sprite.finalComputedStyle != null
? parseFloat(sprite.finalComputedStyle.opacity)
: 1;
let from;
if (this.prior) {
let prior: Opacity = this.prior;
prior.assertHasTween();
// when we're interrupting a prior opacity motion, we always
// take its value as our starting point, regardless of whether
// the user set a "from" option.
from = prior.tween.currentValue;
} else {
// otherwise we start at the user-provided option, the sprite's
// found initial opacity, or zero, in that priority order.
from =
opts.from != null
? opts.from
: sprite.initialComputedStyle != null
? parseFloat(sprite.initialComputedStyle.opacity)
: 0;
}
let proportionalDuration = Math.abs(from - to) * duration;
this.tween = new Tween(
from,
to,
proportionalDuration,
this.opts.easing !== undefined ? this.opts.easing : linear,
);
while (!this.tween.done) {
sprite.applyStyles({
opacity: `${this.tween.currentValue}`,
});
yield rAF();
}
}
assertHasTween(): asserts this is OpacityWithTween {
if (!this.tween) {
throw new Error(`motion does not have tween`);
}
}
}
interface OpacityWithTween extends Opacity {
tween: TweenLike;
}
|
Spraying apparatus
March l, 1955 E. o. NoR Rls SPRAYING APPARATUS 3 sheets-sheet 1 Filed June 23, 1953 III Il HIIIIIIII INVENToR. vw/Mw 0. /i/af Q/e/S March 1, 1955 E.`o. NoR Rls SPRAYING APPARATUS 3 Sheets-Sheet 2 Filed June 23, 1953 TTORNE Y March 1, 1955 E. o. NQRRIS SPRAYING APPARATUS 5 Sheets-Sheet 5 Filed' June 2s, 195s United States Patent O M This invention relates to spraying apparatus of the centrifugal type and more particularly to a centrifugal sprayer having a rotary distributor adapted to project a sprayable material from its periphery in the form of a finely divided spray.
An object of the invention is to provide a distributor of the above type having novel and improved operating.
characteristics.
Another object is to provide a centrifugal spray gun of the all-position type having no station ary external surfaces on which the spray material can collect.
Another object is to provide a centrifugal spray gun 2,703,257 Patented Mar. 1, 1955 a rotary case 85 having an outer flange 86 forming an annular channel 87 adapted to receive the spray material and to cause the material to form an annular lm in the channel 87 due to centrifugal action as the case 8S is rotated at high speed. The iia nge 86 has a central opening 88 through which the spray passes and a sharp edge 89 for conning the spray to a well defined path. The
l shaped outer surface 95 to throw case 85 is shown as made in two parts bolted together by bolts 90, and with an annular lip 91 to cause the material to ow into the channel 87. It may, however, be made in one piece if desired.
The outer surface of the housing 80 is shown as provided with annular grooves 92 and the case 85 carries an annular ange 93 having a surface 94 which extends over the grooves 92 to form a liquid seal, and with a coneoutwardly any spray material that hits or settles on the same. The iia nge 93 is also secured by the bolts 90.
The housing 80 is formed with an enlarged end flange 98 to which a gear case 99 is bolted by bolts 100. One
` end of the shaft 82 projects into the gear case 99 and of the above type which is adapted to project a spray i in a substantially axial direction.
Varlous other objects and advantages will be apparent as the nature of the invention is more fully disclosed.
This application is a continuation-in-part of my co pending application Serial No. 287,789, filed May 14, 1952, on Spraying Apparatus.
The spray gun embodying the present invention is of the type having a case which rotates at a speed to maintain centrifugally a film of the spray material around its entire periphery. A rotary distributor is supported to rotate freely about a fixed axis within the rotary case and is provided at its periphery with fins which dip into the hlm of spray material within the rotating case, and are driven thereby to cause the distributor to rotate at a speed to pick up and discharge the spray material centrifugally. The distributor is mounted on a fixed but adjustable bracket within the rotary case and is positioned for the discharge of the spray through the open end of the case. The relationship between the axis of the distributor and the axis of the rotating case depends upon the contour of the ns. In one embodiment the fins are shown as annular with the distributor mounted to rotate about an axis which is slightly inclined with respect to the axis of the rotary case. In another embodiment the fins are shown as heli cally inclined, similar to turbine blades and the distributor as mounted to rotate about an axis which is normal to the axis of the rotary case but oset with respect thereto so that the spray is dis j charged substantially axially of the case.
The nature of the invention will be better understood from the following description, taken in connection with the accompanying drawings in which specific embodiments have been set forth for purposes of illustration.
In the drawings:
Fig. 1 is a longitudinal section through a spray gun embodying the present invention;
t Fig. 2 is a partial side elevation of a spray gun illustrating a further embodiment of the invention;
Fig. 3 is a transverse section through the spray gun of Fig. 2 taken on the line 3-3 of Fig. 2;
Fig. 4 is a longitudinal section taken on the line 4 4 of Fig. 2 but on a larger scale;
Fig. 5 is a section taken on the line 5-5 of Fig. 4 showing the. mounting for the distributor; t
Fig. 6 is an enlarged detail view showing the relation of the distributor to the rotary case;
Fig. 7 is an enlarged detail sectional view of a distributor vane; and
Fig. 8 is a sectional view showing the mounting for the distributor bracket, taken on the line 8-8 of Fig. 3.
Referring t`o the drawings, the spray gun of Fig. 1 is shown as having a fixed `housing formed with an internal bore S1 in which a hollow shaft 82 is journal led by ball bearings 83 and 84. The hollow shaft 82 carries carries a gear 101 which is secured by a nut 102. The
gear 101 meshes with a gear 103 carried on a shaft 104 which is journaled by ball bearings 105 in a bushing 106. This bushing is held in a boss 107 in a wall 108 of the gear case by set screws 109. The end of the shaft 104 projects into a coupling 110 and is adapted to be coupled to a driving shaft (not shown) by which the rotary case 85 is driven.
A station ary shaft 112 extends through the hollow shaft 82 and through a boss 113 in the wall 108. The station ary shaft 112 is clamped in the boss 113 by a flange 114 -on the shaft 112 and a nut 115 threaded onto the shaft 112.
A bracket 115a is attached to the end of the shaft 112 within the rotary case and is attached by a screw 116. The bracket a carries a hollow stud 117 in which the hub 118 of a distributor 119 is journaled by ball bearings 120. The distributor 119 is formed with a cone-shaped liang e 120a carrying fins 121 terminating in a conical surface and with an inner iia nge 122 extending over the stud 117 to shield the same from the spray. A pin 123 secures the distributor 119 to the hub 118 and is arranged to permit removal or replacement of the distributor.
The fins 121 are positioned to dip into the peripheral film of spray material in the channel 87 and are driven thereby to pick up material from the advancing film and to discharge the same as a fine spray. The distributor is mounted with its axis inclined to the axis of the case 85 so that the fins 121 rotate in a plane which extends through the central opening in the case 85. Hence a portion of the spray from the distributor passes through this opening and the remainder is intercepted by the walls of the case 85 and returned to the peripheral film therein for res praying. In this way all of the material fed to the case 85 is eventually sprayed outwardly in a directed confined spray path. The axis of the distributor may also be tilted with respect to the diametrical plane through the case which contains such distributor so that the peripheral edges of the fins 121 intercept the film in the case 85 at an angle to the direction of movement of the film at the point of interception, so as to avoid forming grooved areas in said film and also so as to agitate the film and prevent stratification thereof due to centrifugal separation.
The station ary shaft 112 is formed with an axial bore 125 communicating with radical bore 126 in the bracket 115a which in turn communicates with a bore 127 opening at 129 into the case 85 opposite an annular groove 129 therein for feeding spray material to the case 85. A coupling 130 is provided on the end of the station ary shaft'112 to receive a hose or pipe carrying spray material under a pressure to force the same through said bores into the rotary case 85. A flange 132 and groove 133 on the bracket 115 and in the case 85 provides a v seal to permit spray material entering the space between -l into the rotating4 case 8 5 where it forms an annular film in the channel 87 from which it is picked up and discharged'as an atomized spray bythe fins 121 of the distributor 119 which is driven at high speed by the rotating film into which it dips. The spray is thus thrown out of 'the opening 88 in the rotating case 85 along a well defined path. The spray from the distributor which is intercepted by the case 85 returns to the peripheral film for res praying v until all of the material fed to the ease has been sprayed.
Referring to the embodiment of Figs, 2 to 8 the housing 80 and associated parts, including the gear drive, are similar to those above described. In this embodiment a hollow shaft is mounted to rotate in bearings 1,1 within the housing 80. The shaft 10 carries a rotating case 12 which is generally similar to the case 85 of Fig'. 1 and the inner surface o f which has a concave peripheral wall forming a channel to receive a film 13'of the spray material.V The case 12 terminates in a flange 14 having a sharp edge 15 defining an axial opening through which the spray is ejected. A bail le ring 16 having a pair of inwardly projecting flanges 17 and 18 is disposed on a shoulder 19 formed in the case 1,2 near the open end thereof. The flanges 17 and 18 project inwardly and terminate in sharp edges to form a cut off for the spray cone.
In order to return to the case 12 any spray material that may collect on the flanges 17 and 18, the baffle ring 16 is provided with a row of peripherally spaced outwardly inclined passages 20 and with holes 21 which extend into said passages from the inner face of the ring 16. The holes 21 and the passages 20 are so formed that the sprayed material is returned by centrifugal force into the interior of the case 12. A skirt 40, carried by the case 12, shields the housing 80 and bearing 11 from the sprayed material.
A st ation ary shaft 22 corresponding to the shaft 112. of Fig. 1 having a bore 23 is disposed within the hollow shaft 10. The shaft 22 is provided near its forward end with helical grooves 24 which are inclined in a direction tg prevent material from feeding upwardly along said s a t.
A hollow pin 25 is threaded into the forward end of the shaft 22. The pin 25 has a bore 26 communicating with the bore 23 of the shaft 22. A hollow ring 2 7 carrying a feed spout 28 is seated on the pin 25.r The spout 28 communicates through the hollow ring 27 and a passage 29 with the bore 26 of the pin 25, and is provided with a discharge end 30 which is disposed adjacent the film 13 of spray material in the rotary case 12 and extends in the direction of rotation ofl the case so that material is fed to the case in the direction of the moving film 13. A bushing 31, disposed on the pin 25 carries a bracket 32 terminating in a pin 33 on which the distributor 34 is journaled. A flange 35 is disposed on the pin 2 5 between the bushing 31 and the end of the shaft l 22. The flange 35 has an annular groove 36 in which an annular flange 37 of thel case 12 is disposed to prevent the spray in the case 12 from feeding into the space, between the station ary shaft 22 and the rotating shaft 10. A packing material 38, such as soft metal, is disposed between the outer surface of the flange 35 and the inner surface of the rotating shaft 10 to effect a further seal. The bushing 31 is fixed to the flange 35 by a pin 5,4 and the flange 35 is'xed to the shaft l22'by ap in 5 5 so asV ti ov fix the position of the4 distributor; 34 with respeptrto the station ary' shaft22. Tho difrbutor position can. bo, adjusted by adjusting the angular position of the shaft 2 2. The'ring 27 and bushing 31`are provided with contacting conical surfaces which4 are clamped together between theY head 39 of the pin 3:5 and the end' of 'the station ary shaft- 2,2. V Thus they relative positions of,` theV brac ket 32 andthe spout 28 can be'adjustecl by v loosening the pin 25. The pin 33 (Fig. 5) carries a bushing 4 1fon which is journaled a hub.` 42 of' the rotary distributor 34 having a sot f heli call'y inoliod'ils. 44 disposed and arranged. in
a`manner similar to turbine blades andn mounted to, dip into the moving film 13 within the case 1 2. The fins 44 are shown asV coated with a thin coating 45 of flame coated tungsten carbide l or similar hardI material which has a rough outer surface. The hard coating, increases the life of the fins and the rough surface thereof ir np'roves their pick-up and` spraying characteristics. A thrust bearing 47 is disposed` between the end of the pin sandi he 11111142.,
'A split'irig 48 is disposed in a groove 49 ofthe hub 42 and engages the end of the bushing 41 to hold the distributofo the pin 33. The bracket 32 is provided with an axial flange 50 running in an angular recess 51 in the distributor 34 to shield the bearing surface from the spray material.
The fins 44 as shown are provided with sharp edges 52 on the side engaged by the advancing film 13. This edge 52 dips into the film and causes a quantity of the material therefrom to be picked up on the leading surface of the fin from which it is discharged centrifugally as the distributor rotates. In this embodiment the bracket 32 is adjusted by suitable manipulation of the bushing 31 so that the distributor rotates about an axis which is substantially normal to the axis of the shaft 10. The helical contour of the fins 44 which dip into the advancing film 13 causes the distributor to rotate in a counterclockwise direction as seen in Fig. 4. Material from the film 13 is thus scooped up by the fins 44 and discharged centrifugally as a Spray cone 53.
In the form shown the flange 17 constitutes a cut off for the outer edge of the spray cone, that is the lefthand edge as seen in Fig. 4, and the flange 18 constitutes a eut off for the opposite edge. The two flanges are provided because the tangents to the rotating distributor at the two edges of the cone extend at different angles with respect to the axis of the shaft 10. In this way the spray cone is centered with respect to the spray opening in the rotary case.
The distributor is so designed that the periphery thereof is substantially tangent to the axis of the shaft 10 so that the cone of spray 53 is projected axially of this shaft and outwardly through the opening in the end of the case 12,.
Although specific embodiments of the invention have been shown f or purposes of illustration it is to be understood that the invention may be applied to various uses and that changes and modifications thereof may be made as will be apparent to a person skilled in the art.
What is claimed is:
l. A spraying de vice comprising a rotary case having an axial spray opening and a concave peripheral wall forming a channel to retain a spray-forming material, driving means including a hollow shaft for rotating said case to form centrifugally an annular film of said material in said channel, a fixed shaft disposed within said hollow shaft and extending axially into said rotary case, a bracket mounted on said fixed shaft within said rotary case, a rotary distributor mounted for free rotation on said bracket and so disposed that l its periphery dips into said film of material and is driven thereby, said distributor rotating in a plane which extends through said axial spray opening.
2. A spraying d e vice comprising a rotary case having an axial spray opening and a concave peripheral wall forming al channel to retain a spray-forming material, driving means including a hollow shaft for rotating said case to form centrifugally an annular film of said material in said channel, a fixed shaft disposed within said hollow shaft and extending axially into said rotary case, a bracket mounted on said fixed shaft within said rotary case, a rotary distributor mounted for free rotation on said bracket and so disposed that its periphery dips into said film 0 f material and is driven thereby, said distributor rotating in a plane which extends through v said axial spray opening,Y and means for adjusting the position of said bracket l for thereby adjusting the relationship between said distributor andj said case.
3- A Spraying de vice.. Comprising aV rotary caso having an axial Spray opening and a concave Peripheral wall forming a channel to retain a spray-forming material, driving means including av hollow shaft for rotating said case to form centrifugally an annular film of said material in said v channel, a fixed shaft disposed within said l hollow shaft and extending axially into said rotary case, a bracket mounted on said fixed, shaft within said, rotary case, a rotary distributor mounted for rotation on said bracket and so disposed that its, periphery dips into said film of material and is driven thereby, said distributor rotating in a plane which extends through said axial spray opening, said fixed shaft having an axial passage through which said spray-forming material` is fed for spraying.
4. A spraying de vice comprising a rotary case having an, axial. Spray 'opening anda conoaye peripheral wall.
forming a, Qhannl. to, A retain a Spray-forming material,
driving means including a hollow shaft for rotating said' ease to form centrifugally an annular ii lm of said material in said channel, a lixed shaft disposed within said hollow shaft and extending axially into said rotary case, a bracket mounted on said fixed shaft within said rotary case, a rotary distributor mounted for rotation on said bracket and so disposed that its periphery dips into said film of material and is driven thereby, said distributor rotating in a plane which extends through said axial spray opening, said fixed shaft having an axial passage through which said spray-forming material is fed, and a discharge spout disposed in said rotary case and communicating with said passage for discharging said material into said case, said discharge spout having an end disposed adjacent said annular film and extending in the direction of movement of said film.
5. In a spraying apparatus, a rotary collecting case having an annular peripheral wall forming a channel for receiving a spray-forming material and having an axial spray-opening, means supplying a spray-forming material to said case, means driving said case to cause the material to form a rotating peripheral layer on said wall, a distributor comprising a rotor having heli cally disposed fins extending substantially radially from the periphery thereof, means rotatably mounting said rotor in said case with the peripheral edges of said fins dipping into said peripheral layer of material whereby the tins pick-up and are driven by said material, the plane of rotation of said rotor intersecting said spray opening whereby the material which is discharged centrifugally from said tins is projected outwardly through said spray opening.
A spraying apparatus as set forth in claim 5 in which said fins are formed with a sharp edge on the side which dips into the advancing film of spray-forming material.
7. In a spraying apparatus, a rotary collecting case having an annular peripheral wall forming a channel for receiving a spray-forming material and having an axial spray-opening, means supplying a spray-forming material to said case, means driving said case to cause the material to form a rotating peripheral layer on said wall, a distributor comprising a rotor having heli cally disposed tins extending substantially radially from the periphery thereof, means rotatably mounting said rotor in said case with the peripheral edges of said fins dipping into said peripheral layer of material whereby the tins pick-up and are driven by said material, said rotor being mounted with its axis of rotation substantially normal to the axs of rotation of said case, the plane of rotation of said rotor intersecting said spray opening whereby the material which is discharged centrifugally from said fins is projected outwardly through said spray opening.
S. In a spraying apparatus, a rotary collecting case having an annular peripheral wall forming a channel for receiving a spray forming material and having an axial spray opening, means supplying a spray-forming material to said case, means driving said case to cause the material to form a rotating peripheral layer on said wall, a distributor` comprising a rotor having peripheral tins, means rotatably mounting said rotor in said case with said fins dipping into said peripheral layer of material whereby the fins pick up and are driven by said material, said tins having a rough surface coating of a hard material to improve the pick-up and wear characteristics thereof, the plane of rotation of said rotor intersecting said spray opening whereby the material which is discharged centrifugally from said ins is projected outwardly through said spray opening.
9. In a spraying apparatus, a rotary collecting case having an annular peripheral wall forming a channel for receiving a spray-forming material and having an axial `spray opening, means supplying a spray-forming material to said case, means driving said case to cause the material to form a rotating peripheral layer on said wall, a distributor comprising a rotor having peripheral fins, means rotatably mounting said rotor in said case with said ns dipping into said peripheral layer of material whereby the ns pick-up and are driven by said material, said tins having a rough surface coating of tungsten carbide to improve the pick-up and Wear characteristics thereof, the plane of rotation of said rotor intersecting said spray opening whereby the material which is discharged centrifugally from said fins is projected outwardly through said spray opening.
References Cited in the le of this patent UNITED STATES PATENTS Re. 19,374 Butterworth Nov. 20, 1934 2,545,487 Norris Mar. 20, 1951 2,550,714 Norris May l, 1951
|
package com.sopa89.mereessentials.commands;
import org.bukkit.command.Command;
import org.bukkit.command.CommandExecutor;
import org.bukkit.command.CommandSender;
import org.bukkit.entity.Player;
import com.sopa89.mereessentials.Main;
import com.sopa89.mereessentials.utils.Utils;
public class FlyCommand implements CommandExecutor
{
private Main plugin;
public FlyCommand(Main plugin)
{
this.plugin = plugin;
plugin.getCommand("fly").setExecutor(this);;
}
@Override
public boolean onCommand(CommandSender sender, Command cmd, String label, String[] args)
{
if(!(sender instanceof Player) && args.length <= 0)
{
sender.sendMessage(Utils.chat(plugin.getConfig().getString("console_error_message")));
return true;
}
if(sender.hasPermission("mereessentials.fly"))
{
if(args.length >= 1)
{
Player target = sender.getServer().getPlayer(args[0]);
if(target != null)
{
if(target.getAllowFlight())
{
target.setAllowFlight(false);
target.setFlying(false);
target.sendMessage(Utils.chat(plugin.getConfig().getString("FlyCommand.fly_disabled")));
return true;
}
else
{
target.setAllowFlight(true);
target.setFlying(true);
target.sendMessage(Utils.chat(plugin.getConfig().getString("FlyCommand.fly_enabled")));
return true;
}
}
else
{
sender.sendMessage(Utils.chat(plugin.getConfig().getString("player_not_found_message")));
}
}
else
{
Player p = (Player) sender;
if(p.getAllowFlight())
{
p.setAllowFlight(false);
p.setFlying(false);
p.sendMessage(Utils.chat(plugin.getConfig().getString("FlyCommand.fly_disabled")));
return true;
}
else
{
p.setAllowFlight(true);
p.setFlying(true);
p.sendMessage(Utils.chat(plugin.getConfig().getString("FlyCommand.fly_enabled")));
return true;
}
}
}
else
{
sender.sendMessage(Utils.chat(plugin.getConfig().getString("no_perm_message")));
}
return false;
}
}
|
[Congressional Record (Bound Edition), Volume 158 (2012), Part 8]
[House]
[Pages 11095-11096]
PUBLIC BILLS AND RESOLUTIONS
Under clause 2 of rule XII, public bills and resolutions of the
following titles were introduced and severally referred, as follows:
By Mr. FLAKE (for himself and Mr. Chaffetz):
H.R. 6098. A bill to amend the Federal Crop Insurance Act
to immediately reduce crop insurance premium subsidy rates
from the higher subsidies provided since the Agricultural
Risk Protection Act of 2000; to the Committee on Agriculture.
By Mr. CARNAHAN (for himself, Mr. Polis, Mr. Honda, and
Mr. Hinchey):
H.R. 6099. A bill to amend the Public Works and Economic
Development Act of 1965 with respect to grants for economic
adjustment, and for other purposes; to the Committee on
Transportation and Infrastructure, and in addition to the
Committee on Financial Services, for a period to be
subsequently determined by the Speaker, in each case for
consideration of such provisions as fall within the
jurisdiction of the committee concerned.
By Mr. BRALEY of Iowa:
H.R. 6100. A bill to amend the Internal Revenue Code of
1986 to provide a temporary extension of the 2001 and 2003
tax cuts for the middle class, and for other purposes; to the
Committee on Ways and Means.
By Ms. CHU (for herself, Mr. Rangel, Ms. Loretta
Sanchez of California, Mr. Filner, and Mr. Jones):
H.R. 6101. A bill to amend title 38, United States Code, to
improve educational counseling opportunities for veterans,
and for other purposes; to the Committee on Veterans'
Affairs, and in addition to the Committee on Armed Services,
for a period to be subsequently determined by the Speaker, in
each case for consideration of such provisions as fall within
the jurisdiction of the committee concerned.
By Mr. GERLACH (for himself and Mr. Kind):
H.R. 6102. A bill to amend the Internal Revenue Code of
1986 to provide tax relief for small businesses, and for
other purposes; to the Committee on Ways and Means.
By Ms. HOCHUL:
H.R. 6103. A bill to amend title XI of the Social Security
Act to increase fines and penalties for Medicare fraud to
augment Medicare fraud enforcement activities, such as the
Health Care Fraud and Enforcement Action Team (HEAT) program;
to the Committee on Ways and Means, and in addition to the
Committee on Energy and Commerce, for a period to be
subsequently determined by the Speaker, in each case for
consideration of such provisions as fall within the
jurisdiction of the committee concerned.
By Mr. RICHMOND:
H.R. 6104. A bill to provide a temporary extension for the
middle class of certain tax relief enacted in 2001, 2003, and
2009; to the Committee on Ways and Means.
By Mr. STIVERS (for himself and Mr. Carson of Indiana):
H.R. 6105. A bill to amend the Federal Home Loan Bank Act
to allow non-Federally insured credit unions to become
members of a Federal Home Loan Bank; to the Committee on
Financial Services.
____________________
|
Backup Android SQLite database on Windows Azure Cloud
I'm trying to find a way to backup Sqlite database from my android app to a cloud Windows Azure. I have just implemented the method that copy the sqlite database in a folder of external sd card, now I would backup this file to a cloud.
I have seen this official guide:
https://azure.microsoft.com/it-it/documentation/articles/mobile-services-android-get-started/
but I don't understand if it is possible. Have you a guide or a faq?
Thanks :)
One option is to send your file to Azure blob storage: http://azure.microsoft.com/en-us/services/storage/blobs/
There's an Android SDK available: https://github.com/Azure/azure-storage-android/
|
Estimating the Unit Costs of Healthcare Service Delivery in India: Addressing Information Gaps for Price Setting and Health Technology Assessment
Background India’s flagship National Health insurance programme (AB-PMJAY) requires accurate cost information for evidence-based decision-making, strategic purchasing of health services and setting reimbursement rates. To address the challenge of limited health service cost data, this study used econometric methods to identify determinants of cost and estimate unit costs for each Indian state. Methods Using data from 81 facilities in six states, models were developed for inpatient and outpatient services at primary and secondary level public health facilities. A best-fit unit cost function was identified using guided stepwise regression and combined with data on health service infrastructure and utilisation to predict state-level unit costs. Results Health service utilisation had the greatest influence on unit cost, while number of beds, facility level and the state were also good predictors. For district hospitals, predicted cost per inpatient admission ranged from 1028 (313–3429) Indian Rupees (INR) to 4499 (1451–14,159) INR and cost per outpatient visit ranged from 91 (44–196) INR to 657 (339–1337) INR, across the states. For community healthcare centres and primary healthcare centres, cost per admission ranged from 412 (148–1151) INR to 3677 (1359–10,055) INR and cost per outpatient visit ranged from 96 (50–187) INR to 429 (217–844) INR. Conclusion This is the first time cost estimates for inpatient admissions and outpatient visits for all states have been estimated using standardised data. The model demonstrates the usefulness of such an approach in the Indian context to help inform health technology assessment, budgeting and forecasting, as well as differential pricing, and could be applied to similar country contexts where cost data are limited. Electronic supplementary material The online version of this article (10.1007/s40258-020-00566-9) contains supplementary material, which is available to authorized users.
Background
The costs of healthcare service delivery underpin many important policy decisions-from questions of affordability, to making choices between different technologies and innovations, to setting prices of health services. Many countries, and in particular, low-and middle-income countries, suffer from a lack of information in this area, creating an information vacuum that leads to opaque policy decisions and cost escalation in health services [1,2]. As the modus operandi of public health systems involves the purchasing of services by the state using public money, and as international pressure to move towards systems of Universal Health Care (UHC) coverage grows, governments without cost information are increasingly vulnerable in their ability to engage in strategic purchasing of health services. Cost information allows governments to be better-equipped as price setters and allows for informed decisions around the allocation of resources between different healthcare services and technologies to ensure value for money.
The challenges arising from limited healthcare cost information are magnified in the highly complex and fragmented Indian health system, where public services are purchased and delivered by a mix of both private and state providers. India operates under a model of fiscal federalism, where health is primarily the responsibility of state governments. There are a multitude of state insurance schemes in operation across the country that have been introduced to tackle the inequitable access to healthcare [3]. At the central level, the first national government taxfunded scheme for the poor and vulnerable was initiated in 2008. In 2018, the national government then launched the Ayushman Bharat-Prime Minister's Jan Arogya Yojana (AB-PMJAY), a tax-funded national insurance programme that aims to subsume earlier national and state schemes and to provide healthcare cover of 500,000 Indian Rupees (INR) for over 500 million poor beneficiaries [4]. Despite these different schemes, to date, state governments have not used systematic, evidence-based approaches to setting prices [5]. Until recently, the process of setting prices under AB-PMJAY and other insurance schemes has been somewhat haphazard, relying on surveys of insurance claims data and interviews with experts. The government explained the severity of the problem in 2018: "we don't have costing studies in India" [6]. While the latter statement exaggerates the issue, there are limited studies, the majority of which focussed on a single disease, technology or site. Data on private expenditures are regularly collected by the National Sample Survey Office, but this is limited to patient expenditures on healthcare and cannot be broken down fully by disease or condition [7,8]. Insurance claims data from 22 different government-funded schemes have also been collated into a single database; however, these estimates reflect prices agreed by tender and do not represent the cost of production [7,9]. More recently, the availability of production cost data for the public sector has begun to grow with individual costing studies that have been carried out to explore the cost-effectiveness of different technologies as well as a series of primary costing studies [10][11][12][13][14][15][16][17][18][19]. However, the paucity of cost information remains a significant fact within the Indian health system [7,20].
Compounding the general lack of cost information, a further challenge in the practical application of cost data for price setting and health technology assessment in India is the vast heterogeneity in costs of service delivery across different types of providers, levels of the system, states and geographical settings. Previously published cost studies have highlighted the variation in healthcare costs within the Indian health system [10-13, 20, 21]. This variation in unit costs arises as a result of supply factors due to different methods of production, ownership (public or private), differences in prices and wage rates as well as demand factors such as epidemiology, population density and socio-economic status of the local population [22][23][24]. Moreover, India's size and federal governance structure with different modes of financing, delivery and purchasing of healthcare have given rise to the view that there is scope for 'differential pricing' across settings when setting reimbursement rates.
With sufficient data, it is possible to explore the determinants of cost using a statistical cost function and thereby enable the prediction of costs for different settings. The advantage of using a cost function approach is the ability to interpret the coefficients on key variables such as scale, geography and other factors and explore the impact of these factors that might drive cost variations [25][26][27][28]. At the global level, the World Health Organization (WHO) has used such an approach to predict country specific unit costs [29,30]. In India, efforts, including those by the present authors, towards estimating costs and understanding the cost structures of healthcare facilities have begun [11][12][13][14][15][16][17][18]21]. While these first studies have provided cost data for different levels of the health system, they have been undertaken in a limited number of facilities and states. Nonetheless, these data form the richest and most accurate source of cost data for publicly delivered health services in India to date and can be used to understand better what drives cost differences between facilities using statistical cost function analyses. Using these data and an average cost function approach, the aim of this paper is to develop models to identify the key drivers of unit costs of inpatient (IP) and outpatient (OP) services at primary and secondary level public health facilities in India for use in healthcare decision-making and to demonstrate the use of such a model in the prediction of unit costs for each Indian state.
Development of the Models
The aims of the models are to predict unit costs of healthcare services for each state in India, at different service volumes by nature of service delivery (IP and OP care), and identify the degree to which other factors influence average costs. Unit costs are dependent on the total costs of input resources consumed (numerator) and output in terms of services provided (denominator). Total costs can broadly be divided into the 'hotel' components, i.e. human workforce, capital resources (like building and equipment) and overheads, and those associated with specific treatments, i.e. the costs of medicine, consumables and diagnostics, and are dependent on the beneficiaries. Hotel costs generally comprise 70-80% of hospital costs [13,19,31]. Other costs, i.e. those of medicines, consumables and diagnostics, are subject to different types of market influences than hotel type services, with patients typically contributing to a large share of these inputs in India [32]. These costs tend to be variable so that the average cost remains constant as volume of services changes. Hotel costs are more fixed in nature, with average costs varying with scale as well as other characteristics that might shape the production of a particular service. The cost function presented here is therefore designed to predict the hotel costs component of the average cost.
Our starting point is the WHO CHOICE refined model for predicting national-level unit costs (version 2) 2017/18 [30]. This model regresses unit costs against a set of explanatory variables such that: where UC is unit cost, X i are the explanatory variables, 0 and 1…n are the estimated parameters, and e is the error term. Natural logs of both the unit cost and independent variables are used because of the inherently skewed nature of cost data. In addition, the equation can then be estimated using ordinary least squares methods, and the coefficients can be interpreted as elasticities [29].
An average cost function approach was chosen. In this approach, the unit cost is regressed against a set of independent variables, selected based on theory and previous empirical findings. Resource inputs and their prices are included to identify the influence of each, e.g. is it the price or quantity of doctors that explains more of the unit cost? Further, explanatory factors such as volume of services, geographical location, capacity utilisation, quality and the nature of the healthcare market can also be included [23,25,[33][34][35]. As average cost is largely explained by volume of activity, the model needs to include output as an independent variable to isolate and identify the influence of each of the other variables. Careful attention then needs to be paid to potential multi-collinearity. Sensitivity analyses were run to verify the inclusion of output as an independent variable and the choice of average cost over total cost function.
Within a hospital the standard set of outputs are the OP visits, IP admissions or IP days. To estimate unit costs for a particular service within a large production unit, a regression model can be run separately for each different service based on the assumption that the production relationship between different services at any single facility is constant. In this case, separate models are needed for IP care and OP care.
Data
Cost data are taken from the cost data surveys of 81 public sector facilities across six states in India: Punjab, Haryana, Tamil Nadu, Odisha, Himachal Pradesh and Kerala [11][12][13]19]. The cost dataset comprised healthcare facility costs at district hospitals (DHs), community healthcare centres (CHC) and primary healthcare centres (PHC) (the sampling methods are described in Appendix 1; see the electronic supplementary material). Economic cost data were collected from a provider perspective using a mixed methodology. The first round of data collection took place in 2013; the second round took place in 2016. The costing methodology followed standard principles [36,37], and the standardised methodology has been published elsewhere [11,13,19]. Costs from the first round were adjusted to 2015-2016 prices, in line with the second round, using a correction factor of 1.46 (source: https ://www.calcu lator stack .com/infla tion-calcu lator -india .php). 1 In line with service provision at the different health system levels, CHCs and DHs were included in the IP care model analysis. For the OP care model, the analysis included DHs, CHCs and PHCs.
Two adjustments were made to the cost dataset to address data issues. First, for the OP model estimation, 14 PHCs reported a value of zero for the number of beds. As number of beds was used as the measure of capital stock, and due to the need to take logs, we would have had to exclude these facilities from the OP model. To address this, we assumed the value 1 for the number of beds-as the lowest level of capital stock-for these facilities. Second, one CHC reported no admissions in the reference year and therefore was excluded from the IP analysis and the OP analysis runs where the admissions variable was required (models including capacity utilisation). No ethical clearance was required for this analysis of secondary data.
Model Specification
A range of different variables were considered for inclusion in the models based on a combination of theoretical considerations and previous cost models (for example, see [22,23,30,31,38,39]). To identify the best specification, we used a combination of guided stepwise linear regression informed by Table 1 and the perspective of a potential user of the model. Potential users attempting to generate a facility-or state-specific unit cost could include policy makers at the central or state level, academics and health technology assessment professionals. As data availability is limited in India, in particular, access to data on wages and human resources and even facility infrastructure variables, it was important to factor data accessibility into the decision around which variables to include in the final model. The variables considered included the outputs of each service category, prices and quantities of labour, proxy of capital and any other significant inputs into production, as well as supply-side factors that might lead to cost variation [22]. Importantly, the models needed to be constructed using readily accessible data to enable a user to predict costs for their settings.
Following Serje et al. four categories of labour should be considered [40]: professional, technical/auxiliary, clerks/ secretaries and physical labourers. However, our data only allowed distinction between three categories: doctors, medical support staff (nurses/technicians/pharmacists) and other support staff. The capital stock can be represented by the number of beds at the facility for both IP and OP services. Number of beds gives an indication of the relative capital stock even where IP beds are equal to zero. Outputs used are hospitalisations for the IP model and OP visits for the OP model.
To account for the influence of supply-side factors, we included the level of health facility, capacity utilisation and state-level per capita health expenditure as well as two proxy variables to represent quality and the nature of the healthcare market. These proxy variables are the state health index, which reflects a combination of health outcomes, governance and inputs to the health sector [41], and the government "Aspirational District Programme" index, a composite index of socio-economic progress, health and education sector performance and basic infrastructure indicators [42]. The full set of variables considered for the models is listed and defined in Table 2. The best-fit models were then selected based on both statistical and theoretical considerations.
Model Selection
A best-fit model was then chosen for each of the OP and IP cost functions for the prediction of unit costs at DHs, CHCs and PHCs for all states in India. Base models for prediction were selected based on the trade-off between the data requirements and high predictive power of the model in terms of adjusted R-squared. First, models with multicollinearity [variance influence factor (VIF) scores > 10] were excluded [44]. Subsequently models were listed in order of the adjusted R-squared. Starting with the model with the highest score, the models were assessed for their suitability to be used in the state-level predictions, according to data availability and ability to interpret the coefficient on the independent variable. The first model to fit these criteria was selected for the state-level cost predictions.
Cost Predictions
The mean values and the 2.5% and 97.5% uncertainty limits for IP admissions and OP visits at DHs and CHCs were estimated for all states in India using the best-fit models. State-level data were identified for each of the variables using national-level data sources including the National Health Profile, the National Sample Survey Office (NSSO) "Health in India" report (71st round) and, where data were unavailable at the national level, state-specific health system websites [8,45]. There were no centrally compiled data on hospitalisations and OP visits as reported by facilities. These state-level variables were therefore estimated from NSSO household survey data on hospitalisations and seeking medical care in the public sector combined with reported institutional deliveries and maternal and child healthcare visits. The summary data on hospitalisations and OP visits and the methodology for their estimation is provided in supplementary appendices 2 and 3 (see the electronic supplementary material). The predicted unit cost generated from the models is a median value due to the log transformations. This was adjusted to the arithmetic mean by applying a smearing factor [30,46]. Uncertainty intervals around the predicted Table 2 List and definition of variables considered for each of the models ALOS average length of stay, DH district hospital, CHC community healthcare centre, INR Indian Rupees, PHC primary healthcare centre a Number of beds is a good reflection of the working capital of a facility. In addition, the variable is an easier variable to obtain for anyone wishing to use the model for further estimations b 14 PHCs did not report data on number of beds. As this was being used as a proxy for capital and because of the need to take logs, we assumed this value to be 1 where actual beds = 0 c To reflect the demand side, an additional variable capturing condition-specific data at the state or facility level would have been preferable, but standardised, reliable and good-quality data of this type are difficult to obtain for potential users of the model d For one CHC, no routine inpatient admission happened in the reference year, so capacity utilisation for the inpatient model could not be calculated and this CHC was excluded from the analysis [43] values were also constructed by first generating a random sample of 1000 based on the mean and standard error of each of the coefficients in the model and extracting the values at the 2.5th and 97.5th percentiles. Versions of the models will further be made available online for individual users to estimate unit costs for their own settings (see https ://www. healt hecon omics .pgisp h.in/costi ng_web/index .php).
Model Validation
The cost prediction models were validated by using data and results from preliminary findings of an additional costing study funded by the Government of India 2 [47]. Actual costs and the explanatory variables were extracted from the primary data collected from the sampled health facilities for this study. The explanatory variables were used to predict the facility unit cost estimates based on the state prediction models. The predicted cost estimates were then compared with the actual unit cost estimates generated as part of the national costing study. The study results are yet unpublished, so identifiers of the health facilities were kept confidential.
Model Outcomes
Descriptive statistics for each model are reported in Table 3. The mean unit cost for an IP hospital admission across the sample was 2563 INR, and the mean number of hospitalisations per facility in a year was 10,467. The mean cost of an OP consultation was 113 INR, with an average of 76,129 consultations in a year. DHs represented 37.5% of the IP sample (DHs and CHCs only) and 19% of the OP sample (which also includes PHCs). Table 4a and b present the results of the best-fit models for the IP and OP sample. The supplementary material reports on all the model runs that were carried out (Appendix 4; see the electronic supplementary material). The majority of the models had good predictive power with an adjusted R-squared greater than 0.7 both with and without inclusion of price and labour variables. The coefficients made theoretical and logical sense with relationships in the hypothesised direction and most were significant. Capacity utilisation was excluded from the reported models due to the presence of multi-collinearity. When output was excluded, the adjusted R-squared was found to be lower than when it was included, and a model run with total cost as the dependent variable yielded similar results to the average cost function (see Appendix 6). In the case of the IP cost estimation, the models that included information on quantity and price of labour performed better than those without-with adjusted R-squared scores all greater than 0.9. For the OP model, models that included the labour variables suffered from multi-collinearity. The models that included district ranking as a variable performed better than those that did not, but due to the difficulty of interpreting the coefficient on a ranking and the impracticality of using this for state-level estimates, these models were not considered for state-level estimations. The output variable has the greatest influence on the unit cost for both IP and OP care. Capital, in the form of number of beds, and the facility level were both important and significant predictors of unit cost. The state health index was significant for some models, but had a relatively smaller influence on the overall unit cost.
Cost Predictions
Model C (see Table 4a and b) was used to predict the statelevel unit costs. Model C was chosen as it fits both the criterion of access to data on each variable at the health facility or state/district health departments and statistically had a good R-squared value. The state-level estimates for IP admissions and OP visits at DHs and CHCs are shown in Fig. 1 In the validation exercise, the actual unit costs from the sampled facilities all fall within the uncertainty intervals for the unit costs predicted by the models. The difference between the actual and predicted costs ranged from − 2 to 62% in the IP model and − 90% to 30% for the OP model (see Table 5).
Discussion
This paper has described the development of a set of models to predict the mean hotel costs of IP admissions and OP visits in Indian healthcare facilities. The models have been used to generate state-level estimates of the cost of IP admissions and OP visits in India. This is the first time cost estimates for IP admissions and OP visits across all the states have been estimated based on standardised data, and no other standardised data on economic costs exist in this form. The models and the cost estimates are a valuable resource for health policy-makers and planners, and can also be utilised to inform important policy-relevant research. In the absence of healthcare cost information in India, these models can inform multiple high-level policy decisions regarding the design and shape of health benefits packages and insurance schemes, including price setting, health technology assessment, budgeting and forecasting. They provide a method with which to estimate facilitylevel unit costs for both IP and OP care without the need to undertake a full costing exercise, saving both time and money, and avoiding the need to use an inaccurate national average. The variation in cost estimates across the states, predicted by the models, confirms the need for state-level information in estimating costs. But the differences in unit costs can be driven by a number of factors, including different levels of service quality and input mix, case mix, price and wage levels and/or the nature of the referral systems [23]. Due to the nature of the models developed here, hospitalisation or OP visit rate have the strongest influence on the unit cost. As a result, unit costs in the states where the DHs have a higher patient load generally have lower costs. In contrast, the states with low population density (such as Nagaland and Mizoram) consistently have higher unit costs across the different sets of predictions. It is also notable that the states that score highest on the state health index (Mizoram, Kerala, Punjab and Tamil Nadu) all have IP unit costs that fall in the higher cost half of states. Those states that score lower on the state health index (Odisha, Rajasthan, Bihar and Nagaland) tend to have lower unit costs.
As well as a wide range in the unit costs across the states, there is some uncertainty in the point estimates seen in the uncertainty intervals. Some of this uncertainty is driven by the choice of model for the state-level predictions. Facility-level unit cost predictions are likely to need a better specified model that captures individual facility characteristics, including management, quality of care, wage rates and labour time. The model runs presented in Appendix 4 (see electronic supplementary material) confirm that state-level models could be improved. However, for this analysis, it was not possible to use models with the highest adjusted R-squared score (e.g. model A in Table 4a and b), as quality data on the average price of labour and the average quantity of human resources at facilities in each state were not available. In addition, the models have been developed using data from only six states and include only public facilities. Cost data from more states would help strengthen and further validate the model predictions for each state. The government funded costing study currently underway [47] has potential to expand the data set and include the private sectors and tertiary providers in an increased number of states.
Further to these limitations, the critical variables of hospital admissions and OP visits were estimated using household reported data. Ideally, facility-reported admissions and visit data from the Health Management Information System (HMIS) would have been used, but these were not accessible at the central level. There is also state variation in reporting and quality of data on infrastructure. In addition, differences in patient characteristics would further strengthen the estimates, but these are not consistently available either. To refine the modelling approach, improving the accessibility and quality of HMIS data is vital. To address this uncertainty, a validation procedure was carried out in which model predictions were compared with actual unit costs for individual sites. While there were some differences between the actual and predicted costs, the actual unit costs for the selected facilities fall within the upper and lower bounds of the predicted costs for the same sites. This suggests that the results from the models are relatively robust, but that larger samples of cost data are needed to narrow the uncertainty intervals. More and better data on health facility costs, statelevel health system infrastructure and service provision, in particular, facility-level average admission and OP visit rates, will increase the predictive power of the models. The variation in costs across the states suggests that costs have the potential to be more closely aligned to each other. In other words, there is scope for improving efficiency and allocation of resources. Ideally unit costs would be aligned around those states that are more efficient at producing quality healthcare services that are equitably distributed, and therefore these estimates need to be used with caution. However, the level of efficiency with respect to health outcomes or quality health services of these facilities is currently unknown, suggesting further research to identify the most efficient states or facilities would be highly beneficial. The state-level estimates also provide a way to assist in the prediction of costs of healthcare interventions or treatment of conditions and can assist with setting 'differential prices' for insurance reimbursement. By characterising the relationship between healthcare costs between different states, it is possible to use this relationship to predict costs or set prices for specific interventions. For example, as the model predicts that DH IP costs are 1.5 times higher in Kerala than Odisha; then if cost data are available for Kerala, one approach would be to assume that an IP procedure such as a caesarean section will be 1.5 times the cost of a caesarean section in Odisha. Again, further research is required to validate this as a robust method for setting differential prices for treatment of individual conditions. In using statistical methods to predict costs, the analysis confirms that unit costs in India are not explained by scale of activity (admissions/OP visits) and capacity (number of beds) alone and that a modelling approach such as this is a better method to obtain state-level average costs estimates. While limitations do persist and therefore the results and, in particular, point estimates need to be used with caution, this first attempt at modelling facility costs in India represents a step forward in providing a more evidence-based approach to cost estimation.
Conclusion
There exists a dearth of cost information within India. We describe here a novel means of estimating cost functions within the Indian healthcare system, which can provide a robust means of filing information gaps in the costing evidence base. An adaptation of the WHO method for estimating unit costs was applied at a country level to generate unit costs estimates for different states in India. The models estimated were statistically robust and found significant variation in unit costs between the states and levels of the health system. Further cost and health system data are still needed to improve the cost evidence base in India. Despite this, the cost function approach is a useful tool for the Indian context, and can be further developed as the evidence base expands at the district level and below, as well as for tertiary level and private sector facilities.
Author Contributions All authors contributed to the study conception and design. Material preparation and analysis were performed by PB, LG and SP. LD, LG, SP and PB contributed to the conceptualisation of the paper. Material preparation was carried out by PB, LG, ASC and SS. The first draft of the manuscript was written by LG, and all authors commented on previous versions of the manuscript. All authors read and approved the final manuscript.
|
nuts were found in a lot from a grove in Santa Ana, Calif.
Tri- and Tetracarpellary Walnuts. F, Alex. McDermott. Torreya 14: 127. July 1914- The author refers to his previous article and states that since then he had obtained a lot of 106 abnormal walnuts from the same place, 89 tricarpellary and 17 tetracarpellary.
2. A weather phenomenon worthy of record is that on Sunday, December 26, 1915, at about 6.15 a. m., thunder and lightning accompanied a snow storm, and the steeple of the Dutch Reformed church on Tompkins Avenue, New Brighton, and a dwelling house on Westervelt Avenue were struck. The principal damage was done in connection with the church, where the entire electric wiring system was destroyed. A long account of the storm was printed in the Staten Island World of December 31, which is herewith contributed to our loc?l items scrapbook.
Mr. William T. Davis read two papers: one on Interesting Records of the Work of Woodpeckers (see this issue, p. 147) and one on the Local Occurrence of Conocephalus strictus (see this issue, p. 149), and also read the following note:
The herring gull, Larus argentatus, usually disappears from New York Bay by the middle of May. They did not do so, however, in 1915, for on several occasions a number were seen in the bay in July. On July 6 five herring gulls were seen; on the 7th, six in the morning, and toward evening fifteen were observed flying toward their roosting place in the Lower Bay. They were still present in the Upper Bay on July 21. The majority of the birds were in dark plumage and were therefore not adults. Wilson's petrels, Oceanites oceanicus, were also common in the Upper Bay during July 1915.
SECTION OF APPLIED SCIENCE
During the fiscal year 1915-16 the section held a total ot 11 meetings. Three of these were business meetings, seven included both a business and a scientific program, and one was a joint meeting witn the Association.
By reason of the absence of a quorum at several of the earlier meetings officers were not elected until December, wh^n the following were elected: August E. Hansen, chairman; Carl F. Grieshaber, vice chairman; George L. Mitchill, recorder. As soon as this was effected the section held a business meeting to discuss ways and means of improving the section. The result was the appointment of a committee on consideration of policy, which met with the sectional committee and made certain recommendations to the section. The section acted on these recommendations and organized a press committee to assist the recorder in securing publicity, a reception committee to promote sociability at the meetings, and a membership cqjnmittee to
|
export const API_URL_ROOT = process.env.APP_URL;
const APP_BASE_CANONICAL_URL = process.env.APP_BASE_CANONICAL_URL;
export const websiteUrl = (relativePath = '') => {
if (relativePath === '/') {
relativePath = '';
}
return APP_BASE_CANONICAL_URL + relativePath;
};
let globalHeaderObj = {
'Content-Type': 'application/json',
'X-Requested-With':'XMLHttpRequest',
}
export const globalHeader = () => {
if(typeof localStorage.getItem('token') !== 'undefined'){
globalHeaderObj['Authorization'] = 'Token ' + localStorage.getItem('token');
return globalHeaderObj;
}
return globalHeaderObj;
};
|
package com.lustrel.geoaccess.activities;
import android.os.Bundle;
import android.support.v7.app.AppCompatActivity;
import android.support.v7.widget.Toolbar;
import android.telecom.Call;
import android.util.Log;
import android.widget.TextView;
import android.widget.Toast;
import com.lustrel.geoaccess.R;
import org.json.JSONException;
import org.json.JSONObject;
public class WaterDetailsActivity extends AppCompatActivity {
private Toolbar toolbar;
private TextView lblLatitude;
private TextView lblLongitude;
private TextView lblState;
private TextView lblLocation;
private TextView lblCounty;
private TextView lblDepth;
private TextView lblStaticLevel;
private TextView lblDynamicLevel;
private TextView lblFlowNumber;
private TextView lblPresentSolids;
private TextView lblFlowRate;
private TextView lblDate;
@Override
protected void onCreate(Bundle savedInstanceState) {
super.onCreate(savedInstanceState);
setContentView(R.layout.water_details_activity);
loadElementsFromXML();
applyToolbar();
populateDetails();
}
private void loadElementsFromXML(){
toolbar = (Toolbar) findViewById(R.id.toolbar);
lblLatitude = (TextView) findViewById(R.id.latitude);
lblLongitude = (TextView) findViewById(R.id.longitude);
lblState = (TextView) findViewById(R.id.state);
lblLocation = (TextView) findViewById(R.id.location);
lblCounty = (TextView) findViewById(R.id.county);
lblDepth = (TextView) findViewById(R.id.depth);
lblStaticLevel = (TextView) findViewById(R.id.static_level);
lblDynamicLevel = (TextView) findViewById(R.id.dynamic_level);
lblFlowNumber = (TextView) findViewById(R.id.flow_number);
lblPresentSolids = (TextView) findViewById(R.id.solids_present);
lblFlowRate = (TextView) findViewById(R.id.flow_rate);
lblDate = (TextView) findViewById(R.id.date);
}
private void applyToolbar(){
setSupportActionBar(toolbar);
}
private void populateDetails(){
try {
String detailsAsText = getIntent().getStringExtra("MARKER_DETAILS");
JSONObject details = new JSONObject(detailsAsText);
setTitle(details.getString("name"));
if(details.has("latitude"))
lblLatitude.setText(getString(R.string.detail_latitude_text) + " " + details.getString("latitude"));
if(details.has("longitude"))
lblLongitude.setText(getString(R.string.detail_longitude_text) + " " + details.getString("longitude"));
if(details.has("state"))
lblState.setText(getString(R.string.detail_state_text) + " " + details.getString("state"));
if(details.has("location"))
lblLocation.setText(getString(R.string.detail_location_text) + " " + details.getString("location"));
if(details.has("county"))
lblCounty.setText(getString(R.string.detail_county_text) + " " + details.getString("county"));
if(details.has("depth"))
lblDepth.setText(getString(R.string.detail_depth_text) + " " + details.getString("depth"));
if(details.has("date"))
lblDate.setText(getString(R.string.detail_date) + " " + details.getString("date"));
if(details.has("nivelestatico"))
lblStaticLevel.setText(getString(R.string.detail_static_level_text) + " " + details.getString("nivelestatico"));
if(details.has("niveldinamico"))
lblDynamicLevel.setText(getString(R.string.detail_dynamic_level_text) + " " + details.getString("niveldinamico"));
if(details.has("numerodavazao"))
lblFlowNumber.setText(getString(R.string.detail_flow_number_text) + " " + details.getString("numerodavazao"));
if(details.has("solidspresent"))
lblPresentSolids.setText(getString(R.string.detail_present_solids_text) + " " + details.getString("solidspresent"));
if(details.has("flowrate"))
lblFlowRate.setText(getString(R.string.detail_flow_rate_text) + " " + details.getString("flowrate"));
} catch(JSONException exception){}
}
}
|
Thread:Mister Explicit/@comment-24374939-20160414111950/@comment-25999606-20160414230043
Yeah i was right about that. I guess great minds think alike? Lol
|
Board Thread:Game Discussion/@comment-37524761-20190425131229/@comment-31567784-20190426081151
20 laps @ PTT, 21 opponents. Skip 300 I see you got the idea behind it :-)
|
Theranostics, which combines photodynamic therapy (PDT) and fluorescence diagnostics, is a promising field in modern medicine that uses light to detect and eliminate tumors, other unwanted structures, as well as the foci of microbial and fungal infections of the skin and mucous membrane \[[@R1], [@R2]\]. Photodynamic reactions are carried out by dye molecules capable of absorbing a quantum of light and passing into a long-lived triplet state. During its deactivation, a dye molecule produces reactive oxygen species (ROSs) and free radicals. ROSs possess high oxidative activity and can be used to disrupt the functionality of individual biomolecules and the vital activity of whole cells. Such dyes are called photosensitizers (PSs). These are typically complex heterocyclic compounds with a number of absorption bands in the visible spectral range. A substantive search for highly effective PSs that can be used within the phenomenon of photosensitization for the treatment of cancer and infectious diseases is currently underway. A number of synthetic PSs are already successfully being used in clinical practice to fight certain types of cancer, in dentistry, etc. \[[@R3]\].
One of the key criteria in choosing dyes for PDT is the significant absorption capacity of PS in the red and near-infrared spectral regions, since light penetration depth into biological tissues is considered to be the greatest in this range. Modifying the structure of a PS molecule might be an inefficient way to meet this criterion; therefore, it might be required to use additional light collectors. Having absorbed light of the required spectral range, the light collector will transfer energy to the PS and, thereby, enhance its photodynamic effect.
The main mechanism of energy transfer in such hybrid complexes (HCs) is considered to be the nonradiative one (Forster resonant energy transfer, FRET). Accordingly, a number of requirements also apply regarding the light collector. In particular, the resonance condition imposes certain restrictions on the spectral characteristics of an energy donor and an energy acceptor. Taking into account the fact that the spectral properties of HC components largely depend on their structural properties, which can change during the complex formation, we obtain a complicated multicomponent system whose design optimization is among the most consequential issues in applied biophysics.
Luminescent nanoparticles (LNPs) are currently the most commonly used as light collectors for PS molecules \[[@R4]\]. Such nanoparticles can be applied simultaneously as an antenna, a diagnostic marker, and a platform for targeted drug delivery. A sufficient number of reviews have focused on the latter two aspects of nanoparticle use \[[@R5], [@R6], [@R7]\], whereas the fundamental problems of using nanoparticles as a light collector receive less attention \[[@R8], [@R9], [@R10]\].
Upconversion \[[@R11], [@R12]\], silicon \[[@R13]\], and carbon \[[@R14], [@R15]\] nanoparticles are the LNPs most widely used in photobiology. Furthermore, a large number of studies have been devoted to the application of semiconductor nanoparticles (quantum dots, QDs) as energy donors for PS, although their biocompatibility still remains disputable \[[@R16]\]. Nevertheless, the question regarding the relationship between the spectral and structural properties of QDs is the one that has been resolved most satisfactorily, making it possible to study the energy transfer in HCs in detail.
This review considers the features of the design of HCs based on QDs and PSs with allowance for the complex formation mechanism, the stoichiometry of the complex, the structure of HC components, as well as the influence of these parameters on the efficiency of energy transfer and ROS generation in the complexes. We found out that the photodynamic properties of PS decrease with a rising ratio of the components of the PS : LNP complex because of its high local concentration on the nanoparticle surface even through energy transfer efficiency is enhanced. Enhancement of the luminescent properties of QDs due to protective shells can reduce the efficiency of energy transfer in HC, as the distance between the energy donor and the acceptor increases. Based on the correlations obtained, a technique allowing one to synthesize highly efficient HCs has been proposed; the aim of this technique is to maximize the generation of reactive oxygen species by the photosensitizer within a HC. The conclusions drawn in this review largely apply to HCs based on all other types of LNPs.
1. COMPONENTS OF THE HYBRID COMPLEX
**1.1. Second-generation tetrapyrrolic photosensitizers**
A photosensitizer that is highly efficient in terms of ROS yield is supposed to boast the following characteristics. First, the energy of its triplet state must be sufficient to enable a photodynamic reaction with molecular oxygen; the selection is performed to increase the yield of the triplet state and its lifetime. Second, the PS is supposed to exist in a monomeric state, since PS aggregates do not generate ROS as efficiently. Third, the PS should have a high absorption capacity, preferably within the "optical window" of biological tissues.
It is obvious that the photodynamic properties depend on the structure of a PS molecule. We will consider the relationship between the structural and photophysical properties of PSs using tetrapyrrole dyes, the most common second-generation PSs, as an example.
::: {#F1 .fig}
(*A*) -- The structure of a porphin molecule and possible ways for its modification. (*B*) -- The absorption spectra of zinc phthalocyanines modified with different numbers of choline groups R
Porphin is the simplest dye of the tetrapyrrole series. The absorption spectrum of porphin contains an intense Soret band at the boundary between the UV and visible regions, as well as four low-intensity narrow bands in the visible region (QI--QIV; numbering starts at longer wavelengths). There are several main ways to modify the structure of a porphin molecule, making it possible to obtain PS that exhibit high photodynamic activity (*[Fig. 1A](#F1){ref-type="fig"}*):
\(A) sequential hydrogenation of two double bonds, which are not formally included in the conjugated system, shifts the QI band to the long-wavelength spectral region (a bathochromic shift) and increases its intensity by more than an order of magnitude. Hydrogenation gives rise to the classes of dihydroporphyrins (chlorins) and tetrahydroporphyrins (bacteriochlorins);
\(B) replacement of carbon in the methine CH groups with a nitrogen atom (tetrazaporphyrins) or incorporation of benzene rings in the macrocycle of a dye molecule (tetrabenzoporphyrins) increases the intensity of the QI and QIII bands, as well as causes their bathochromic shift. The strongest effect is obtained when these two approaches are combined, i.e., in the classes of tetrazatetrabenzoporphyrins or phthalocyanines (Pcs); and
\(C) coordination of various elements by the macrocycle of a porphin molecule due to the lone electron pairs of the central nitrogen atoms. For porphyrins, complexes with divalent metals are the most typical. Formation of a metal complex leads to the degeneration of four absorption bands in the visible spectral region to leave two bands whose intensity is significantly increased. This situation is typical of all porphyrin dyes containing no hydrogenated pyrrole rings. When a metal atom is incorporated into the Pc macrocycle, insignificant bathochromic shifts of the QI and QII bands are observed and the magnitude of the bathochromic shift increases as the atomic number of the metal increases \[[@R17]\].
Modification of the porphyrin structure also changes the characteristics of the excited triplet state. Thus, the yield of the excited triplet state slightly decreases as one proceeds from porphyrins to chlorins \[[@R18]\]. Heavy and paramagnetic metal atoms within the Pc increase the probability of a singlet--triplet transition; therefore, such Pcs are characterized by a high yield of the excited triplet state \[[@R19]\]. In addition, the probability of nonradiative deactivation to the ground state increases due to the involvement of the *d*-shells of the metal in the conjugation system \[[@R20]\]. The relationship between the constants of these processes depends on the nature of the metal and side substituents \[[@R21]\].
The solubility of a tetrapyrrolic PS in water is achieved by incorporating side substituents at the macrocycle periphery. These side substituents are usually low-molecular-weight ligands imparting polarity and/or charge to a molecule \[[@R22]\]. The maximum number of side substituents that can be inserted into a tetrapyrrole molecule is determined by the number of binding sites on pyrrole (or benzene in the case of benzoporphyrins) rings and is equal to eight for both the ortho- and meta-substitution \[[@R23]\]. For silicon PS (or PS complexes with trivalent metals), insertion of axial ligands is available \[[@R24]\]. Side substituents significantly affect the optical and photophysical properties of PS \[[@R17], [@R25], [@R26]\]. A wide range of substituents with specific properties, as well as the possibility of varying the degree of substitution, allow one to create substituted PSs for various fields of industry (catalysts, sensors, and solar cells) or medicine.
Although chemical modification of PS molecules makes them more water-soluble, the hydrophobic nature of the macrocycle determines the probability of aggregation of these molecules in aqueous solutions. Several types of tetrapyrrole aggregates have been proven to exist \[[@R27]\]. H-type (oligomeric) and D-type (dimeric) aggregates have a narrow absorption band in the visible region, which is shifted to the blue spectral region compared to the absorption band of monomeric form (*[Fig. 1B](#F1){ref-type="fig"}*). Tetrapyrrole molecules in such aggregates form a "sandwich" structure; the aggregates do not fluoresce, since the excited state is nonradiatively deactivated due to intramolecular conversion. J-type (polymeric) aggregates have a wide absorption band shifted to the red spectral region, compared to the absorption band of the monomeric form; the aggregates are formed by PS molecules interacting with the edge parts. Porphyrin molecules can simultaneously exist in both forms (the monomer/aggregate equilibrium) of all types of aggregates; transitions between these states are also possible \[[@R28], [@R29], [@R30]\]. Aggregation can be caused by variation of a number of ambient parameters (pH and ionic strength of a solution) \[[@R31], [@R32]\] or an increase in PS concentration \[[@R33]\]. It can also be initiated by the formation of a complex between tetrapyrroles and molecules of a different nature \[[@R34]\]. The probability of aggregation also depends on the presence and nature of the central metal atom in the PS macrocycle.
**1.2. Colloidal quantum dots**
Quantum dots simultaneously have the physical and chemical properties of molecules and the optoelectronic properties of semiconductors. A QD is a luminescent semiconductor nanocrystal whose characteristic dimensions lie in the range of 3--10 nm (*[Fig. 2A](#F2){ref-type="fig"}*). It is known that the properties of nanomaterials qualitatively differ from those of a bulk analog \[[@R35]\] because of the quantum size effects. If the size of an object does not exceed the Bohr radius of the exciton, typical of a given material, the charge carrier inside the object appears in a three-dimensional potential well \[[@R36]\]. This leads to a modification of the energy spectrum (*[Fig. 2B](#F2){ref-type="fig"}*). The classical spectrum of a semiconductor with a valence band, a forbidden band, and a conduction band is transformed into a set of discrete energy levels with a characteristic gap *h*2/8*π*2*mr*2, where *h* is the Planck constant, *m*is the effective mass of the charge carrier, and *r*is the QD radius. Electron transitions are possible between these levels, accompanied by absorption or emission of a quantum of light in the visible wavelength range.
::: {#F2 .fig}
(*A*) -- An electron micrograph of CdSe/ZnS nanoparticles. (*B*) -- The energy spectra of a bulk and nanosized semiconductor vs. the energy spectrum of an organic fluorophore. C -- the conduction band; V -- the valence band; Ez -- the forbidden band; and S0, S1 and S2 -- the ground, first and second excited electronic levels, respectively. Vertical arrows indicate the electronic transitions; dashed arrows indicate the transitions to the lower excited levels accompanied by thermal energy dissipation
Due to the absorbed energy, the electron is transferred to a high-energy level, so that an exciton (an electron--"hole" pair) is formed in the QD crystal. Deactivation of the excited state is performed by exciton recombination accompanied by the emission of excess energy as a light quantum.
Since the gap between the energy levels of QDs depends on particle size, the luminescence spectrum of QDs undergoes a bathochromic shift when the crystal radius is increased. Thus, by varying the crystal size, one can choose QDs with the required spectral properties for specific research problems.
Quantum dots absorb light in a wide wavelength range with molar extinction coefficients of \~10^5^-10^6^ L/mol•Ecm. This fact has spurred a keen interest in QDs as promising luminescent labels for biological research. However, for a successful application of QD in biology, two significant disadvantages of QDs (the low luminescence quantum yield (*φ*) and hydrophobicity of semiconductor material) need to be overcome.
The main reason for the low *φ*values is the crystal lattice defects on the nanocrystal surface, which act as trap states for the charge carrier \[[@R36]\]. The charge carrier localized in such a trap prevents radiative recombination of the exciton. A QD is said to have passed into the so-called "off" state, which can be up to 100 s for an individual crystal \[[@R37]\].
The number of the defects on the QD surface was reduced for the first time in 1990 by coating a CdSe nanocrystal with a protective ZnS shell \[[@R38]\]. We will further refer to the luminescent central part of a multilayer QD as its core. Zinc sulfide is also a semiconductor, but with a wider gap, which creates a potential barrier for the charge carrier and pushes exciton to localize in the QD core. In addition, the protective shell is a physical barrier between the QD core and the environment, making the optical properties of the QD less sensitive to chemical reactions on its surface. By 1996, the development of methods for coating the QD core with a protective shell had given rise to samples of relatively monodisperse nanocrystals with *φ*\~ 50% \[[@R39]\]. The modern methods used to synthesize QDs yield nanocrystal samples with a *φ*\~ 80--90% \[[@R40]\]. It should be noted that the *φ*value depends nonlinearly on the thickness of the protective shell of the QD: the protective shell consisting of more than three ZnS layers was shown to quench the luminescence of the QD with a CdSe core \[[@R41]\]. It is believed that the probability of formation of intrinsic defects increases with the number of atomic layers in the shell \[[@R42]\].
Furthermore, the use of QDs in biological research involves the transfer of hydrophobic nanocrystals to the aqueous phase. Substitution chemistry methods are usually used for this purpose: the precursor molecules covering QDs during their synthesis are replaced with amphiphilic ligands with the target properties.
Any molecules containing nucleophilic groups can be adsorbed on the nanocrystal surface. The organic shell can be multilayered: an amphiphilic polymer is additionally adsorbed onto a layer of low-molecular-weight hydrophobic ligands, which is responsible for the surface properties of QDs. In addition to water solubility, the organic shell largely ensures passivation of crystal lattice defects \[[@R43]\]. However, organic ligands cannot cover the entire surface of QDs; therefore, some crystal lattice defects persist \[[@R36]\]. In addition, ligands can give rise to new energy levels: thiols are known to quench the luminescence of CdSe QDs due to the emergence of an energy level superjacent to the first excited level of QDs \[[@R36]\].
The typical lifetime values of QD luminescence are 5--20 ns, being quite sufficient for efficient energy transfer. The kinetics of QD luminescence decay are characterized by two or three time components. There currently is no clear understanding of the reasons for the complexity of the decay kinetics of QD luminescence \[[@R35]\]. The most common hypothesis associates each time component with emissions from a specific energy state. This is evidenced by the complex structure of the exciton absorption peak of QDs \[[@R44]\]. In the simplest case (biexponential decay curve), the fast component corresponds to the radiative recombination of an exciton, while the slower one corresponds to the radiation mediated by crystal lattice defects \[[@R45], [@R46]\]. In this model, the QD luminescence spectrum consists of two overlapping bands, which sometimes cannot be separated. The contribution of the slow component declines with decreasing temperature \[[@R45]\] and luminescence quantum yield \[[@R40]\]. In this case, the luminescence decay curves of ideal QDs without defects would be monoexponential; indeed, only one time component was found in some QD samples \[[@R37], [@R47]\]. The more differentiated the defects in crystals are (especially in QDs with a core/shell structure), the more time components in the luminescence decay curves there are \[[@R39]\].
Particle size nonuniformity can be an alternative reason for the emergence of several time components in the decay curves of QD luminescence. Increasing the QD size not only leads to a bathochromic shift in the luminescence spectrum, but also causes a corresponding shift of the exciton band in the absorption spectrum \[[@R48]\], reduces the luminescence lifetime \[[@R49]\], and causes nonlinear changes in the quantum yield *φ*\[[@R50]\]. Consequently, a broadened luminescence spectrum will be observed for a sample containing several fractions of QDs of different sizes. Such a spectrum is a superposition of the spectra from different fractions of QDs, which have their own quantum yield and luminescence lifetime values. The average value weighted over all the components is typically used as the QD luminescence lifetime because of the complexity of interpreting the time components.
2. THE COMPLEXATION STRATEGIES
The following types of interactions make it possible to create hybrid LNP--PS complexes in aqueous solutions: electrostatic or covalent ones, or a group of interactions combined under the concept of sorption (*[Fig. 3](#F3){ref-type="fig"}*). The spectral properties of PS change as bonds of any of these types form. The properties of LNPs change extremely rarely and are not associated with the HC formation process \[[@R51], [@R52], [@R53]\].
::: {#F3 .fig}
The most common methods used to create a quantum dot--photosensitizer hybrid complex. 1.1--1.2 is the electrostatic interaction; 2.1--2.2 are absorption and adsorption, respectively; 3.1--3.2 are the covalent interactions; 4 corresponds to coordination. The nanocrystal core of QDs is shown in gray; the polymer shell is shown in blue; and the shell of low-molecular-weight ligands is shown in red. The orange dot indicates the charged functional groups on the polymer/ligand; the green dot shows the covalent bond
**2.1. Electrostatic interaction**
HCs are often formed by mixing the aqueous solutions of LNP and PS due to the electrostatic attraction of oppositely charged components (*[Fig. 3, 1.1--1.2](#F3){ref-type="fig"}*). In this case, changes in the spectral properties of PS should be determined by electron density perturbation and may differ depending on the nature and the stoichiometric ratio of HC components. Information on the following complexation effects is available:
\(1) a bathochromic shift in the absorption and/or fluorescence spectra of PS \[[@R54], [@R55], [@R56], [@R57], [@R58], [@R59]\];
\(2) a hypsochromic shift in the absorption and fluorescence spectra of PS \[[@R52], [@R60], [@R61], [@R62]\];
\(3) hypochromism \[[@R52], [@R56], [@R57], [@R60]\];
\(4) a reduced quantum yield of the PS fluorescence \[[@R60], [@R62]\];
\(5) an increased \[[@R60], [@R63]\] quantum yield of the triplet state of PS; and
\(6) an increased \[[@R60], [@R62]\] lifetime of the triplet state of PS.
The increased yield of the triplet states of PS is usually attributed to the so-called "heavy-atom effect." According to it, the probability of intramolecular conversion of PS to the triplet state increases in the presence of heavy metal atoms (Cd, Te), which also reduces the quantum yield of PS fluorescence. In some cases, the cadmium ion from QD can be incorporated into the macrocycle of metal-free PS upon HC formation \[[@R62], [@R64]\]. It was noted \[[@R65]\] that the magnitude of the changes in the optical properties of PS increases with the size of the QD crystal. The presence of the ZnS protective shell is expected to reduce the effect of the heavy metal atoms in the QD core on the properties of PS.
**2.2. Nonspecific sorption**
HCs formed due to the electrostatic attraction of oppositely charged nanoparticles and photosensitizers do not require special preparation protocols and are quite stable. However, it was noted that mixing of likecharged components also leads to the formation of HC in some cases \[[@R66], [@R67], [@R68], [@R69], [@R70]\]. Consequently, the self-assembly of HCs can involve interactions other than electrostatic ones, which we will further combine under the term "sorption".
Depending on the structure of the organic shell of QD, there can be two variants of PS sorption. If the QD surface is coated with a layer of low-molecular- weight ligands, then PS molecules are incorporated into this monolayer due to peripheral \[[@R64]\] or axial \[[@R71], [@R72], [@R73]\] hydrophobic substituents. In this case, we talk about surface binding (*adsorption*, *[Fig. 3, 2.2](#F3){ref-type="fig"}*). This kind of interaction weakens with increasing branching of the substituent \[[@R73]\]. Interestingly, the energy transfer efficiency increases with the substituent length as a result of stronger interaction, but then it decreases if the substituent length starts to exceed the length of the low-molecular-weight ligand on the QD surface \[[@R72]\].
Direct interaction between a PS molecule and a QD crystal is a special case of adsorption (*[Fig. 3](#F3){ref-type="fig"}*, *[Fig. 4](#F4){ref-type="fig"}*). The formation of a coordination bond between the tertiary nitrogen atom of the PS molecule and the atoms of the CdSe/ZnS QD crystal lattice in toluene can be considered proven \[[@R74], [@R75], [@R76], [@R77], [@R78]\]. In this case, a close contact is required between the PS and the QD crystal, which can be hindered by the outer organic shell of the nanoparticle. Meanwhile, the formation of a coordination bond should not be accompanied by the obligatory displacement of organic ligands by the PS molecule, since adsorption can occur on the ligand-free areas of the nanoparticle surface. A porphyrin molecule can obviously be adsorbed onto QDs both by the plane of the macrocycle involving all the side pyridyl rings and by its edge involving one or two pyridyl substituents. This is evidenced by the increased efficiency of energy transfer W in HC as the number of pyridyl substituents in the porphyrin molecule rises from 1 to 4, but the value of W is comparable for monopyridyl porphyrin and bipyridyl porphyrin with an opposite arrangement of pyridyl rings.
::: {#F4 .fig}
Dependence of the energy transfer efficiency *W* in HC on the size *R*~QD~ of the QD core (here, we assume that the coordination bond forms directly between the PS molecule and the QD crystal). The Forster radius (*R*~0~) was chosen to be equal to 5 nm. An example of HC with a photosensitizer covalently attached to the QD polymer shell (the total QD radius being 11.5 nm) is shown
A hypsochromic shift in the fluorescence spectrum of porphyrin and an increase in its fluorescence lifetime were observed during the formation of HC \[[@R79]\]. According to Zenkevich et al. \[[@R79]\], the amplitude of the effects decreased with increasing porphyrin concentration in solution due to the rise in the proportion of porphyrin molecules not associated with QDs. In addition, during the formation of HC, a bathochromic shift of the Soret band was observed, which is possibly caused by changes in the structure of the π-system of electrons upon coordination of the pyridyl nitrogen atom to the QD zinc atom, or by a higher dielectric constant of the medium near the nanoparticle surface as compared to the toluene solution.
The feasibility of coordination interaction has been proposed to explain the formation of HC between a negatively charged CdTe quantum dot (coated with 3-mercaptopropionic acid) and aluminum tetrasulfophthalocyanine, which is also negatively charged \[[@R80]\]. It is assumed that the PS molecule is coordinated to the QD carboxyl group by an aluminum atom. The idea was extended to CdTe QDs coated with thioglycolic acid \[[@R81], [@R82]\].
The complexes of PS with LNPs coated with a polymer shell are of particular interest \[[@R70], [@R83], [@R84], [@R85], [@R86], [@R87], [@R88], [@R89], [@R90]\]. It is believed that the PS molecules in such complexes can be incorporated into the bulk of the polymer; therefore, we talk about *absorption*in this case (*[Fig. 3](#F3){ref-type="fig"}*, 2.1). This conclusion was drawn from the fact that the hydrodynamic radius of an LNP (together with the polymer shell) exceeds the distance between the donor and the acceptor required for efficient energy transfer via the FRET mechanism that is actually observed in these systems.
During the formation of HC through sorption, multidirectional changes in the spectral properties of PS were noted, depending on the type of PS molecule \[[@R78], [@R85], [@R87], [@R89], [@R91], [@R92]\]; there could also be no changes at all because of the adsorption occurring when incorporation was minimal \[[@R64]\]. Aggregation of PS molecules can be observed during sorption \[[@R93]\].
The triplet yield of PS typically increases upon sorption on LNP \[[@R67], [@R92]\]; however, some opposite results have also been obtained \[[@R68]\]: thus, a reduced lifetime of the triplet state of PS was observed in \[[@R91]\]. This could have been due to the fact that when a PS molecule is incorporated into the organic shell of a QD, the probability of quenching of the PS triplet state by oxygen decreases \[[@R78]\].
**2.3. Covalent binding**
The complexes between nanoparticles and PS formed via covalent interaction have a number of advantages over HCs stabilized by other types of interactions (*[Fig. 3, 3.1--3.2](#F3){ref-type="fig"}*). First, the interaction occurs between specific functional groups of PS and the organic shell of QDs; therefore, exact localization of PS in HC is known. This makes it possible to predict some of the photophysical properties of HCs. Second, this HC potentially remains more stable in the presence of biological objects and environments. Therefore, there is a keen interest in covalently stabilized conjugates of PSs and nanoparticles \[[@R53], [@R65], [@R94], [@R95], [@R96], [@R97], [@R98], [@R99], [@R100]\].
Formation of a covalent bond can be easily monitored by the emergence of corresponding lines in the Raman spectra or absorption spectra in the IR region \[[@R65], [@R94], [@R96]\]. Meanwhile, it is difficult to control the PS : LNP ratio in the end product when routine crosslinking methods are used. In addition, when crosslinking is performed through amino and carboxyl groups, HCs of the electrostatically interacting components can form, which is difficult to prevent. For these reasons, a number of studies have failed to compare the properties of covalently crosslinked and electrostatically stabilized HCs based on the same components \[[@R94], [@R96], [@R98]\].
An even more important problem is that the linker that forms between the PS molecule and the LNP surface increases the distance between them. This fact negatively affects the energy transfer efficiency, which rapidly decreases with increasing distance between the energy donor and acceptor. *[Figure 3](#F3){ref-type="fig"}* shows that the influence of this effect can be critical when a polymer shell is used.
In most studies, changes in the spectral characteristics of PS during HC formation are identical for the covalent and electrostatic binding methods: a hypsochromic shift in the absorption spectrum of PS and hypochromism \[[@R94], [@R95], [@R97]\] or a bathochromic shift in the absorption spectrum of PS and hypochromism \[[@R98]\]. There were no changes in the spectral properties of PSs during the formation of a covalent bond \[[@R96]\].
3. DESIGN OPTIMIZATION FOR HYBRID COMPLEXES
Designing hybrid complexes based on LNPs implies that the efficiency of ROS generation by a photosensitizer upon excitation is increased in the spectral regions where the PS itself has a low absorption capacity. Since such an enhancement of the photodynamic properties of PS is achieved due to nonradiative energy transfer, optimization of the HC design is primarily associated with the optimization of energy transfer via the FRET mechanism. However, it should be noted that a set of properties of HC promoting efficient energy transfer may, generally speaking, not coincide with the set of properties of HC that enhances the photodynamic activity of PS in HC. For this reason, we will consider these two aspects of HC optimization separately.
**3.1. Energy transfer efficiency**
Since energy transfer increases the deactivation rate of the excited state of an energy donor, the degree of quenching of LNP luminescence is the main criterion in a quantitative assessment of the transfer efficiency.
Let us consider the simplest quantum dot--tetrapyrrolic PS system stabilized via coordination of the PS to the nanocrystal surface. The subject of optimization will be energy transfer, which contributes to the increase in the absorption capacity of PS in the bluegreen spectral region. According to the nonradiative resonance energy transfer theory, the efficiency of this process (*W*) can be increased by
\(A) increasing the overlap integral (*J*) of the LNP luminescence spectrum and PS absorption spectrum;
\(B) increasing the quantum yield of LNP luminescence;
\(C) decreasing the LNP--PS distance;
\(D) increasing the molar extinction coefficient of a PS molecule; or
\(E) increasing the PS : LNP stoichiometric ratio.
The *J*value can be increased by shifting the QD luminescence spectrum to longer wavelengths, closer to the absorption spectrum of the PS. Since the position of the luminescence spectrum of QDs is easily specified during their synthesis, a QD providing the maximum*J*value can be easily selected when the position of the PS absorption spectrum is fixed. However, the bathochromic shift in the QD luminescence spectrum occurs due to a rise in the particle size, which increases the QD--PS distance and reduces the energy transfer efficiency *W* (*[Fig. 4](#F4){ref-type="fig"}*). This is typically accompanied by a reduction in the quantum yield of QD luminescence, which should also negatively affect the*W*value. Although the quantum yield of QD luminescence can be increased by growing a protective shell from a wider-gap semiconductor, such a modification will not only increase the luminescence yield, but also additionally increase the crystal size and, accordingly, increase the donor--acceptor distance. An alternative way is to choose materials for the crystal lattice of the QD core. On the one hand, an organic shell on the QD core protects the crystal surface against solvent molecules; therefore, the QD luminescence yield is expected to increase. On the other hand, additional defects may form on the crystal surface depending on the nature of the molecules comprising the organic shell, and the quantum yield of the QD luminescence will decrease.
It is possible to increase the *J*value due to the hypsochromic shift in the absorption spectrum of PS, since QDs of a smaller size can be used to create HCs in this case. Indeed, a smaller QD size will increase the quantum yield of QD luminescence and reduce the QD--PS distance, which will eventually increase the *W*value. However, applying such a strategy means that the red spectral region will not be used for ROS generation. In addition, if the spectra are ultimately shifted to the blue region, there is no need to use QDs, since many metal-free PSs absorb blue light perfectly due to the Soret band.
Therefore, complex QD-based systems have a number of parameters that cannot be optimized simultaneously due to their mutually exclusive influence on each other. Consequently, the highest energy transfer efficiency can be achieved only through compromise values of the PS and QD parameters.
Variation of only two parameters unambiguously increases the *W*value: increasing the molar extinction coefficient of PS and the PS : LNP stoichiometric ratio.
The molar extinction coefficient of PS in the visible region is usually increased by inserting a metal atom into the macrocycle. Since the formation of a metal complex significantly increases the lifetime of the triplet state of PS, this additionally enhances the photodynamic activity of the PS. Alternative ways for increasing the molar extinction coefficient of PS are to replace carbon with nitrogen in the methine bridges of the macrocycle, increase the macrocyclic aromaticity due to benzene rings, and hydrogenate double bonds. These ways also lead to an additional bathochromic shift in the absorption spectrum of PS. Consequently, it is necessary to additionally shift the luminescence spectrum of QD to longer wavelengths to preserve the maximum value of the overlap integral *J*. The effects caused by such a displacement can reduce the efficiency of energy transfer in HC.
The PS : LNP stoichiometric ratio can be increased to a certain limiting value that depends on the complexation method. If HC is formed by covalent crosslinking, then \[PS : LNP\]~max~ is determined by the number of functional groups on the organic shell of the QD (i.e., their density and surface area of the QD). If HC is stabilized via electrostatic interactions, the \[PS : LNP\]~max~ is determined by the number of charged groups on the organic shell of QD, as well as the number of charged groups on the PS molecule. There is ambiguity here: the more charges there are on the PS, the stronger the interaction is, but fewer PS molecules will bind to the QD surface.
If HC is stabilized trough sorption interactions, the \[PS : LNP\]~max~ is determined by the LNP surface area, as well as by the hydrophilic--hydrophobic balance of the PS molecule. For a bulk polymer shell of a nanoparticle, \[PS : LNP\]~max~ will be much higher than that when a monolayer of low-molecular-weight ligands is used. However, additional PS molecules will be located far enough from the QD center so that the efficiency of energy transfer to these PS molecules should be minimal. *[Figure 4](#F4){ref-type="fig"}* shows the situation where PS is covalently bound to the polymer shell of QD. One can see that for a total nanoparticle radius of 11.5 nm and Forster radius R0 = 5 nm, the efficiency of energy transfer to a given PS molecule will be no more than 0.7%.
In theory, the increased factor *χ*2 describing the mutual orientation of the transition dipole moments of the donor and acceptor can increase the energy transfer efficiency. The *χ*2 values can vary from 0 to 4. In solutions,*χ*2 is taken equal to 2/3 due to rotational diffusion and random orientation of the molecules. This is also used in the case of HCs, since most QDs do not have luminescence anisotropy. Nevertheless, in the general case, the orientation of transition dipole moments in the HC can be nonrandom. It is assumed that studies focusing on the anisotropy of the PS and LNPs fluorescence would potentially help estimate the possible mutual orientations of the transition dipole moments and thereby refine the *χ*2 value \[[@R101]\].
**3.2. Photodynamic properties of a photosensitizer**
A successful energy transfer event causes a transition of the PS molecule to an excited state. Energy transfer can increase the ROS yield or increase the intensity of PS fluorescence. Increased absorption capacity of a PS manifesting itself as an increase in the intensity of its sensitized fluorescence can be used to calculate the energy transfer efficiency *W*\[[@R58], [@R75], [@R82]\]. However, it is considered more correct to use the spectral characteristics of the energy donor to calculate the *W*value, since enhancement of the photodynamic properties of PS in HC strongly depends on the PS : LNP stoichiometric ratio.
::: {#F5 .fig}
(*A*) -- The concentration dependence of the fluorescence intensity of polycationic aluminum Pc in an aqueous solution and in an electrostatically stabilized hybrid complex with a polymer-coated QD. *R*Pc is the average distance between two Pc molecules in the medium (water in the case of a one-component Pc solution and the QD polymer shell in the case of a HC solution). The fluorescence excitation wavelength is 655 nm. (*B*) -- The concentration dependence of the PS fluorescence intensity in water and in HC (LNP concentration being constant). (1--4) the schematic representation of HCs with a different stoichiometry and the fluorescence intensity of PS in such HCs
It is known that as the PS concentration in a dilute solution rises, its fluorescence intensity increases linearly in the initial period of time; however, it reaches a plateau and then decreases in sufficiently concentrated solutions (*[Fig. 5](#F5){ref-type="fig"}*) \[[@R102]\]. This effect can be called "self-quenching of PS fluorescence". Self-quenching of the PS fluorescence can be caused by PS aggregation and the inner filter effects. PS aggregation was discussed in section 1.1. The inner filter effects consist in the shielding of the exciting light by layers of the PS solution, which lie closer to the front cell wall (a), and reabsorption of PS fluorescence (b). The latter is possible, since tetrapyrrolic PSs have a small Stokes shift (\~ 10 nm) so that the absorption and fluorescence spectra of PSs largely overlap. In addition to the nonlinear dependence of PS fluorescence intensity on its concentration, this phenomenon leads to a bathochromic shift in the fluorescence spectrum of PS and increases the measured fluorescence lifetime of the PS \[[@R103]\].
Quenching of PS fluorescence in the presence of nanoparticles is common \[[@R55], [@R104], [@R105], [@R106]\]. The concentration dependence of the fluorescence intensity of PS in HCs with semiconductor nanoparticles is also nonlinear \[[@R59], [@R70], [@R71], [@R87]\]; however, self-quenching starts at a much lower PS concentration compared to the PS in a single-component solution (*[Fig. 5A](#F5){ref-type="fig"}*). Indeed, the maximum PS : LNP ratio in HC can exceed 1000, so the local PS concentration during complex formation can be as high as several mM \[[@R90]\].
An increasing PS : LNP ratio may result in the aggregation of PS in the organic shell of the LNP. This effect is observed in any type of interaction between PS and LNP, except for covalent crosslinking. Any PS in a solution exists in a state of monomer/aggregate dynamic equilibrium, which can be shifted upon binding to LNP. The probability of this process depends both on the structural properties of the PS molecule (the type of metal atom, the nature and number of peripheral substituents) and on the structural features of the organic shell of the LNP. Thus, we have shown that despite the presence of eight peripheral carboxyl groups, zinc and aluminum Pcs aggregate upon binding to upconversion LNPs coated with a polymer shell containing terminal amino groups; zinc Pcs undergo aggregation at lower concentrations than aluminum Pcs do \[[@R107]\]. In this case, the PS aggregates continue to accept the electronic excitation energy of the LNP and the efficiency of this process may increase due to the greater overlap of the absorption spectrum of the aggregates with the luminescence spectrum of the LNP.
In addition, concentrating PS from the solution onto the LNP surface leads to solution "bleaching" within the region of PS absorption. In this case, the photodynamic activity of PS in HC is further reduced.
Let us imagine that the number of PS molecules on the LNP surface can increase infinitely without an increase in the average PS--LNP distance that is equal to the Forster radius R0. According to Forster's theory, at PS : LNP = x = 1, the energy transfer efficiency *W*is 50% at a distance R0. When x = 10, *W*= 91%; at x = 100,*W*= 99%; and at x = 1000, *W*= 99.9%. It is clear that the highest increase in the *W*value is observed as the PS : LNP ratio rises from 1 to 10, which is much less than the characteristic \[PS : LNP\]~max~ values are. It is fair to say that the absolute energy transfer efficiency*W*increases with a rising number of PS molecules in HC, while the energy transfer efficiency *W*for every separate PS molecule decreases.
Consequently, the more PS molecules there are in a complex with LNP, the less additional energy each of them receives, and, therefore, the enhancement of photodynamic properties of PS tends to zero. The photodynamic activity of PS in the HC at large PS : LNP ratios turns out to be lower than the activity of free PS due to self-quenching effects.
Finally, the use of some types of LNP shells can lead to the fact that ROS formed in a reaction between PS and molecular oxygen inside the organic shell of LNP cannot effectively damage the targets in the solution surrounding HC, since diffusion in the LNP shell is hindered. In this case, the most likely target of oxidation will be the PS molecule itself. Indeed, in electrostatically stabilized HCs based on aluminum phthalocyanines and QDs coated with a polymer shell, we observed rapid bleaching of the dye both under selective illumination of Pc and upon excitation of QD, followed by energy transfer \[[@R108]\]. As a result, the measured concentration of ROS is lower than the actual one. Nevertheless, the calculated ROS concentration corresponds to the effective concentration of ROS capable of exhibiting photodynamic activity outside the hybrid complex.
Therefore, the increased energy transfer efficiency in HCs due to a rise in the PS : LNP value contradicts the idea of enhancing the photodynamic activity of PS.
It should be noted that the interaction between PS and LNP can result in electron transfer. This phenomenon is observed quite rarely and is easily detected with strong changes in the spectral properties of PS due to the formation of radical anions and other derivatives \[[@R63], [@R109]\]. In addition, the electron transfer implies a QD transition to the "off" state, when the model of classical static quenching is appropriate. In this case, the QD luminescence intensity is quenched without a change in its lifetime. Unfortunately, the luminescence lifetime of LNPs has been estimated only in some studies and the absence of such an estimate may lead to a misinterpretation of the experimental results \[[@R52], [@R56]\].
CONCLUSIONS AND FUTURE PROSPECTS
All the mentioned functional relationships between the structural and spectral properties of PSs and LNPs, which can affect the efficiency of LNP as a light collector, and an enhancement of the photodynamic activity of PS in HC can be summarized in a single scheme shown in *[Fig. 6](#F6){ref-type="fig"}*. One can see that all the key characteristics of PS and LNPs are interconnected. Therefore, the full set of parameters optimized so as to ensure the highest ROS yield must involve some degree of compromise.
::: {#F6 .fig}
Scheme showing the functional relationships between the structural parameters of PS/QD molecules and their photophysical properties, as well as the effect of these properties on the yield of reactive oxygen species through the parameters of energy transfer via the FRET mechanism. *F~d~*(*λ*) is the luminescence spectrum of QD; *ε~a~*(*λ*) is the absorption spectrum of PS; and *φ*is the luminescence quantum yield. Green arrows denote the positive correlation; red arrows denote the negative correlation; and blue arrows show the nonlinear dependences
Achieving this compromise is the primary task for PDT on its path to creating third-generation PSs. However, even though an impressive number of studies have been devoted to HCs, the data collected are too fragmentary and heterogeneous, making a global analysis and the selection of the required set of HC characteristics impossible. This would be feasible only by using an integrated approach, when all the connections shown in *[Fig. 6](#F6){ref-type="fig"}* can be identified as quan titative dependences. Since most of these parameters are related to each other by the well-known formulas of the FRET theory, the difficulty arises only at the stage of uncovering the relationship between the structural and photophysical characteristics of the HC components. First of all, this concerns LNPs, since the relationship between the structural and spectral properties of tetrapyrrolic PSs has been studied quite thoroughly.
However, it is not enough to possess information about the properties of each component to optimize the design of the HC. Phenomena such as PS aggregation and static quenching of the luminescence of LNPs (as a result of the formation of nanocrystal surface defects involving PS) can be quantitatively studied only through experiments on HC formation. It should also be noted that electron density perturbation in a PS molecule during the formation of HC (even in the absence of the aforementioned aggregation and quenching effects) has some effect on the photophysical properties of PS and, thus, indirectly affects the energy transfer efficiency and the enhancement of the ROS yield. Failure to take into account any of the parameters described above leads to the following fact: even in the presence of PSs and LNPs with spectral characteristics optimal for FRET, it might not always be possible to obtain HC where enhanced PS fluorescence or the ROS generation rate is observed \[[@R87], [@R98], [@R104], [@R105], [@R106]\]. This usually leads to a rejection of the FRET mechanism as a model for describing the interactions between a nanoparticle and a PS \[[@R51], [@R56], [@R91], [@R93], [@R110]\].
It might be possible to find several variants of complexes significantly differing in terms of their set of internal characteristics but having comparable ROS yields (or comparable in terms of the efficiency of using certain spectral regions for ROS generation) by optimizing the HC design. Since the enhancement of the photodynamic characteristics of PS can be achieved only at low PS : LNP values, when the luminescence of the LNP is not completely quenched, the LNP luminescence can be used for diagnostic purposes. Such HCs can obviously be used to solve specific problems of PDT and fluorescence diagnostics depending on the properties of the target object. In this regard, it must be said that we have discussed the trends in optimizing the HC design exclusively with a view to enhancing the ROS yield. In fact, the overall photodynamic activity will depend not only on the absorption capacity of HC and the ROS yield, but also on the efficiency of interaction between HC and cells, the internalization mechanism, and the stability of HC in the presence of blood components when an HC-based drug is administered to a living being. It is highly likely that the approaches to optimizing HC for increasing the efficiency of targeted delivery will significantly affect the final set of HC parameters. Therefore, the scheme shown in *[Fig. 6](#F6){ref-type="fig"}* should be expanded with allowance for all the aspects of the functional activity of HC as a third-generation photosensitizer. Building a complete scheme of this kind will allow one to take the prospects for using HC with energy transfer in PDT to a fundamentally new level and is, therefore, the main objective of modern medical biophysics.
This study was carried out with the financial support from the Russian Foundation for Basic Research (project No. 20-34-70042).
: hybrid complex
: luminescent nanoparticle
: photodynamic therapy
: semiconductor quantum dot
: reactive oxygen species
|
Page:Lavine - Recipes Tried and True.djvu/26
* 4 ounces grated cheese,
2 ounces butter,
2 ounces inside white bread,
½ pint milk,
2 eggs,
⅓ teaspoon salt,
Cayenne. Mix cheese, butter, bread and beaten yolks, salt, pepper and milk. Put in double boiler, heat until smooth and add beaten whites. Fill ramikinsramekins [sic] ¾ full and put in oven six minutes.
* 2 tablespoons butter,
2 tablespoons chopped, onions,
1½ cans mushrooms chopped (fresh preferred)
1 cup milk,
1½ tablespoons flour,
1 cup chicken meat in disks,
Salt, pepper.
Melt butter; add onion and mushrooms; cook five minutes, add milk with flour. Cook altogether; when thick and smooth add chicken: Heat through, season and serve on buttered toast or in ramikinsramekins [sic].
Chop three and one-half cups chicken very fine, add one pint thick white sauce. Mix as in making rice croquettes; shape and cook the same way.
* Small chicken,
Tablespoon butter,
Tablespoon flour,
½ pint of cream,
1 can mushrooms,
Juice of one lemon,
Yolks of two eggs, salt, pepper.
Parboil chicken, cut into small pieces. Melt butter; add flour, cream, mushrooms. Cook to a thick sauce. Add chicken, lemon juice, eggs, salt and pepper. Grease ramikinsramekins [sic] and bake to a very light brown. Trim with parsley and slices of lemon.
|
<?php
use common\models\PediaUserGroup;
use common\models\PediaUserMember;
use common\models\PediaUserPerm;
use yii\helpers\Html;
use yii\grid\GridView;
/* @var $this yii\web\View */
/* @var $searchModel backend\models\PediaUserAboutusSearch */
/* @var $dataProvider yii\data\ActiveDataProvider */
/** Team:没有蛀牙，NKU
*Coding by 孙一冉，1711297，20190714
*Coding by 王心荻，1711298,20190712
*/
$this->title = 'Pedia User Aboutuses';
$this->params['breadcrumbs'][] = $this->title;
?>
<div class="pedia-user-aboutus-index">
<h1><?= Html::encode($this->title) ?></h1>
<?php
$uid = PediaUserMember::find()->where(['uid' => Yii::$app->user->identity->id])->asArray()->one()['uid'];
if ($uid==1 || $uid==2 || $uid==3 || $uid==4 || $uid==5) {
?><p>
<?= Html::a('Create Pedia User Aboutus', ['create'], ['class' => 'btn btn-success']) ?>
</p><?php
}
?>
<?php // echo $this->render('_search', ['model' => $searchModel]); ?>
<?= GridView::widget([
'dataProvider' => $dataProvider,
'filterModel' => $searchModel,
'columns' => [
['class' => 'yii\grid\SerialColumn'],
'uid',
'sid',
'sname',
'ssex',
'smajor',
//'semail:email',
['class' => 'yii\grid\ActionColumn'],
],
]); ?>
</div>
|
#!/usr/bin/env bash
#/ Usage: ghe-restore-mssql <host>
#/ Restore MSSQL backup to a GitHub Actions service instance.
#/
#/ Note: This script typically isn't called directly. It's invoked by the ghe-restore command.
set -e
# Bring in the backup configuration
# shellcheck source=share/github-backup-utils/ghe-backup-config
. "$( dirname "${BASH_SOURCE[0]}" )/ghe-backup-config"
# Show usage and bail with no arguments
[ -z "$*" ] && print_usage
# Check if the import tool is available in this version
import_tool_available() {
if [ -z "$GHE_TEST_REMOTE_VERSION" ]; then
ghe-ssh "$GHE_HOSTNAME" "test -e /usr/local/bin/ghe-import-mssql"
else
ghe-ssh "$GHE_HOSTNAME" "type ghe-import-mssql"
fi
}
if ! import_tool_available; then
ghe_verbose "ghe-import-mssql is not available"
exit
fi
# Grab host arg
GHE_HOSTNAME="$1"
# Perform a host-check and establish the remote version in GHE_REMOTE_VERSION.
ghe_remote_version_required "$GHE_HOSTNAME"
# The snapshot to restore should be set by the ghe-restore command but this lets
# us run this script directly.
: ${GHE_RESTORE_SNAPSHOT:=current}
# The directory holding the snapshot to restore
snapshot_dir_mssql="$GHE_DATA_DIR/$GHE_RESTORE_SNAPSHOT/mssql"
# Transfer backup files from appliance to backup host
appliance_dir="$GHE_REMOTE_DATA_USER_DIR/mssql/backups"
echo "set -o pipefail; sudo rm -rf $appliance_dir; sudo mkdir -p $appliance_dir" | ghe-ssh $GHE_HOSTNAME /bin/bash
for b in $snapshot_dir_mssql/*
do
[[ -e "$b" ]] || break
filename="${b##*/}"
ghe_verbose "Transferring $filename to appliance host"
cat $snapshot_dir_mssql/$filename | ghe-ssh $GHE_HOSTNAME "sudo tee -a $appliance_dir/$filename >/dev/null 2>&1"
done
# Change owner to mssql:mssql to ready for restore
ghe-ssh $GHE_HOSTNAME "sudo chown -R mssql:mssql $appliance_dir"
# Invoke restore command
bm_start "$(basename $0)"
ghe-ssh "$GHE_HOSTNAME" -- "ghe-import-mssql" < "/dev/null" 1>&3
bm_end "$(basename $0)"
|
Alloplastic adaptation
Alloplastic adaptation (from the Greek word "allos", meaning "other") is a form of adaptation where the subject attempts to change the environment when faced with a difficult situation. Criminality, mental illness, and activism can all be classified as categories of alloplastic adaptation.
The concept of alloplastic adaptation was developed by Sigmund Freud, Sándor Ferenczi, and Franz Alexander. They proposed that when an individual was presented with a stressful situation, he could react in one of two ways:
* Autoplastic adaptation: The subject tries to change himself, i.e. the internal environment.
* Alloplastic adaptation: The subject tries to change the situation, i.e. the external environment.
Origins and development
'These terms are possibly due to Ferenczi, who used them in a paper on "The Phenomenon of Hysterical Materialization" (1919,24). But he there appears to attribute them to Freud' (who may have used them previously in private correspondence or conversation). Ferenczi linked 'the purely "autoplastic" tricks of the hysteric...[to] the bodily performances of "artists" and actors'.
Freud's only public use of the terms was in his paper "The Loss of Reality in Neurosis and Psychosis" (1924), where he points out that 'expedient, normal behaviour leads to work being carried out on the external world; it does not stop, as in psychosis, at effecting internal changes. It is no longer autoplastic but alloplastic '.
A few years later, in his paper on "The Neurotic Character" (1930), Alexander described 'a type of neurosis in which...the patient's entire life consists of actions not adapted to reality but rather aimed at relieving unconscious tensions'. Alexander considered that 'neurotic characters of this type are more easily accessible to psychoanalysis than patients with symptom neuroses...[due] to the fact that in the latter the patient has regressed from alloplasticity to autoplasticity; after successful analysis he must pluck up courage to take action in real life'.
Otto Fenichel however took issue with Alexander on this point, maintaining that 'The pseudo-alloplastic attitude of the neurotic character cannot be changed into a healthy alloplastic one except by first being transformed, for a time, into a neurotic autoplastic attitude, which can then be treated like an ordinary symptom neurosis'.
Human evolution
Alloplasticity has also been used to describe humanity's cultural "evolution". Man's 'evolution by culture...is through alloplastic experiment with objects outside his own body....Unlike autoplastic experiments, alloplastic ones are both replicable and reversible'.
In particular, 'advanced technological societies...are generally characterized by "alloplastic" relations with the environment, involving the manipulation of the environment itself'.
|
rescue retry Ruby
Returning to Ruby after a long break, I'm trying to run a rescue retry block with an RSpec assertion with Capybara / Cucumber. I have the following which is purposely designed to fail to test my retry. It doesn't appear to be running the retry, I have gotten confused:
begin
retries ||= 2
a = 1
a.eql? 2 # false
raise
rescue
puts 'Retrying assertion for failed step'
retries -= 1
if retries > 0
sleep 0.5 # allows render of screen content
retry
end
end
I do suspect I've written something wrong here. Is this the case?
Could you provice a MVCE, ie an example without rspec involved?
Edited, is that OK?
I thought you were asking about the RSpec test. Now after the edit I have no idea what you are asking - the code correctly retries twice then exits.
edited version works correctly on my machine
Works for me, Ruby 2.5.5.
unusually, I wasn't getting the puts in console even though the statement was false.
RSpec works by throwing RSpec::Expectations::ExpectationNotMetError when an expect fails. You are catching it with your unlimited rescue, so RSpec never sees it, which makes your test pass. Never ever use unlimited rescue. Always use a typed rescue, with the most general type being StandardError (not Exception!) - but make it as tight and specific as possible.
If you meant to catch ExpectationNotMetError and retry twice, then let it happen afterwards, you need to reraise it (using plain raise) for RSpec to see it, otherwise Ruby considers it to be handled and execution continues normally (and RSpec doesn't see it). You should still rescue it specifically, just to be safe from other possible errors you could do in the rescued block.
*) unless you know that exactly one thing can go wrong (and even then triple-check).
|
User:Batfan13
Batfan13's Talk Page
Can't wait for Arkham Three
Stuff I did
Crazy Quilt II
Gaggy
Maggie Kyle
The Crusader
Fireball
Mister Hammer
Sickle
The Lion
The Unicorn
The Walrus
The Carpenter
The Broker
Doctor Aesop
Bedbug
Alisa Adams
The Alstairean
Vicki Vale
March Harriet
The Mortician
Alyce Sinner
Simon Burton
Sylvia Sinclair
Boneblaster
Carla Vitti
Johnny Vitti
Luigi Maroni
Contributions
Batman: Arkham City
Young Justice
Batman: The Brave and The Bold
Batman: Arkham Asylum
Gotham City Sirens Issue 1
To...
Gotham City Sirens Issue 26
My favorite pages
* Add links to your favorite pages on the wiki here!
* Favorite page #2
* Favorite page #3
To Do
Next Cheshire, Pino Maroni, Umberto Maroni, and Janice Porter
Origin
Starting Out
Justice League: The Rise of Arsenal and Deathstroke's Titans
Teen Titans Animated Series
Young Justice
|
'use strict'
const la = require('lazy-ass')
const is = require('check-more-types')
function hasVersionSeparator (s) {
return s.indexOf('@', 1) > 0
}
function isScopedName (s) {
return /^@/.test(s)
}
function splitVersion (name, version) {
la(is.unemptyString(name), 'missing string', name)
if (hasVersionSeparator(name) && !version) {
let parts = name.split('@')
if (isScopedName(name)) {
name = '@' + parts[1]
version = parts[2]
} else {
name = parts[0]
version = parts[1]
}
}
return {
name: name,
version: version
}
}
module.exports = splitVersion
|
selected items list empty when maxSelectedItems=1
Hello,
here is example, what I want to do (everything works):
http://codepen.io/anon/pen/RrWJLb
(shortly: max-select-items=1 and set initial value with external-model)
I've tried to do the same in my project, but 'Selected Items:' list is empty (sorry, I couldn't replicate the problem in codepen, I guess it may be connected with using ionic menu )...
Here are my conclusions after few hours of debugging:
value of ng-model is correct
selected item exist in DOM but is not visible
condition "!viewModel.isArray(viewModel.selectedItems)" returns true (line 88 in master - ng-show condition in template)
when max-selected-items=2, selected items list is viewed correctly
My solution: when I've changed 'ng-show' to 'ng-if' (line 88, master) everything works perfectly (as in example)
Hi Przemysław,
thanks for reporting this issue. I just fixed this on the master. Could you maybe test it again and give me feedback such that I can close the issue?
Happy christmas and regards,
Guy
Hi,
I've just tested, and everything seems to work correctly, so You can close the issue.
Thanks a lot,
Przemek
|
ἰοὺ ἰού: exclamation of surprise and wonder, usually with a sideidea of ill-treatment (σχετλιαστικὸν ἐπίρρημα), as Ar. Nub. 1 ἰοὺ ἰοὺ, Ζεῦ βασιλεύ, τὸ χρῆμα τῶν νυκτῶν ὅσον ἀπέραντον, but it also expresses pleasure, as e.g. Rep. iv. 432 d καὶ ἐγὼ κατιδών, Ἰοὺ ἰού, εἶπον, Γλαύκων: κινδυνεύομέν τι ἔχειν ἴχνος (trace) καί μοι δοκεῖ οὐ πάνυ τι ἐκφευξεῖσθαι ἡμᾶς. Εὖ ἀγγέλλεις, δ̓ ὅς.—
πανοῦργος: sometimes associated with δεινός, denotes a rather excessive adroitness, bordering on rascality, as “artful,” “sly”; also “knavish.”
ὥσπερ παιδί: by a delicate use of his own comparison, Socrates characterizes Callicles' conduct in acting as if he were dealing with boys, not men, as improper and unworthy.—
τότε μὲν αὖ: it must be confessed that αὖ in this position gives trouble. Cron thinks that it recalls a similar allegation in 491 b; but that is rather far-fetched.
καίτοι κτἑ.: in 495 a Socrates' faith in Callicles' παρρησία is shaken; in 497 a, that in his σοφία, and now, that in his εὔνοια.
ἑκόντος εἶναι: on the use of εἶναι in phrases, see GMT. 780 and H. 956 a.
10 f.
κατὰ τὸν πάλαιον λόγον: a common way of introducing a proverb; cf. Symp. 195 b.
τὸ παρὸν εὖ ποιεῖν κτἑ.: a mixture of two proverbs. The first one means literally, to “treat well what is at hand,” i.e. ‘to make the best of what one has,’ according to the English saying. In almost the same sense we use the more colloquial ‘grin and bear it.’ The second proverb, δέχεσθαι τὸ διδόμενον, applies more exactly to the case in point, the διδόμενον being naturally τὸ λεγόμενον. An English proverb which has much the same force is, ‘do not look a gifthorse in the mouth.’ After τοῦτο, τὸ διδόμενον serves for a relative clause.
κακαί: we should naturally ex
This work is licensed under a Creative Commons Attribution-ShareAlike 3.0 United States License.
An XML version of this text is available for download, with the additional restriction that you offer Perseus any modifications you make. Perseus provides credit for all accepted changes, storing new additions in a versioning system.
hide References (3 total)
• Commentary references from this page (3):
• Plato, Gorgias, 491b
• Plato, Gorgias, 495a
• Plato, Gorgias, 497a
hide Display Preferences
Greek Display:
Arabic Display:
View by Default:
Browse Bar:
|
Talk:Season 3/@comment-5204804-20130105125136/@comment-5254771-20130105153430
Yay! I like jabian. I just want it to be mutual, not one chasing the other like in last season
|
import * as THREE from 'three';
import { CONSTANTS, EquirectangularAdapter, PSVError, utils } from '../..';
import { Queue } from '../shared/Queue';
import { Task } from '../shared/Task';
import { buildErrorMaterial, createBaseTexture } from '../shared/tiles-utils';
/**
* @callback TileUrl
* @summary Function called to build a tile url
* @memberOf PSV.adapters.EquirectangularTilesAdapter
* @param {int} col
* @param {int} row
* @returns {string}
*/
/**
* @typedef {Object} PSV.adapters.EquirectangularTilesAdapter.Panorama
* @summary Configuration of a tiled panorama
* @property {string} [baseUrl] - low resolution panorama loaded before tiles
* @property {PSV.PanoData | PSV.PanoDataProvider} [basePanoData] - panoData configuration associated to low resolution panorama loaded before tiles
* @property {int} width - complete panorama width (height is always width/2)
* @property {int} cols - number of vertical tiles
* @property {int} rows - number of horizontal tiles
* @property {PSV.adapters.EquirectangularTilesAdapter.TileUrl} tileUrl - function to build a tile url
*/
/**
* @typedef {Object} PSV.adapters.EquirectangularTilesAdapter.Options
* @property {number} [resolution=64] - number of faces of the sphere geometry, higher values may decrease performances
* @property {boolean} [showErrorTile=true] - shows a warning sign on tiles that cannot be loaded
* @property {boolean} [baseBlur=true] - applies a blur to the low resolution panorama
*/
/**
* @typedef {Object} PSV.adapters.EquirectangularTilesAdapter.Tile
* @private
* @property {int} col
* @property {int} row
* @property {float} angle
*/
/* the faces of the top and bottom rows are made of a single triangle (3 vertices)
* all other faces are made of two triangles (6 vertices)
* bellow is the indexing of each face vertices
*
* first row faces:
* ⋀
* /0\
* / \
* / \
* /1 2\
* ¯¯¯¯¯¯¯¯¯
*
* other rows faces:
* _________
* |\1 0|
* |3\ |
* | \ |
* | \ |
* | \ |
* | \2|
* |4 5\|
* ¯¯¯¯¯¯¯¯¯
*
* last row faces:
* _________
* \1 0/
* \ /
* \ /
* \2/
* ⋁
*/
const ATTR_UV = 'uv';
const ATTR_ORIGINAL_UV = 'originaluv';
const ATTR_POSITION = 'position';
function tileId(tile) {
return `${tile.col}x${tile.row}`;
}
const frustum = new THREE.Frustum();
const projScreenMatrix = new THREE.Matrix4();
const vertexPosition = new THREE.Vector3();
/**
* @summary Adapter for tiled panoramas
* @memberof PSV.adapters
* @extends PSV.adapters.AbstractAdapter
*/
export class EquirectangularTilesAdapter extends EquirectangularAdapter {
static id = 'equirectangular-tiles';
static supportsDownload = false;
/**
* @param {PSV.Viewer} psv
* @param {PSV.adapters.EquirectangularTilesAdapter.Options} options
*/
constructor(psv, options) {
super(psv);
this.psv.config.useXmpData = false;
/**
* @member {PSV.adapters.EquirectangularTilesAdapter.Options}
* @private
*/
this.config = {
resolution : 64,
showErrorTile: true,
baseBlur : true,
...options,
};
if (!utils.isPowerOfTwo(this.config.resolution)) {
throw new PSVError('EquirectangularAdapter resolution must be power of two');
}
this.SPHERE_SEGMENTS = this.config.resolution;
this.SPHERE_HORIZONTAL_SEGMENTS = this.SPHERE_SEGMENTS / 2;
this.NB_VERTICES_BY_FACE = 6;
this.NB_VERTICES_BY_SMALL_FACE = 3;
this.NB_VERTICES = 2 * this.SPHERE_SEGMENTS * this.NB_VERTICES_BY_SMALL_FACE
+ (this.SPHERE_HORIZONTAL_SEGMENTS - 2) * this.SPHERE_SEGMENTS * this.NB_VERTICES_BY_FACE;
this.NB_GROUPS = this.SPHERE_SEGMENTS * this.SPHERE_HORIZONTAL_SEGMENTS;
/**
* @member {PSV.adapters.Queue}
* @private
*/
this.queue = new Queue();
/**
* @type {Object}
* @property {int} colSize - size in pixels of a column
* @property {int} rowSize - size in pixels of a row
* @property {int} facesByCol - number of mesh faces by column
* @property {int} facesByRow - number of mesh faces by row
* @property {Record<string, boolean>} tiles - loaded tiles
* @property {external:THREE.SphereGeometry} geom
* @property {external:THREE.MeshBasicMaterial[]} materials
* @property {external:THREE.MeshBasicMaterial} errorMaterial
* @private
*/
this.prop = {
colSize : 0,
rowSize : 0,
facesByCol : 0,
facesByRow : 0,
tiles : {},
geom : null,
materials : [],
errorMaterial: null,
};
/**
* @member {external:THREE.ImageLoader}
* @private
*/
this.loader = new THREE.ImageLoader();
if (this.psv.config.withCredentials) {
this.loader.setWithCredentials(true);
}
if (this.psv.config.requestHeaders && typeof this.psv.config.requestHeaders === 'object') {
this.loader.setRequestHeader(this.psv.config.requestHeaders);
}
this.psv.on(CONSTANTS.EVENTS.POSITION_UPDATED, this);
this.psv.on(CONSTANTS.EVENTS.ZOOM_UPDATED, this);
}
/**
* @override
*/
destroy() {
this.psv.off(CONSTANTS.EVENTS.POSITION_UPDATED, this);
this.psv.off(CONSTANTS.EVENTS.ZOOM_UPDATED, this);
this.__cleanup();
this.prop.errorMaterial?.map?.dispose();
this.prop.errorMaterial?.dispose();
delete this.queue;
delete this.loader;
delete this.prop.geom;
delete this.prop.errorMaterial;
super.destroy();
}
/**
* @private
*/
handleEvent(e) {
/* eslint-disable */
switch (e.type) {
case CONSTANTS.EVENTS.POSITION_UPDATED:
case CONSTANTS.EVENTS.ZOOM_UPDATED:
this.__refresh();
break;
}
/* eslint-enable */
}
/**
* @summary Clears loading queue, dispose all materials
* @private
*/
__cleanup() {
this.queue.clear();
this.prop.tiles = {};
this.prop.materials.forEach((mat) => {
mat?.map?.dispose();
mat?.dispose();
});
this.prop.materials.length = 0;
}
/**
* @override
*/
supportsTransition(panorama) {
return !!panorama.baseUrl;
}
/**
* @override
*/
supportsPreload(panorama) {
return !!panorama.baseUrl;
}
/**
* @override
* @param {PSV.adapters.EquirectangularTilesAdapter.Panorama} panorama
* @returns {Promise.<PSV.TextureData>}
*/
loadTexture(panorama) {
if (typeof panorama !== 'object' || !panorama.width || !panorama.cols || !panorama.rows || !panorama.tileUrl) {
return Promise.reject(new PSVError('Invalid panorama configuration, are you using the right adapter?'));
}
if (panorama.cols > this.SPHERE_SEGMENTS) {
return Promise.reject(new PSVError(`Panorama cols must not be greater than ${this.SPHERE_SEGMENTS}.`));
}
if (panorama.rows > this.SPHERE_HORIZONTAL_SEGMENTS) {
return Promise.reject(new PSVError(`Panorama rows must not be greater than ${this.SPHERE_HORIZONTAL_SEGMENTS}.`));
}
if (!utils.isPowerOfTwo(panorama.cols) || !utils.isPowerOfTwo(panorama.rows)) {
return Promise.reject(new PSVError('Panorama cols and rows must be powers of 2.'));
}
const panoData = {
fullWidth : panorama.width,
fullHeight : panorama.width / 2,
croppedWidth : panorama.width,
croppedHeight: panorama.width / 2,
croppedX : 0,
croppedY : 0,
poseHeading : 0,
posePitch : 0,
poseRoll : 0,
};
if (panorama.baseUrl) {
return super.loadTexture(panorama.baseUrl, panorama.basePanoData)
.then(textureData => ({
panorama: panorama,
texture : textureData.texture,
panoData: panoData,
}));
}
else {
return Promise.resolve({ panorama, panoData });
}
}
/**
* @override
*/
createMesh(scale = 1) {
const geometry = new THREE.SphereGeometry(
CONSTANTS.SPHERE_RADIUS * scale,
this.SPHERE_SEGMENTS,
this.SPHERE_HORIZONTAL_SEGMENTS,
-Math.PI / 2
)
.scale(-1, 1, 1)
.toNonIndexed();
geometry.clearGroups();
let i = 0;
let k = 0;
// first row
for (; i < this.SPHERE_SEGMENTS * this.NB_VERTICES_BY_SMALL_FACE; i += this.NB_VERTICES_BY_SMALL_FACE) {
geometry.addGroup(i, this.NB_VERTICES_BY_SMALL_FACE, k++);
}
// second to before last rows
for (; i < this.NB_VERTICES - this.SPHERE_SEGMENTS * this.NB_VERTICES_BY_SMALL_FACE; i += this.NB_VERTICES_BY_FACE) {
geometry.addGroup(i, this.NB_VERTICES_BY_FACE, k++);
}
// last row
for (; i < this.NB_VERTICES; i += this.NB_VERTICES_BY_SMALL_FACE) {
geometry.addGroup(i, this.NB_VERTICES_BY_SMALL_FACE, k++);
}
geometry.setAttribute(ATTR_ORIGINAL_UV, geometry.getAttribute(ATTR_UV).clone());
return new THREE.Mesh(geometry, []);
}
/**
* @summary Applies the base texture and starts the loading of tiles
* @override
*/
setTexture(mesh, textureData, transition) {
const { panorama, texture } = textureData;
if (transition) {
this.__setTexture(mesh, texture);
return;
}
this.__cleanup();
this.__setTexture(mesh, texture);
this.prop.materials = mesh.material;
this.prop.geom = mesh.geometry;
this.prop.geom.setAttribute(ATTR_UV, this.prop.geom.getAttribute(ATTR_ORIGINAL_UV).clone());
this.prop.colSize = panorama.width / panorama.cols;
this.prop.rowSize = panorama.width / 2 / panorama.rows;
this.prop.facesByCol = this.SPHERE_SEGMENTS / panorama.cols;
this.prop.facesByRow = this.SPHERE_HORIZONTAL_SEGMENTS / panorama.rows;
// this.psv.renderer.scene.add(createWireFrame(this.prop.geom));
setTimeout(() => this.__refresh(true));
}
/**
* @private
*/
__setTexture(mesh, texture) {
let material;
if (texture) {
material = new THREE.MeshBasicMaterial({ map: texture });
}
else {
material = new THREE.MeshBasicMaterial({ opacity: 0, transparent: true });
}
for (let i = 0; i < this.NB_GROUPS; i++) {
mesh.material.push(material);
}
}
/**
* @override
*/
setTextureOpacity(mesh, opacity) {
mesh.material[0].opacity = opacity;
mesh.material[0].transparent = opacity < 1;
}
/**
* @summary Compute visible tiles and load them
* @param {boolean} [init=false] Indicates initial call
* @private
*/
__refresh(init = false) { // eslint-disable-line no-unused-vars
if (!this.prop.geom) {
return;
}
const camera = this.psv.renderer.camera;
camera.updateMatrixWorld();
projScreenMatrix.multiplyMatrices(camera.projectionMatrix, camera.matrixWorldInverse);
frustum.setFromProjectionMatrix(projScreenMatrix);
const panorama = this.psv.config.panorama;
const verticesPosition = this.prop.geom.getAttribute(ATTR_POSITION);
const tilesToLoad = [];
for (let col = 0; col < panorama.cols; col++) {
for (let row = 0; row < panorama.rows; row++) {
// for each tile, find the vertices corresponding to the four corners (three for first and last rows)
// if at least one vertex is visible, the tile must be loaded
// for larger tiles we also test the four edges centers and the tile center
const verticesIndex = [];
if (row === 0) {
// bottom-left
const v0 = this.prop.facesByRow === 1
? col * this.prop.facesByCol * this.NB_VERTICES_BY_SMALL_FACE + 1
: this.SPHERE_SEGMENTS * this.NB_VERTICES_BY_SMALL_FACE
+ (this.prop.facesByRow - 2) * this.SPHERE_SEGMENTS * this.NB_VERTICES_BY_FACE
+ col * this.prop.facesByCol * this.NB_VERTICES_BY_FACE + 4;
// bottom-right
const v1 = this.prop.facesByRow === 1
? v0 + (this.prop.facesByCol - 1) * this.NB_VERTICES_BY_SMALL_FACE + 1
: v0 + (this.prop.facesByCol - 1) * this.NB_VERTICES_BY_FACE + 1;
// top (all vertices are equal)
const v2 = 0;
verticesIndex.push(v0, v1, v2);
if (this.prop.facesByCol >= this.SPHERE_SEGMENTS / 8) {
// bottom-center
const v4 = v0 + this.prop.facesByCol / 2 * this.NB_VERTICES_BY_FACE;
verticesIndex.push(v4);
}
if (this.prop.facesByRow >= this.SPHERE_HORIZONTAL_SEGMENTS / 4) {
// left-center
const v6 = v0 - this.prop.facesByRow / 2 * this.SPHERE_SEGMENTS * this.NB_VERTICES_BY_FACE;
// right-center
const v7 = v1 - this.prop.facesByRow / 2 * this.SPHERE_SEGMENTS * this.NB_VERTICES_BY_FACE;
verticesIndex.push(v6, v7);
}
}
else if (row === panorama.rows - 1) {
// top-left
const v0 = this.prop.facesByRow === 1
? -this.SPHERE_SEGMENTS * this.NB_VERTICES_BY_SMALL_FACE
+ row * this.prop.facesByRow * this.SPHERE_SEGMENTS * this.NB_VERTICES_BY_FACE
+ col * this.prop.facesByCol * this.NB_VERTICES_BY_SMALL_FACE + 1
: -this.SPHERE_SEGMENTS * this.NB_VERTICES_BY_SMALL_FACE
+ row * this.prop.facesByRow * this.SPHERE_SEGMENTS * this.NB_VERTICES_BY_FACE
+ col * this.prop.facesByCol * this.NB_VERTICES_BY_FACE + 1;
// top-right
const v1 = this.prop.facesByRow === 1
? v0 + (this.prop.facesByCol - 1) * this.NB_VERTICES_BY_SMALL_FACE - 1
: v0 + (this.prop.facesByCol - 1) * this.NB_VERTICES_BY_FACE - 1;
// bottom (all vertices are equal)
const v2 = this.NB_VERTICES - 1;
verticesIndex.push(v0, v1, v2);
if (this.prop.facesByCol >= this.SPHERE_SEGMENTS / 8) {
// top-center
const v4 = v0 + this.prop.facesByCol / 2 * this.NB_VERTICES_BY_FACE;
verticesIndex.push(v4);
}
if (this.prop.facesByRow >= this.SPHERE_HORIZONTAL_SEGMENTS / 4) {
// left-center
const v6 = v0 + this.prop.facesByRow / 2 * this.SPHERE_SEGMENTS * this.NB_VERTICES_BY_FACE;
// right-center
const v7 = v1 + this.prop.facesByRow / 2 * this.SPHERE_SEGMENTS * this.NB_VERTICES_BY_FACE;
verticesIndex.push(v6, v7);
}
}
else {
// top-left
const v0 = -this.SPHERE_SEGMENTS * this.NB_VERTICES_BY_SMALL_FACE
+ row * this.prop.facesByRow * this.SPHERE_SEGMENTS * this.NB_VERTICES_BY_FACE
+ col * this.prop.facesByCol * this.NB_VERTICES_BY_FACE + 1;
// bottom-left
const v1 = v0 + (this.prop.facesByRow - 1) * this.SPHERE_SEGMENTS * this.NB_VERTICES_BY_FACE + 3;
// bottom-right
const v2 = v1 + (this.prop.facesByCol - 1) * this.NB_VERTICES_BY_FACE + 1;
// top-right
const v3 = v0 + (this.prop.facesByCol - 1) * this.NB_VERTICES_BY_FACE - 1;
verticesIndex.push(v0, v1, v2, v3);
if (this.prop.facesByCol >= this.SPHERE_SEGMENTS / 8) {
// top-center
const v4 = v0 + this.prop.facesByCol / 2 * this.NB_VERTICES_BY_FACE;
// bottom-center
const v5 = v1 + this.prop.facesByCol / 2 * this.NB_VERTICES_BY_FACE;
verticesIndex.push(v4, v5);
}
if (this.prop.facesByRow >= this.SPHERE_HORIZONTAL_SEGMENTS / 4) {
// left-center
const v6 = v0 + this.prop.facesByRow / 2 * this.SPHERE_SEGMENTS * this.NB_VERTICES_BY_FACE;
// right-center
const v7 = v3 + this.prop.facesByRow / 2 * this.SPHERE_SEGMENTS * this.NB_VERTICES_BY_FACE;
verticesIndex.push(v6, v7);
if (this.prop.facesByCol >= this.SPHERE_SEGMENTS / 8) {
// center-center
const v8 = v6 + this.prop.facesByCol / 2 * this.NB_VERTICES_BY_FACE;
verticesIndex.push(v8);
}
}
}
// if (init && col === 0 && row === 0) {
// verticesIndex.forEach((vertexIdx) => {
// this.psv.renderer.scene.add(createDot(
// verticesPosition.getX(vertexIdx),
// verticesPosition.getY(vertexIdx),
// verticesPosition.getZ(vertexIdx)
// ));
// });
// }
const vertexVisible = verticesIndex.some((vertexIdx) => {
vertexPosition.set(
verticesPosition.getX(vertexIdx),
verticesPosition.getY(vertexIdx),
verticesPosition.getZ(vertexIdx)
);
vertexPosition.applyEuler(this.psv.renderer.meshContainer.rotation);
return frustum.containsPoint(vertexPosition);
});
if (vertexVisible) {
let angle = vertexPosition.angleTo(this.psv.prop.direction);
if (row === 0 || row === panorama.rows - 1) {
angle *= 2; // lower priority to top and bottom tiles
}
tilesToLoad.push({ col, row, angle });
}
}
}
this.__loadTiles(tilesToLoad);
}
/**
* @summary Loads tiles and change existing tiles priority
* @param {PSV.adapters.EquirectangularTilesAdapter.Tile[]} tiles
* @private
*/
__loadTiles(tiles) {
this.queue.disableAllTasks();
tiles.forEach((tile) => {
const id = tileId(tile);
if (this.prop.tiles[id]) {
this.queue.setPriority(id, tile.angle);
}
else {
this.prop.tiles[id] = true;
this.queue.enqueue(new Task(id, tile.angle, task => this.__loadTile(tile, task)));
}
});
this.queue.start();
}
/**
* @summary Loads and draw a tile
* @param {PSV.adapters.EquirectangularTilesAdapter.Tile} tile
* @param {PSV.adapters.Task} task
* @return {Promise}
* @private
*/
__loadTile(tile, task) {
const panorama = this.psv.config.panorama;
const url = panorama.tileUrl(tile.col, tile.row);
if (this.psv.config.requestHeaders && typeof this.psv.config.requestHeaders === 'function') {
this.loader.setRequestHeader(this.psv.config.requestHeaders(url));
}
return new Promise((resolve, reject) => {
this.loader.load(url, resolve, undefined, reject);
})
.then((image) => {
if (!task.isCancelled()) {
const material = new THREE.MeshBasicMaterial({ map: utils.createTexture(image) });
this.__swapMaterial(tile.col, tile.row, material);
this.psv.needsUpdate();
}
})
.catch(() => {
if (!task.isCancelled() && this.config.showErrorTile) {
if (!this.prop.errorMaterial) {
this.prop.errorMaterial = buildErrorMaterial(this.prop.colSize, this.prop.rowSize);
}
this.__swapMaterial(tile.col, tile.row, this.prop.errorMaterial);
this.psv.needsUpdate();
}
});
}
/**
* @summary Applies a new texture to the faces
* @param {int} col
* @param {int} row
* @param {external:THREE.MeshBasicMaterial} material
* @private
*/
__swapMaterial(col, row, material) {
const uvs = this.prop.geom.getAttribute(ATTR_UV);
for (let c = 0; c < this.prop.facesByCol; c++) {
for (let r = 0; r < this.prop.facesByRow; r++) {
// position of the face (two triangles of the same square)
const faceCol = col * this.prop.facesByCol + c;
const faceRow = row * this.prop.facesByRow + r;
const isFirstRow = faceRow === 0;
const isLastRow = faceRow === (this.SPHERE_HORIZONTAL_SEGMENTS - 1);
// first vertex for this face (3 or 6 vertices in total)
let firstVertex;
if (isFirstRow) {
firstVertex = faceCol * this.NB_VERTICES_BY_SMALL_FACE;
}
else if (isLastRow) {
firstVertex = this.NB_VERTICES
- this.SPHERE_SEGMENTS * this.NB_VERTICES_BY_SMALL_FACE
+ faceCol * this.NB_VERTICES_BY_SMALL_FACE;
}
else {
firstVertex = this.SPHERE_SEGMENTS * this.NB_VERTICES_BY_SMALL_FACE
+ (faceRow - 1) * this.SPHERE_SEGMENTS * this.NB_VERTICES_BY_FACE
+ faceCol * this.NB_VERTICES_BY_FACE;
}
// swap material
const matIndex = this.prop.geom.groups.find(g => g.start === firstVertex).materialIndex;
this.prop.materials[matIndex] = material;
// define new uvs
const top = 1 - r / this.prop.facesByRow;
const bottom = 1 - (r + 1) / this.prop.facesByRow;
const left = c / this.prop.facesByCol;
const right = (c + 1) / this.prop.facesByCol;
if (isFirstRow) {
uvs.setXY(firstVertex, (left + right) / 2, top);
uvs.setXY(firstVertex + 1, left, bottom);
uvs.setXY(firstVertex + 2, right, bottom);
}
else if (isLastRow) {
uvs.setXY(firstVertex, right, top);
uvs.setXY(firstVertex + 1, left, top);
uvs.setXY(firstVertex + 2, (left + right) / 2, bottom);
}
else {
uvs.setXY(firstVertex, right, top);
uvs.setXY(firstVertex + 1, left, top);
uvs.setXY(firstVertex + 2, right, bottom);
uvs.setXY(firstVertex + 3, left, top);
uvs.setXY(firstVertex + 4, left, bottom);
uvs.setXY(firstVertex + 5, right, bottom);
}
}
}
uvs.needsUpdate = true;
}
/**
* @summary Create the texture for the base image
* @param {HTMLImageElement} img
* @return {external:THREE.Texture}
* @private
*/
__createBaseTexture(img) {
if (img.width !== img.height * 2) {
utils.logWarn('Invalid base image, the width should be twice the height');
}
return createBaseTexture(img, this.config.baseBlur, w => w / 2);
}
}
|
S3 PutObject fails on Windows with errors depending on the upload size
Describe the bug
I am building aws-sdk-cpp as a static library linked to my application with the following cmake flags:
-DBUILD_ONLY=s3 -DENABLE_TESTING=OFF -DBUILD_SHARED_LIBS=OFF
I am using the SDK to upload files to S3 using the PutObject function of S3Client. The application works fine on Linux, but there are some errors reported on Windows depending on the size of the upload.
When the file to be uploaded is less than 10MB of size the upload fails with the error SignatureDoesNotMatch (<bucket> is only a placeholder for the used bucket name):
[2023-07-14 16:07:29.300] [org::apache::nifi::minifi::aws::utils::AWSSdkLogger] [warning] [WinHttpSyncHttpClient] Failed setting TCP keep-alive interval with error code: 12018
[2023-07-14 16:07:29.300] [org::apache::nifi::minifi::aws::utils::AWSSdkLogger] [error] [WinHttpSyncHttpClient] Failed to add HTTP request headers: amz-sdk-invocation-id: A47F213E-E882-4874-A672-476928DCF98D
amz-sdk-request: attempt=1
authorization: AWS4-HMAC-SHA256 Credential=AKIAUYLDB5SQVHSVDTJS/20230714/eu-west-2/s3/aws4_request, SignedHeaders=amz-sdk-invocation-id;amz-sdk-request;content-length;content-md5;content-type;host;x-amz-content-sha256;x-amz-date;x-amz-grant-full-control;x-amz-grant-read;x-amz-grant-read-acp;x-amz-grant-write-acp;x-amz-server-side-encryption;x-amz-storage-class, Signature=cb2bb298a825a9c44fe8901f8aecc50cf1301e1c850e20dd1144e73ea313b27a
content-length: 13
content-md5: ZajifYh5KDgxtmS9i38K1A==
content-type: application/octet-stream
host: <bucket>.s3.eu-west-2.amazonaws.com
user-agent: aws-sdk-cpp/1.11.118 Windows/10.0.19041.3155 AMD64 MSVC/1929
x-amz-content-sha256: UNSIGNED-PAYLOAD
x-amz-date: 20230714T140729Z
x-amz-grant-full-control:
x-amz-grant-read:
x-amz-grant-read-acp:
x-amz-grant-write-acp:
x-amz-server-side-encryption:
x-amz-storage-class: STANDARD
, with error code: 12150
[2023-07-14 16:07:29.458] [org::apache::nifi::minifi::aws::utils::AWSSdkLogger] [warning] [AWSErrorMarshaller] Encountered AWSError 'SignatureDoesNotMatch': The request signature we calculated does not match the signature you provided. Check your key and signing method.
[2023-07-14 16:07:29.458] [org::apache::nifi::minifi::aws::utils::AWSSdkLogger] [error] [AWSXmlClient] HTTP response code: 403
Resolved remote host IP address:
Request ID: EF8H8BECB3N9KE0A
Exception name: SignatureDoesNotMatch
Error message: The request signature we calculated does not match the signature you provided. Check your key and signing method.
7 response headers:
connection : close
content-type : application/xml
date : Fri, 14 Jul 2023 14:07:27 GMT
server : AmazonS3
transfer-encoding : chunked
x-amz-id-2 : 6gApL4IUcv8x1DyoE2jrmips9TvoCzQJsYPywjgYQA/BAb0oUUQ3fP1b6qDCUcxwn349+Wxnii4=
x-amz-request-id : EF8H8BECB3N9KE0A
[2023-07-14 16:07:29.458] [org::apache::nifi::minifi::aws::utils::AWSSdkLogger] [warning] [AWSClient] If the signature check failed. This could be because of a time skew. Attempting to adjust the signer.
[2023-07-14 16:07:29.458] [org::apache::nifi::minifi::aws::s3::S3RequestSender] [error] PutS3Object failed with the following: 'The request signature we calculated does not match the signature you provided. Check your key and signing method.'
[2023-07-14 16:07:29.459] [org::apache::nifi::minifi::aws::utils::AWSSdkLogger] [info] [WinHttpConnectionPoolMgr] Cleaning up connection pool mgr.
When the file to be uploaded is larger than 10MB it fails with a network error:
[2023-07-14 15:07:15.931] [org::apache::nifi::minifi::aws::utils::AWSSdkLogger] [info] [WinHttpConnectionPoolMgr] Attempting to acquire connection for <bucket>.s3.eu-west-2.amazonaws.com:443
[2023-07-14 15:07:15.931] [org::apache::nifi::minifi::aws::utils::AWSSdkLogger] [info] [WinHttpConnectionPoolMgr] Connection now available, continuing.
[2023-07-14 15:07:15.932] [org::apache::nifi::minifi::aws::utils::AWSSdkLogger] [warning] [WinHttpSyncHttpClient] Failed setting TCP keep-alive interval with error code: 12018
[2023-07-14 15:07:15.932] [org::apache::nifi::minifi::aws::utils::AWSSdkLogger] [error] [WinHttpSyncHttpClient] Failed to add HTTP request headers: amz-sdk-invocation-id: 5D7FBB4D-C082-4F1D-A747-873F1EF29A74
amz-sdk-request: attempt=11; max=11
authorization: AWS4-HMAC-SHA256 Credential=AKIAUYLDB5SQVHSVDTJS/20230714/eu-west-2/s3/aws4_request, SignedHeaders=amz-sdk-invocation-id;amz-sdk-request;content-length;content-md5;content-type;host;x-amz-content-sha256;x-amz-date;x-amz-grant-full-control;x-amz-grant-read;x-amz-grant-read-acp;x-amz-grant-write-acp;x-amz-server-side-encryption;x-amz-storage-class, Signature=f409939221b771de925e3186bb55e4b9d2eede605d0778e78d387ab485225bc5
content-length: 104857600
content-md5: zCK33pOsKi8NW/JWyU1+Zg==
content-type: application/octet-stream
host: <bucket>.s3.eu-west-2.amazonaws.com
user-agent: aws-sdk-cpp/1.11.118 Windows/10.0.19041.3155 AMD64 MSVC/1929
x-amz-content-sha256: UNSIGNED-PAYLOAD
x-amz-date: 20230714T130715Z
x-amz-grant-full-control:
x-amz-grant-read:
x-amz-grant-read-acp:
x-amz-grant-write-acp:
x-amz-server-side-encryption:
x-amz-storage-class: STANDARD
, with error code: 12150
[2023-07-14 15:07:17.661] [org::apache::nifi::minifi::aws::utils::AWSSdkLogger] [warning] [WinHttpSyncHttpClient] Send request failed: The connection with the server was terminated abnormally
[2023-07-14 15:07:17.661] [org::apache::nifi::minifi::aws::utils::AWSSdkLogger] [error] [AWSXmlClient] HTTP response code: -1
Resolved remote host IP address:
Request ID:
Exception name:
Error message: Encountered network error when sending http request
0 response headers:
[2023-07-14 15:07:17.661] [org::apache::nifi::minifi::aws::utils::AWSSdkLogger] [warning] [AWSClient] If the signature check failed. This could be because of a time skew. Attempting to adjust the signer.
[2023-07-14 15:07:17.661] [org::apache::nifi::minifi::aws::s3::S3RequestSender] [error] PutS3Object failed with the following: 'Encountered network error when sending http request'
First tried with version 1.10.48, but also tried the latest version 1.11.118 with the same result. The issue was tested on AWS S3, but the same issue was reported when using S3 compatible storages: VAST S3 and MinIO S3
Suspected a firewall issue, but disabling the firewall had no effect.
Expected Behavior
PutObject call should succeed.
Current Behavior
PutObject failed.
Reproduction Steps
Aws::Auth::AWSCredentials = aws_credentials_provider_.getAWSCredentials();
auto client_config = Aws::Client::ClientConfiguration();
Aws::S3::Model::PutObjectRequest request;
request.SetBucket("bucket");
request.SetKey("key");
auto stream = std::make_sharedstd::stringstream();
(*stream) << "Hello, World!";
request.SetBody(data_stream);
Aws::S3::S3Client s3_client(credentials, client_config, Aws::Client::AWSAuthV4Signer::PayloadSigningPolicy::Never, true);
auto outcome = s3_client.PutObject(request);
Possible Solution
No response
Additional Information/Context
No response
AWS CPP SDK version used
1.11.118 and 1.10.48
Compiler and Version used
Visual Studio 2019, MSVC 14.29.30133
Operating System and version
Windows 10
Hi @yasminetalby,
Thank you for the quick response! I collected trace logs from an 8MB and a 12MB file upload:
aws_failure_8MB.log
aws_failure_12MB.log
In the meantime I tried building the library with the USE_CRT_HTTP_CLIENT=ON flag on version 1.11.118 to use the CRT HTTP client instead of the winhttp calls. I ran into this issue as I also set the server side encryption every time with the default value of NOT_SET and due to this the upload failed. After fixing the issue with the proposed workaround the upload succeeded on Windows with the CRT HTTP client. Do you think this could be a good temporary workaround until this issue is figured out? Which one is the preferred, more future proof approach, using the CRT HTTP client on all platforms or the platform specific WinHTTP on Windows and Curl on Linux?
BR,
Gabor
Some additional info regarding the CRT HTTP client:
I tested it on Ubuntu 22.04 as well, and while the Curl backend constantly succeeds there seems to be random failures with the CRT client with the error Request Timeout Has Expired, see the attached trace logs for more information. Could this be due to some configuration issue?
[2023-07-18 14:21:23.413] [org::apache::nifi::minifi::aws::utils::AWSSdkLogger] [trace] [Aws::Endpoint::DefaultEndpointProvider] Endpoint str eval parameter: Region = eu-west-2
[2023-07-18 14:21:23.413] [org::apache::nifi::minifi::aws::utils::AWSSdkLogger] [trace] [Aws::Endpoint::DefaultEndpointProvider] Endpoint bool eval parameter: UseFIPS = 0
[2023-07-18 14:21:23.413] [org::apache::nifi::minifi::aws::utils::AWSSdkLogger] [trace] [Aws::Endpoint::DefaultEndpointProvider] Endpoint bool eval parameter: UseDualStack = 0
[2023-07-18 14:21:23.413] [org::apache::nifi::minifi::aws::utils::AWSSdkLogger] [trace] [Aws::Endpoint::DefaultEndpointProvider] Endpoint bool eval parameter: UseArnRegion = 0
[2023-07-18 14:21:23.413] [org::apache::nifi::minifi::aws::utils::AWSSdkLogger] [trace] [Aws::Endpoint::DefaultEndpointProvider] Endpoint bool eval parameter: DisableMultiRegionAccessPoints = 0
[2023-07-18 14:21:23.413] [org::apache::nifi::minifi::aws::utils::AWSSdkLogger] [trace] [Aws::Endpoint::DefaultEndpointProvider] Endpoint str eval parameter: Bucket = testbucket
[2023-07-18 14:21:23.413] [org::apache::nifi::minifi::aws::utils::AWSSdkLogger] [debug] [Aws::Endpoint::DefaultEndpointProvider] Endpoint rules engine evaluated the endpoint: https://testbucket.s3.eu-west-2.amazonaws.com
[2023-07-18 14:21:23.413] [org::apache::nifi::minifi::aws::utils::AWSSdkLogger] [trace] [Aws::Endpoint::DefaultEndpointProvider] Endpoint rules evaluated props: {"authSchemes":[{"disableDoubleEncoding":true,"name":"sigv4","signingName":"s3","signingRegion":"eu-west-2"}]}
[2023-07-18 14:21:23.414] [org::apache::nifi::minifi::aws::utils::AWSSdkLogger] [trace] [AWSClient] Found body, but content-length has not been set, attempting to compute content-length
[2023-07-18 14:21:23.431] [org::apache::nifi::minifi::aws::utils::AWSSdkLogger] [debug] [AWSAuthV4Signer] Note: Http payloads are not being signed. signPayloads=0 http scheme=https
[2023-07-18 14:21:23.431] [org::apache::nifi::minifi::aws::utils::AWSSdkLogger] [debug] [AWSAuthV4Signer] Canonical Header String: amz-sdk-invocation-id:C5794CA0-4ED1-4CB3-BE2B-513134FCE44A
amz-sdk-request:attempt=1
content-length:15728640
content-md5:Tlv3ZX2UNZUYIlvmfZhw2Q==
content-type:application/octet-stream
host:testbucket.s3.eu-west-2.amazonaws.com
x-amz-content-sha256:UNSIGNED-PAYLOAD
x-amz-date:20230718T122123Z
x-amz-grant-full-control:
x-amz-grant-read:
x-amz-grant-read-acp:
x-amz-grant-write-acp:
x-amz-storage-class:STANDARD
[2023-07-18 14:21:23.431] [org::apache::nifi::minifi::aws::utils::AWSSdkLogger] [debug] [AWSAuthV4Signer] Signed Headers value:amz-sdk-invocation-id;amz-sdk-request;content-length;content-md5;content-type;host;x-amz-content-sha256;x-amz-date;x-amz-grant-full-control;x-amz-grant-read;x-amz-grant-read-acp;x-amz-grant-write-acp;x-amz-storage-class
[2023-07-18 14:21:23.431] [org::apache::nifi::minifi::aws::utils::AWSSdkLogger] [debug] [AWSAuthV4Signer] Canonical Request String: PUT
/1689682882982900132
amz-sdk-invocation-id:C5794CA0-4ED1-4CB3-BE2B-513134FCE44A
amz-sdk-request:attempt=1
content-length:15728640
content-md5:Tlv3ZX2UNZUYIlvmfZhw2Q==
content-type:application/octet-stream
host:testbucket.s3.eu-west-2.amazonaws.com
x-amz-content-sha256:UNSIGNED-PAYLOAD
x-amz-date:20230718T122123Z
x-amz-grant-full-control:
x-amz-grant-read:
x-amz-grant-read-acp:
x-amz-grant-write-acp:
x-amz-storage-class:STANDARD
amz-sdk-invocation-id;amz-sdk-request;content-length;content-md5;content-type;host;x-amz-content-sha256;x-amz-date;x-amz-grant-full-control;x-amz-grant-read;x-amz-grant-read-acp;x-amz-grant-write-acp;x-amz-storage-class
UNSIGNED-PAYLOAD
[2023-07-18 14:21:23.431] [org::apache::nifi::minifi::aws::utils::AWSSdkLogger] [debug] [AWSAuthV4Signer] Final String to sign: AWS4-HMAC-SHA256
20230718T122123Z
20230718/eu-west-2/s3/aws4_request
fa28ce5c5a03255d0b3387e632af022703b6e985be52b7c1511b3347edd0c500
[2023-07-18 14:21:23.431] [org::apache::nifi::minifi::aws::utils::AWSSdkLogger] [debug] [AWSAuthV4Signer] Final computed signing hash: 871e0fbfcada0cbef9f5deffc4ac7708247aca6caccdf98b2cf45a0a3f1472fc
[2023-07-18 14:21:23.431] [org::apache::nifi::minifi::aws::utils::AWSSdkLogger] [debug] [AWSAuthV4Signer] Signing request with: AWS4-HMAC-SHA256 Credential=AKIAUYLDB5SQVHSVDTJS/20230718/eu-west-2/s3/aws4_request, SignedHeaders=amz-sdk-invocation-id;amz-sdk-request;content-length;content-md5;content-type;host;x-amz-content-sha256;x-amz-date;x-amz-grant-full-control;x-amz-grant-read;x-amz-grant-read-acp;x-amz-grant-write-acp;x-amz-storage-class, Signature=871e0fbfcada0cbef9f5deffc4ac7708247aca6caccdf98b2cf45a0a3f1472fc
[2023-07-18 14:21:23.431] [org::apache::nifi::minifi::aws::utils::AWSSdkLogger] [debug] [AWSClient] Request Successfully signed
[2023-07-18 14:21:23.431] [org::apache::nifi::minifi::aws::utils::AWSSdkLogger] [trace] [CRTHttpClient] Making PUT request to https://testbucket.s3.eu-west-2.amazonaws.com/1689682882982900132
[2023-07-18 14:21:23.431] [org::apache::nifi::minifi::aws::utils::AWSSdkLogger] [trace] [CRTHttpClient] Including headers:
[2023-07-18 14:21:23.431] [org::apache::nifi::minifi::aws::utils::AWSSdkLogger] [trace] [CRTHttpClient] amz-sdk-invocation-id: C5794CA0-4ED1-4CB3-BE2B-513134FCE44A
[2023-07-18 14:21:23.431] [org::apache::nifi::minifi::aws::utils::AWSSdkLogger] [trace] [CRTHttpClient] amz-sdk-request: attempt=1
[2023-07-18 14:21:23.431] [org::apache::nifi::minifi::aws::utils::AWSSdkLogger] [trace] [CRTHttpClient] authorization: AWS4-HMAC-SHA256 Credential=AKIAUYLDB5SQVHSVDTJS/20230718/eu-west-2/s3/aws4_request, SignedHeaders=amz-sdk-invocation-id;amz-sdk-request;content-length;content-md5;content-type;host;x-amz-content-sha256;x-amz-date;x-amz-grant-full-control;x-amz-grant-read;x-amz-grant-read-acp;x-amz-grant-write-acp;x-amz-storage-class, Signature=871e0fbfcada0cbef9f5deffc4ac7708247aca6caccdf98b2cf45a0a3f1472fc
[2023-07-18 14:21:23.431] [org::apache::nifi::minifi::aws::utils::AWSSdkLogger] [trace] [CRTHttpClient] content-length: 15728640
[2023-07-18 14:21:23.431] [org::apache::nifi::minifi::aws::utils::AWSSdkLogger] [trace] [CRTHttpClient] content-md5: Tlv3ZX2UNZUYIlvmfZhw2Q==
[2023-07-18 14:21:23.431] [org::apache::nifi::minifi::aws::utils::AWSSdkLogger] [trace] [CRTHttpClient] content-type: application/octet-stream
[2023-07-18 14:21:23.431] [org::apache::nifi::minifi::aws::utils::AWSSdkLogger] [trace] [CRTHttpClient] host: testbucket.s3.eu-west-2.amazonaws.com
[2023-07-18 14:21:23.431] [org::apache::nifi::minifi::aws::utils::AWSSdkLogger] [trace] [CRTHttpClient] user-agent: aws-sdk-cpp/1.11.118 Linux/5.19.0-46-generic x86_64 GCC/11.3.0
[2023-07-18 14:21:23.431] [org::apache::nifi::minifi::aws::utils::AWSSdkLogger] [trace] [CRTHttpClient] x-amz-content-sha256: UNSIGNED-PAYLOAD
[2023-07-18 14:21:23.431] [org::apache::nifi::minifi::aws::utils::AWSSdkLogger] [trace] [CRTHttpClient] x-amz-date: 20230718T122123Z
[2023-07-18 14:21:23.431] [org::apache::nifi::minifi::aws::utils::AWSSdkLogger] [trace] [CRTHttpClient] x-amz-grant-full-control:
[2023-07-18 14:21:23.431] [org::apache::nifi::minifi::aws::utils::AWSSdkLogger] [trace] [CRTHttpClient] x-amz-grant-read:
[2023-07-18 14:21:23.431] [org::apache::nifi::minifi::aws::utils::AWSSdkLogger] [trace] [CRTHttpClient] x-amz-grant-read-acp:
[2023-07-18 14:21:23.431] [org::apache::nifi::minifi::aws::utils::AWSSdkLogger] [trace] [CRTHttpClient] x-amz-grant-write-acp:
[2023-07-18 14:21:23.431] [org::apache::nifi::minifi::aws::utils::AWSSdkLogger] [trace] [CRTHttpClient] x-amz-storage-class: STANDARD
[2023-07-18 14:21:23.650] [org::apache::nifi::minifi::aws::utils::AWSSdkLogger] [debug] [CRTHttpClient] Obtained connection handle 0x7f982c02a2e0
[2023-07-18 14:21:26.432] [org::apache::nifi::minifi::aws::utils::AWSSdkLogger] [debug] [AWSClient] Request returned error. Attempting to generate appropriate error codes from response
[2023-07-18 14:21:26.432] [org::apache::nifi::minifi::aws::utils::AWSSdkLogger] [error] [AWSXmlClient] HTTP response code: -1
Resolved remote host IP address:
Request ID:
Exception name:
Error message: Request Timeout Has Expired
0 response headers:
[2023-07-18 14:21:26.432] [org::apache::nifi::minifi::aws::utils::AWSSdkLogger] [warning] [AWSClient] If the signature check failed. This could be because of a time skew. Attempting to adjust the signer.
[2023-07-18 14:21:26.432] [org::apache::nifi::minifi::aws::utils::AWSSdkLogger] [debug] [AWSClient] Date header was not found in the response, can't attempt to detect clock skew
[2023-07-18 14:21:26.433] [org::apache::nifi::minifi::aws::s3::S3RequestSender] [error] PutS3Object failed with the following: 'Request Timeout Has Expired'
Hello @lordgamez ,
My apologies for the delay of answer. Thank you very much for providing the information requested. First of all let’s go over your first comment. I have gone over the log and we can see two different behavior here:
For the attempt to upload a 8MB file, the issue is caused by a difference between the server time and the client time :
[2023-07-18 11:12:11.823] [org::apache::nifi::minifi::aws::utils::AWSSdkLogger] [warning] [AWSClient] If the signature check failed. This could be because of a time skew. Attempting to adjust the signer.
[2023-07-18 11:12:11.823] [org::apache::nifi::minifi::aws::utils::AWSSdkLogger] [debug] [AWSClient] Server time is Tue, 18 Jul 2023 09:12:10 GMT, while client time is Tue, 18 Jul 2023 09:12:11 GMT
[2023-07-18 11:12:11.823] [org::apache::nifi::minifi::aws::s3::S3RequestSender] [error] PutS3Object failed with the following: 'The request signature we calculated does not match the signature you provided. Check your key and signing method.'
In this case scenario, the SDK should be adjusting the signer with the skew and attempt the request again. (See. There is a client configuration parameter available enableClockSkewAdjustment which if set to true, adjusts clock skew after each http attempt and default to true. This might also be an issue with your retry strategy.
In the case of the 12MB file, the issue is caused by the Date header not being present in the response:
[2023-07-18 11:14:28.161] [org::apache::nifi::minifi::aws::utils::AWSSdkLogger] [warning] [AWSClient] If the signature check failed. This could be because of a time skew. Attempting to adjust the signer.
[2023-07-18 11:14:28.161] [org::apache::nifi::minifi::aws::utils::AWSSdkLogger] [debug] [AWSClient] Date header was not found in the response, can't attempt to detect clock skew
[2023-07-18 11:14:28.162] [org::apache::nifi::minifi::aws::s3::S3RequestSender] [error] PutS3Object failed with the following: 'Encountered network error when sending http request'
due to Encountered network error when sending http request which causes the request to fail.
Now looking at the behavior using the CRT client, you are experiencing a similar behavior as the second case with a request timeout.
Based on the behavior above, it might be a network issue which would cause latency in the PutObjectRequest and would arise with larger file upload causing the behavior above.
There has been issue submission with similar behavior caused by this see.
Best regards,
Yasmine
Hi @yasminetalby ,
Thanks for investigating the issue. I checked and the enableClockSkewAdjustment was kept on the default true value, but I suppose the reason it did not do the clock skew adjusting because in the time diff check the TIME_DIFF_MAX and TIME_DIFF_MIN values are set to 4 minutes and the difference was only 1 second.
While testing it seems that I have found the root cause of the issue and it looks to be related to this issue. In the application code I had a default ServerSideEncryption::NOT_SET value set for the ServerSideEncryption and it was always set with this default value if no other value was specified by the user. After changing this to only set this value in the request when the configuration value is set to anything but "None" then the S3 upload works as intended on Windows:
inline constexpr std::array<std::pair<std::string_view, Aws::S3::Model::ServerSideEncryption>, 3> SERVER_SIDE_ENCRYPTION_MAP {{
{"None", Aws::S3::Model::ServerSideEncryption::NOT_SET},
{"AES256", Aws::S3::Model::ServerSideEncryption::AES256},
{"aws_kms", Aws::S3::Model::ServerSideEncryption::aws_kms},
}};
...
if (!put_object_params.server_side_encryption.empty() && put_object_params.server_side_encryption != "None") {
request.SetServerSideEncryption(minifi::utils::at(SERVER_SIDE_ENCRYPTION_MAP, put_object_params.server_side_encryption));
}
So it seems that the issue mentioned in #1771 does not only happen with the CRT library but the WinHTTP library as well. When using a build on Linux with CURL for HTTP backend this issues does not appear.
After adding this fix I tested uploads with 5MB, 12MB, and 100MB sized files and all seem to work without a hiccup.
|
Big Winner
Big Winner is a group of unmarked quests in Fallout: New Vegas.
Summary
* The player needs to successfully be banned from gambling on all the casinos in the game.
Each casino has there own marks for comp rewards and the limit at which the player will get banned.
Vikki and Vance Casino
* 625+ chips: 20 more Vikki and Vance Casino chips
* 1,250+ chips: Stealth boy
* 1,875+ chips: Leather armor, reinforced
Atomic Wrangler Casino
* 1,250+ chips: Beer
* 2,500+ chips: Whiskey & dapper gambler hat
* 3,750+ chips: Absinthe, rum & Nuka & dapper gambler suit
Gomorrah
* 2,250+ chips: 2x Brahmin steak
* 4,500+ chips: Mentats, Jet and 2x Wine
* 6,750+ chips: Combat armor, reinforced (not at full repair, valued at 5720)
The Tops
* 2,500+ chips: Vodka
* 5,000+ chips: Brahmin steak and wine
* 7,500+ chips: The Tops High Roller suite key
Ultra-Luxe
* NOTE -- This is the only casino to not offer slot machines, only blackjack and roulette.
* 3,750+ chips: Atomic cocktail
* 7,500+ chips: Brahmin wellington
* 11,250+ chips: Bon Vivant suite key
Sierra Madre Casino
* 2,500+ chips: One wine and one scotch
* 5,000+ chips: Pre-war parkstroller outfit and a pre-war hat
* 7,500+ chips: Complimentary voucher
|
Canon EOS-1N
The EOS-1N is a 35mm single lens reflex (SLR) camera body produced by Canon. It was announced by Canon in 1994, and was the professional model in the range, superseding the original Canon EOS-1. The camera was itself superseded by the EOS-1V in 2000.
The original EOS-1 had been launched in 1989, two years after the company had introduced their new EOS autofocus system. It was the company's first professional-level EOS camera and was aimed at the same photographers who had used Canon's highly regarded, manual focus professional FD mount SLRs, such as the Canon New F-1 and the Canon T90. On a physical level the EOS-1 resembled the T90, which had been designed for Canon by Luigi Colani. The EOS-1N was a revision of the EOS-1, with five autofocus points spread across the frame rather than a single centrally-mounted autofocus point, plus more effective weather sealing, a wider exposure range, and numerous other improvements. In common with the EOS-1, the 1N used Canon's A-TTL automatic flash system, and does not support the more modern E-TTL.
Features
At the time of its creation, The Canon EOS-1N was placed at the top of Canon's EOS camera line. The camera featured polycarbonate external construction with weather-resistant seals around buttons, dials and its Canon EF lens mount.
The fixed eye-level pentaprism viewfinder has 100-percent vertical and horizontal coverage, has dioptric viewfinder adjustment from –3 to +1 diopter and has as a viewfinder eyepiece blind to block stray light when on a tripod.
For automatic focusing, the camera used a 5-point BASIS auto focus system with the sensors arranged horizontally across the middle of the viewing area. The center point is a cross-type, which detects horizontal and vertical lines, while the outer four detect vertical lines only.
Metering modes include a 16-zone evaluative, center-weighted average, partial, selectable spot, and fine central spot metering mode. Film speeds can be set from ISO 6-6400 either manually or automatically by DX codes on the film canisters.
The camera allows variable Program autoexposure, as well as aperture-priority and shutter-priority automatic exposure and manual exposure. Another option is Depth-of-field AE (DEP), an automatic mode that selects the focusing distance and aperture f-number to place the depth of field between two user-specified near and far points.
Shutter speeds range from 30 seconds to 1/8000 of a second in all exposure modes. A non-timed bulb speed is available. Flash X-sync is available up to a shutter speed of 1/250 of a second.
There are 14 custom functions to change the way the camera operates, which set options like exposure steps and mirror lock-up.
The camera has user-interchangeable focusing screens, interchangeable with those out of other EOS-1-series cameras, and a now-discontinued interchangeable Canon Command Back E1.
Power comes from one 2CR5 battery, an optional BP-E1 Battery Pack housing four AA alkaline or lithium batteries or the PB-E1 Power Booster drive housing eight AA batteries and allowing for 6 frames per second to be photographed, depending on the type of battery and the shutter speed selected.
The camera weighs in at 855 grams, or 1 lb and 14.15 oz.
Background
There were several versions of the EOS-1N available. The base model EOS-1N consisted of the standard camera body with significant upgrades over the EOS-1, launched in 1989. The EOS-1N DP comprised the standard body and the BP-E1 pack (see below) and the EOS-1N HS comprised the standard body plus booster (see below).
One feature the EOS-1N (and previous/subsequent '1' models) lacks, which lower models in the range have, is built-in flash, intentionally omitted to provide an overall very rigid camera body able to withstand severe treatment by professionals. Weather sealing was incorporated after feedback from working professionals. Other notable omissions are the eye-controlled focus feature of the EOS-5 and the bar code reader of the EOS-10, neither of which are professional-level cameras.
Another feature of the EOS-1N, and other professional models in the range, is the provision for a precise viewfinder indication of exposure in manual mode. This had previously been provided in fully manual cameras such as the F-1, but older Canon cameras with automatic exposure modes merely provided a recommended exposure reading in manual mode, leaving the user to accept the offered settings or not. The EOS-1N provides a viewfinder readout similar to the old F-1's needle display, but in electronic LCD form showing steps in 0.3, 0.5 or 1 stops. Like the EOS-5, the internal displays of the EOS-1N self-adjust in brightness in response to the brightness level of the subject.
The optional Power Booster PB-E1 or Battery Pack BP-E1 attach to the base of the camera. The PB-E1 holds 8 AA batteries or an optional Ni-Cd pack, and boosts the standard frame rate from 3 frames per second to 6 (5 when using AI Servo AF). The PB-E1 has a shutter release and AE Lock button for use when shooting in the vertical format. There is also a Power Booster PB-E2 which adds a main control dial, focusing point selector button, and FE Lock/multi-spot metering button. The PB-E2 was designed for the later EOS-3 camera, and only provides the functionality of a PB-E1 when attached to an EOS-1 or 1N.
The BP-E1 is a lighter and simpler accessory. This holds a 2CR5 lithium battery and 4 AA cells (in the removable Battery Magazine BM-1). The user can select between the two power sources with a switch. It provides a grip for vertical shots but no additional controls. The major appeal of the Battery Pack BP-E1 is that is lighter and less expensive than the PB-E1, while still providing the advantage of using inexpensive AA batteries.
In addition to the standard EOS-1N there was another, specialized model in the range — the EOS-1N RS, introduced in 1995, with a permanently attached power drive booster. This camera has a fixed pellicle mirror so there is no viewfinder black-out at the moment of exposure. The fixed mirror allows high-speed continuous shooting at a top speed of 10 frames per second, with a shutter release lag as low as 6 ms. There is a cost to this however: slightly less light reaches the film, as some is always being directed up to the viewfinder and optical quality loss. By the time of the release of the next generation EOS-1V, considerable technical improvements to the standard camera design meant that Canon no longer offered RS model variants.
The EOS-1N was discontinued in 2001 with the arrival of the EOS-1V.
Digital
During the late 1990s, Canon and Kodak collaborated on a range of professional digital SLRs which combined Canon EOS-1N bodies with Kodak digital sensors and electronics. They were Canon's first ventures into the digital SLR marketplace and divided into two distinct generations.
The first generation was the Kodak EOS DCS series of 1995, which encompassed the 6 mp EOS DCS 1, the 1.3 mp DCS 3, and the 1.5 mp DCS 5. The EOS-1N camera bodies were almost unmodified from stock configuration, and were mounted on a removable Kodak digital back.
The relationship continued with the Kodak DCS 500 series, which fully integrated the EOS-1N body with Kodak's imaging components. The range consisted of the 2 mp DCS 520 and the 6 mp DCS 560. The two cameras were also sold by Canon, as the Canon EOS D2000 and Canon EOS D6000 respectively. Canon's subsequent professional digital SLRs were produced independently of Kodak, and were initially based on the EOS-1V, before moving to custom-designed digital bodies.
|
Long-Term Consumption of Food-Derived Chlorogenic Acid Protects Mice against Acetaminophen-Induced Hepatotoxicity via Promoting PINK1-Dependent Mitophagy and Inhibiting Apoptosis
Hepatotoxicity brought on by acetaminophen (APAP) is significantly impacted by mitochondrial dysfunction. Mitophagy, particularly PINK1-mediated mitophagy, maintains the stability of cell function by eliminating damaged mitochondria. One of the most prevalent dietary polyphenols, chlorogenic acid (CGA), has been shown to have hepatoprotective properties. It is yet unknown, nevertheless, whether its defense against hepatocyte apoptosis involves triggering PINK1-mediated mitophagy. In vitro and in vivo models of APAP-induced hepatotoxicity were established to observe CGA’s effect and mechanism in preventing hepatotoxicity in the present study. Serum aminotransferase levels, mouse liver histology, and the survival rate of HepG2 cells and mice were also assessed. The outcomes showed that CGA could reduce the activities of serum enzymes such as alanine transaminase (ALT), aspartate transaminase (AST), and lactate dehydrogenase (LDH), and alleviate liver injury in mice. It could also significantly increase the cell viability of HepG2 cells and the 24-h survival rate of mice. TUNEL labeling and Western blotting were used to identify the hepatocyte apoptosis level. According to data, CGA could significantly reduce liver cell apoptosis in vivo. Additionally, Tom20 and LC3II colocalization in mitochondria may be facilitated by CGA. CGA considerably increased the levels of genes and proteins associated with mitophagy (PINK1, Parkin, LC3II/LC3I), while considerably decreasing the levels of p62 and Tom20, suggesting that it might activate PINK1/Parkin-mediated mitophagy in APAP-induced liver damage. Additionally, the protection of CGA was reduced when PINK1 was knocked down by siPINK1 in HepG2 cells, and it did not upregulate mitophagy-related proteins (PINK1, Parkin, LC3II/LC3I). In conclusion, our findings revealed that long-term consumption of food-derived CGA could prevent APAP hepatotoxicity via increasing PINK1-dependent mitophagy and inhibiting hepatocyte apoptosis.
Introduction
Acetaminophen (APAP) overdoses are one of the most frequent forms of drug-induced liver injury (DILI), which poses a serious threat to public health. Since 1955, APAP has been
Introduction
Acetaminophen (APAP) overdoses are one of the most frequent forms of drug-induced liver injury (DILI), which poses a serious threat to public health. Since 1955, APAP has been a widely used antipyretic and analgesic medication. As the liver is one of the most sensitive organs to APAP, even if it is normally safe at a therapeutic dose (4 g per 24 h), APAP could result in serious liver damage through hepatotoxicity with a single excess dose reaching 15 to 25 g [1,2]. In the United States, APAP overdoses account for 50% of all occurrences of acute liver failure, and they are the second most common reason for liver transplants in people worldwide [3][4][5]. The hallmark of APAP hepatotoxicity is the production of mitochondrial superoxide and peroxynitrite. It is widely known that APAP hepatotoxicity results from the overproduction of the poisonous metabolite N-acetyl-pbenzoquinone imine (NAPQI), even though Cytochrome P450 only converts a very small amount of APAP (5-9%) into NAPQI at therapeutic doses [6]. Apoptosis, glutathione (GSH) depletion, oxidative stress, sterile inflammation, mitochondrial dysfunction, and excessive NAPQI buildup are all caused by the metabolism of overdose APAP by P450, which in turn causes hepatotoxicity and hepatic necrosis [7][8][9][10] (Figure 1).
Figure 1.
Schematic diagram of APAP-induced hepatotoxicity. NOPQI is metabolized in combination with cysteine and mercaptoacetic acid when GSH is abundant. With the depletion of GSH, the accumulated NAPQI binds to some large proteins to induce mitochondrial damage, oxidative stress, an inflammatory response, and apoptosis.
The major target of APAP hepatotoxicity is the mitochondria, which are highly dynamic organelles that regulate cell redox homeostasis, innate immunity, and apoptosis [11,12]. These organelles also serve as the origin of inflammatory signals and oxidative stress responses in liver cells [13]. The primary cause of liver apoptosis and death in APAP hepatotoxicity is mitochondrial dysfunction [14]. Emerging data suggest that mitophagy is essential to the physiology and pathology of the liver [15]. Mitophagy can maintain its function, metabolic stability, and reactive oxygen species (ROS) equilibrium while selectively destroying mitochondria damaged by ROS [16]. Typically, autophagosome production, mitochondrial fission, and fusion with lysosomes occur during mitophagy [17]. The PINK1/Parkin pathway, which is activated by the phosphatase and tenson homolog (PTEN) gene, controls these functions. In brief, in answer to various stimuli, PINK1 locates damaged mitochondria from the inner membrane on the outside mitochondrial membrane, and then, by recruiting Parkin, removes the damaged mitochondria [18]. Importantly, Pink1/Parkin suppression increases APAP hepatotoxicity by impairing hepatic mitophagy, suggesting that Pink1/Parkin-mediated mitophagy may be essential for reducing APAP toxicity [19,20]. Therefore, it is crucial to precisely regulate the Pink1/Parkin pathway to prevent APAP hepatotoxicity. Intriguingly, a recent study discovered that knockdown of PINK1 dramatically decreased mitophagy in a cell model of cadmium- Figure 1. Schematic diagram of APAP-induced hepatotoxicity. NOPQI is metabolized in combination with cysteine and mercaptoacetic acid when GSH is abundant. With the depletion of GSH, the accumulated NAPQI binds to some large proteins to induce mitochondrial damage, oxidative stress, an inflammatory response, and apoptosis.
The major target of APAP hepatotoxicity is the mitochondria, which are highly dynamic organelles that regulate cell redox homeostasis, innate immunity, and apoptosis [11,12]. These organelles also serve as the origin of inflammatory signals and oxidative stress responses in liver cells [13]. The primary cause of liver apoptosis and death in APAP hepatotoxicity is mitochondrial dysfunction [14]. Emerging data suggest that mitophagy is essential to the physiology and pathology of the liver [15]. Mitophagy can maintain its function, metabolic stability, and reactive oxygen species (ROS) equilibrium while selectively destroying mitochondria damaged by ROS [16]. Typically, autophagosome production, mitochondrial fission, and fusion with lysosomes occur during mitophagy [17]. The PINK1/Parkin pathway, which is activated by the phosphatase and tenson homolog (PTEN) gene, controls these functions. In brief, in answer to various stimuli, PINK1 locates damaged mitochondria from the inner membrane on the outside mitochondrial membrane, and then, by recruiting Parkin, removes the damaged mitochondria [18]. Importantly, Pink1/Parkin suppression increases APAP hepatotoxicity by impairing hepatic mitophagy, suggesting that Pink1/Parkin-mediated mitophagy may be essential for reducing APAP toxicity [19,20]. Therefore, it is crucial to precisely regulate the Pink1/Parkin pathway to prevent APAP hepatotoxicity. Intriguingly, a recent study discovered that knockdown of PINK1 dramatically decreased mitophagy in a cell model of cadmiuminduced mitochondrial dysfunction and exacerbated liver parenchymal cell damage [21]. In hypoxia/reoxygenation-induced L02 cells, cell apoptosis was increased after PINK1 was knocked down by siRNA, suggesting that PINK1-mediated mitophagy plays a role in controlling apoptosis [22]. However, the effectiveness of mitophagy-mediated apoptosis in reducing APAP hepatotoxicity is still mainly unknown.
N-acetylcysteine (NAC) is currently thought to be the only antidote for APAP due to its potent antioxidant effects by boosting the content of endogenous GSH [23,24]. Due to NAC's drawbacks, such as a narrow therapeutic window and limited effectiveness, it is vital and necessary to develop early prevention and intervention measures that can prevent APAP hepatotoxicity, particularly natural bioactive substances [25,26]. Ammonium glycyrrhizinate (AG), also known as glycyrrhizin or glycyrrhetinic acid, is an inhibitor of high mobility group box 1 (HMGB1) protein with antioxidant activity and has been reported to protect against APAP-induced liver toxicity through tumor necrosis factor α (TNF-α)mediated apoptosis and the fatty acid metabolic pathway [27][28][29][30][31]. Thus, it was used as a positive drug in this study. Several studies have shown that phenolic phytochemicals in dietary foods, spices, and herbs with antioxidant activity can prevent the liver toxicity caused by APAP [32,33]. Chlorogenic acid (CGA) is a potent antioxidant with a purportedly high safety profile that is a naturally occurring dietary polyphenolic component produced from coffee, apple, blueberries, tea, and several natural remedies such as Lonicerae flos. According to reports, CGA levels in coffee, sunflower seeds, and Lonicerae flos range from 2.0% to 8.00%, 1.50 to 3.00%, and 1.00 to 5.90%, respectively [34]. The protective effect of CGA on APAP hepatotoxicity has been demonstrated by increasing data. This impact incorporates many mechanisms, including anti-oxidation, anti-inflammatory, and antiapoptosis [9,[35][36][37]. CGA's unique strategies against APAP hepatotoxicity include blocking CYP2E1 and CYP1A2 enzymatic characteristics, attenuating liver mitochondrial injury and lowering mitochondrial HSP60 production, activating the Nrf2 anti-oxidative signaling system, and inhibiting the MAPK, TLR3/4, and NF kappa B signaling pathways [9,[38][39][40][41][42][43][44]. Cellular homeostasis and the response of the mitochondria to stress are significantly influenced by mitophagy. The fundamental mechanisms of oxidative stress, inflammation, and apoptosis are mitophagy abnormalities. However, it is unclear whether long-term consumption of food-derived CGA can trigger mitophagy dependent on PINK1, which suppresses liver cell death to reduce APAP hepatotoxicity. Determining the underlying mechanism and evaluating the hepatoprotective impact of CGA in overdose APAP-induced mice are the goals of the current investigation.
Animals
One hundred male Kunming mice (weighing 20 ± 2 g, 4-6 weeks age) were obtained from Byrness Weil Biotech Co., Ltd. (No.: 0003181, Chengdu, China). After all mice were acclimated for 3 days in a constant temperature and humidity room (24 • C ± 1 • C, Toxics 2022, 10, 665 4 of 15 50% ± 10% humidity) with a standard diet, water, and a 12-h light/dark cycle (lights on at 8:00 am and lights off at 8:00 pm), animals were randomly separated into five groups (n = 20): the control group (Ctrl), APAP (300 mg/kg), the APAP (300 mg/kg) + AG group (200 mg/kg), and the APAP (300 mg/kg) + CGA group (20 mg/kg or 40 mg/kg). Mice in the intervention group were respectively pre-administered (i.g.) with CGA (20 mg/kg or 40 mg/kg) or AG (200 mg/kg) for 14 consecutive days. Simultaneously, the Ctrl and APAP groups were congruously orally administrated (i.g.) with the same volume of 0.9% saline. On day 15, mice were orally administered (i.g.) a single dose of APAP (300 mg/kg) to induce acute hepatotoxicity injury, except the Ctrl group, which was orally administered (i.g.) 0.9% saline. The dose for APAP-induced liver injury was sourced from the reported literature [45,46]. After APAP (300 mg/kg) treatment, the death period of mice was recorded within 24 h. All mice were anesthetized with pentobarbital (50 mg/kg, i.p., dissolved in sterilized normal saline) on day 16, blood was collected by cardiac puncture, and serum was obtained after centrifugation at 3500 rpm for 10 min at room temperature. Then, all animals were euthanized and liver tissues were collected. A schematic diagram of the treatment schedule is shown in Figure 2
Animals
One hundred male Kunming mice (weighing 20 ± 2 g, 4-6 weeks age) were obtained from Byrness Weil Biotech Co., Ltd. (No.: 0003181, Chengdu, China). After all mice were acclimated for 3 days in a constant temperature and humidity room (24 °C ± 1 °C, 50% ± 10% humidity) with a standard diet, water, and a 12-h light/dark cycle (lights on at 8:00 am and lights off at 8:00 pm), animals were randomly separated into five groups (n = 20): the control group (Ctrl), APAP (300 mg/kg), the APAP (300 mg/kg) + AG group (200 mg/kg), and the APAP (300 mg/kg) + CGA group (20 mg/kg or 40 mg/kg). Mice in the intervention group were respectively pre-administered (i.g.) with CGA (20 mg/kg or 40 mg/kg) or AG (200 mg/kg) for 14 consecutive days. Simultaneously, the Ctrl and APAP groups were congruously orally administrated (i.g.) with the same volume of 0.9% saline. On day 15, mice were orally administered (i.g.) a single dose of APAP (300 mg/kg) to induce acute hepatotoxicity injury, except the Ctrl group, which was orally administered (i.g.) 0.9% saline. The dose for APAP-induced liver injury was sourced from the reported literature [45,46]. After APAP (300 mg/kg) treatment, the death period of mice was recorded within 24 h. All mice were anesthetized with pentobarbital (50 mg/kg, i.p., dissolved in sterilized normal saline) on day 16, blood was collected by cardiac puncture, and serum was obtained after centrifugation at 3500 rpm for 10 min at room temperature. Then, all animals were euthanized and liver tissues were collected. A schematic diagram of the treatment schedule is shown in Figure 2
Cell Culture
HepG2 cell lines were purchased from the Cell Bank of the Chinese Academy of Science (Shanghai, China). HepG2 cells were cultured in DMEM with 10% fetal bovine serum and 1% penicillin/streptomycin (Gibco) at 37 °C with 5% CO2. The cells were divided into Ctrl, APAP, APAP + CGA, APAP + CGA + siNC, APAP + CGA + siPINK1. Then, 1 × 10 4 cells cultured in 96-well plates were pre-incubated with CGA at different concentrations for 15 min after adherence, and then incubated with APAP for an additional 24 h. Cell viability was measured by MTT assay according to the manufacturer's instructions.
Biochemical Analysis for Serum
Since alanine aminotransferase (ALT), aspartate aminotransferase (AST), and alkaline phosphatase (ALP) are the classic diagnostic markers of liver injury [47], the serum enzymatic activities of ALT, AST, and LDH were measured with a HITACHI 7180 automatic biochemistry analyzer (Hitachi, Japan).
Cell Culture
HepG2 cell lines were purchased from the Cell Bank of the Chinese Academy of Science (Shanghai, China). HepG2 cells were cultured in DMEM with 10% fetal bovine serum and 1% penicillin/streptomycin (Gibco) at 37 • C with 5% CO 2 . The cells were divided into Ctrl, APAP, APAP + CGA, APAP + CGA + siNC, APAP + CGA + siPINK1. Then, 1 × 10 4 cells cultured in 96-well plates were pre-incubated with CGA at different concentrations for 15 min after adherence, and then incubated with APAP for an additional 24 h. Cell viability was measured by MTT assay according to the manufacturer's instructions.
Biochemical Analysis for Serum
Since alanine aminotransferase (ALT), aspartate aminotransferase (AST), and alkaline phosphatase (ALP) are the classic diagnostic markers of liver injury [47], the serum enzymatic activities of ALT, AST, and LDH were measured with a HITACHI 7180 automatic biochemistry analyzer (Hitachi, Japan).
HE Staining and TUNEL Assay
Fresh liver tissues were immediately fixed in 4% paraformaldehyde for 24 h, embedded in paraffin, and then cut into 4-µm-thick sections. The tissues were stained with hematoxylin and eosin (HE) for histological examination under light microscopy. The histological scores (including inflammation and necrosis) indicating the degree of liver injury were determined according to Suzike's standard in a blinded manner [48]. The scoring criteria are as follows: the score scale of inflammation ranged from 0 to 4, indicating none, slight, mild, moderate, and severe, respectively. The score scale of necrosis ranged from 0 to 4, indicating no necrosis area, a single cell, <30%, 31-60%, >60%. Simultaneously, terminal deoxynucleotidyl transferase-mediated dUTP-biotin nick end labeling (TUNEL) was used to measure hepatic apoptosis according to the instructions of the manufacturer of the TUNEL apoptotic detection kit. Images were captured by fluorescence microscopy (Leica Microsystems, Wetzlar, Germany), and we counted the positive cells.
PINK1 siRNA Transfection
PINK1-siRNA (Hanheng Biotechnology, Shanghai, China) was used to knock down PINK1 in HepG2 cells, according to the manufacturer's instructions. In addition, HepG2 cells transfected with non-silencing scrambled siRNA (siNC, Hanheng Biotechnology. Shanghai, China) were used as the Ctrl. The respective siRNA senses and antisense sequences for PINK1 and Ctrl siRNA were as follows: siPINK1, 5 -CGCUGUUCCUCGUUAU GAATT-3 and 5 -UUCAUAACGAGGAACAGCGTT-3 , and siNC, 5 -UUCUCCGAACGU GUCACGUdTdT-3 and 5 -ACGUGACACGUUCGGAGAA dTdT-3 . After the cells were successfully transfected, the cells were treated according to the method shown in Section 2.7, Section 2.8 and then subjected to RT-qPCR and Western blot analysis.
Immunofluorescence Analysis
The liver tissue was cut into 4-µm-thick sections, followed by deparaffinization with xylene and gradient ethanol, antigen retrieval with trisodium citrate dihydrate for 30 min, and blocking with 1% BSA at room temperature for 30 min. The sections were incubated with primary anti-Tom20 (1:100) and anti-LCII (1:300) at 4 • C overnight, and then with secondary antibodies (1:500) in the dark for 1 h. Hoechst 33258 was used to counterstain the nucleus. Lastly, the sections were mounted with anti-fluorescence quenching sealer and observed via confocal microscopy (Olympus, Japan).
Statistical Analysis
Statistical analysis was performed with one-way analysis of variance (ANOVA), followed by Bonferroni's post-tests. The values were expressed as the mean ± standard error of the mean (SEM). The survival rate was analyzed via the log-rank test. Values of p < 0.05 were considered to be statistically significant. The R language was applied for the statistical analysis and graph work.
CGA Alleviated Hepatotoxicity in APAP-Induced Mice
To evaluate the preventive effect of CGA in APAP-induced liver injury, the 24 h survival rates of mice, the activities of serum enzymes (AST, ALT, LDH), and liver injury were assessed. As shown in Figure 3A, APAP administration resulted in an obvious decline in survival rates to 65% within 6 h, which remained at this level for up to 24 h. Pretreatment with CGA (40 mg/kg) or AG increased survival rates compared with APAP alone. The activities of serum ALT, AST, and LDH in APAP hepatotoxicity mice were significantly increased compared with the Ctrl group, while markedly decreased in the AG and CGA pretreatment (40 mg/kg) group (p < 0.05, Figure 3B-D). As shown in Figure 3E, APAP administration significantly induced severe hepatocellular injury compared with the Ctrl group, such as the loss of hepatocyte architecture, vacuolization of hepatocytes, massive necrosis, and mononuclear cell infiltration in the portal area. Conversely, pretreatment with CGA or AG significantly ameliorated the hepatocellular injury around the portal area. The results of the necrosis score and inflammation score showed high conformity with HE staining (p < 0.05, Figure 3F,G). These results suggested that pretreatment with CGA could prophylaxis APAP hepatotoxicity in mice.
CGA Suppressed Liver Cell Apoptosis in APAP Hepatotoxicity Mice
Since hepatocyte apoptosis is the key feature of APAP hepatotoxicity, TUNEL staining and Western blotting were used to evaluate the CGA against apoptosis. As shown in Figure 4A, B, there were few apoptotic cells in the normal liver tissue. However, significantly increased numbers of apoptotic cells could be observed in the APAP group, which
CGA Suppressed Liver Cell Apoptosis in APAP Hepatotoxicity Mice
Since hepatocyte apoptosis is the key feature of APAP hepatotoxicity, TUNEL staining and Western blotting were used to evaluate the CGA against apoptosis. As shown in Figure 4A,B, there were few apoptotic cells in the normal liver tissue. However, significantly increased numbers of apoptotic cells could be observed in the APAP group, which was significantly reduced by pretreatment with CGA or AG (p < 0.05). To further demonstrate the effect of CGA on APAP-induced apoptosis, the expression of apoptosis-associated proteins (Bax and Bcl-2) was measured by Western blotting. Our data showed that APAP mice presented remarkably elevated expression of Bax and decreased expression of Bcl-2 (p < 0.01, Figure 4C-E) and a reduced Bcl-2/Bax rate (p < 0.001, Figure 4F) compared to the Ctrl group, which were significantly reversed after treatment with CGA (40 mg/kg) or AG (p < 0.05, p < 0.01, or p < 0.001, Figure 4C-F). These results indicated that CGA attenuated APAP-induced apoptosis of hepatocytes by regulating Bcl-2 family protein levels in mice.
CGA Triggered PINK1-Dependent Mitophagy in APAP Hepatotoxicity Mice
PINK1-dependent mitophagy is closely related to apoptosis. In order to clarify whether CGA, acting against liver apoptosis, is involved in activating mitophagy through the PINK1/Parkin pathway, mitophagy was evaluated by immunofluorescence colocalization, RT-qPCR, and Western blotting. Since the expression decrease of Tom20 (a specific mitochondria marker) is often considered to be due to the reduction in mitochondria damage and the activation of autophagy [49], the colocalization of Tom20 and LC3II (autophagy marker) was firstly measured by immunofluorescence analysis. The results showed that pretreatment with CGA significantly promoted the colocalization of Tom20 and LC3II in the membranes of the mitochondria to exert a mitophagy-enhancing effect compared with APAP mice ( Figure 5A, B, p < 0.05). Moreover, the expression of LC3II mRNA and protein was dramatically increased, while p62 showed the opposite compared with APAP mice; the ratio levels of LC3II/I were significantly decreased in APAP mice, while they were remarkably increased in CGA mice (p < 0.05 or p < 0.01, Figure 5C-E). These results indicated that CGA promoted autophagy flux in APAP-induced liver injury mice. Furthermore, PINK1-dependent mitophagy was recently recognized as a novel target for the treatment of alcoholic liver disease and APAP hepatotoxicity [20,50]. The gene and protein expression of PINK1 and Parkin were significantly downregulated in the APAP group compared with the Ctrl group, while being markedly upregulated in the group that received pretreatment with CGA (p < 0.05 or p < 0.01, Figure 5C-E). These results confirmed that the PINK1-depended mitophagy deficit is the underlying mechanism of over-
CGA Triggered PINK1-Dependent Mitophagy in APAP Hepatotoxicity Mice
PINK1-dependent mitophagy is closely related to apoptosis. In order to clarify whether CGA, acting against liver apoptosis, is involved in activating mitophagy through the PINK1/Parkin pathway, mitophagy was evaluated by immunofluorescence colocalization, RT-qPCR, and Western blotting. Since the expression decrease of Tom20 (a specific mitochondria marker) is often considered to be due to the reduction in mitochondria damage and the activation of autophagy [49], the colocalization of Tom20 and LC3II (autophagy marker) was firstly measured by immunofluorescence analysis. The results showed that pretreatment with CGA significantly promoted the colocalization of Tom20 and LC3II in the membranes of the mitochondria to exert a mitophagy-enhancing effect compared with APAP mice (Figure 5A,B, p < 0.05). Moreover, the expression of LC3II mRNA and protein was dramatically increased, while p62 showed the opposite compared with APAP mice; the ratio levels of LC3II/I were significantly decreased in APAP mice, while they were remarkably increased in CGA mice (p < 0.05 or p < 0.01, Figure 5C-E). These results indicated that CGA promoted autophagy flux in APAP-induced liver injury mice. Furthermore, PINK1-dependent mitophagy was recently recognized as a novel target for the treatment of alcoholic liver disease and APAP hepatotoxicity [20,50]. The gene and protein expression of PINK1 and Parkin were significantly downregulated in the APAP group compared with the Ctrl group, while being markedly upregulated in the group that received pretreatment with CGA (p < 0.05 or p < 0.01, Figure 5C-E). These results confirmed that the PINK1-depended mitophagy deficit is the underlying mechanism of overdose APAP hepatotoxicity, and CGA protects against APAP hepatotoxicity by activating PINK1-depended mitophagy.
siPINK1 Reversed the Protective Effect of CGA
To further confirm that the protection against APAP hepatotoxicity is dependent on the promotion of PINK1-dependent mitophagy, siPINK1 HepG2 cells (p < 0.001, Figure 6B, C) were established. Our data showed that CGA had no significant effect on the
siPINK1 Reversed the Protective Effect of CGA
To further confirm that the protection against APAP hepatotoxicity is dependent on the promotion of PINK1-dependent mitophagy, siPINK1 HepG2 cells (p < 0.001, Figure 6B,C) were established. Our data showed that CGA had no significant effect on the viability of HepG2 cells at 0-100 µM ( Figure 6A), while cell viability was significantly increased by CGA (25-50 µM) in APAP (10 mM)-induced HepG2 cells (p < 0.05 or p < 0.01, Figure 6D), suggesting that CGA could protect against APAP cytotoxicity in vitro. Moreover, the cytoprotective effect of CGA was reversed when PINK1 was knocked down by siRNA (p < 0.01, Figure 6D). As expected, the expression of mitophagy-related proteins (PINK1, Parkin, LC3II/I ratio) was also reversed, with the exception of p62 (p < 0.05 or p < 0.01, Figure 6E, F). These results, gained from siPINK1 HepG2 cells, further demonstrated that CGA protected against APAP hepatotoxicity in a PINK1-dependent manner, triggering mitophagy. Figure 6D), suggesting that CGA could protect against APAP cytotoxicity in vitro. Moreover, the cytoprotective effect of CGA was reversed when PINK1 was knocked down by siRNA (p < 0.01, Figure 6D). As expected, the expression of mitophagy-related proteins (PINK1, Parkin, LC3II/I ratio) was also reversed, with the exception of p62 (p < 0.05 or p < 0.01, Figure 6E, F). These results, gained from siPINK1 HepG2 cells, further demonstrated that CGA protected against APAP hepatotoxicity in a PINK1-dependent manner, triggering mitophagy.
Discussion
The current investigation proved that insufficient PINK1-dependent mitophagy was one of the primary mechanisms of APAP-induced hepatotoxicity and demonstrated the preventive efficacy of CGA in APAP-induced liver injury by activating PINK1-dependent mitophagy and inhibiting apoptosis (As shown in Figure 7). LC3II/LC3I, and p62 in HepG2 in different groups by Bio-Rad Quantity One (n = 3). # p < 0.05, ## p < 0.01 vs. Ctrl group; * p < 0.05, ** p < 0.01 vs. APAP group.
Discussion
The current investigation proved that insufficient PINK1-dependent mitophagy was one of the primary mechanisms of APAP-induced hepatotoxicity and demonstrated the preventive efficacy of CGA in APAP-induced liver injury by activating PINK1-dependent mitophagy and inhibiting apoptosis (As shown in Figure 7). As a non-opioid analgesic, APAP frequently causes toxicity, most notably hepatotoxicity. Due to its accessibility and false perceptions of its safety, hepatotoxicity induced by APAP overdose is a highly regular occurrence throughout the world. The only antidote to APAP overdose currently approved by the FDA is NAC. However, it has a limited therapeutic window and is only effective when taken within 8 h of consuming APAP [46,51]. This deficiency emphasizes the critical need for novel, late-acting medicines. In this context, natural active ingredients have already received a lot of attention in recent decades. Some natural components, such as ginsenoside Rk3, rosmarinic acid, isorhamnetin, and Emodin, have been found to have hepatoprotective potential in preventing APAP-induced liver injury [52][53][54][55]. AG has been shown to prevent liver injury via binding to and inhibiting HMGB1, decreasing TNF-mediated apoptosis, and inhibiting the fatty acid metabolic pathway [27][28][29][30][31]. In patients with drug-induced liver injury, compound glycyrrhizin's injection, an AG preparation, has a positive hepatoprotective effect by lowering the levels of ALT and AST [56,57]. AG (200 mg/kg) was chosen as a positive medication in this study based on the available literature [31]. Our data showed that AG preadministration significantly reduced APAP-induced hepatotoxicity by decreasing the activities of serum ALT, AST, and LDH, as well as hepatocyte apoptosis.
Plant polyphenols from food (such as CGA) have been shown to protect against and even prevent liver damage thanks to their benefits as natural antioxidants and their low toxicity. It has been demonstrated that the phenylpropanoid molecule CGA, which has significant antioxidant capacity, can prevent liver damage brought about by a variety of As a non-opioid analgesic, APAP frequently causes toxicity, most notably hepatotoxicity. Due to its accessibility and false perceptions of its safety, hepatotoxicity induced by APAP overdose is a highly regular occurrence throughout the world. The only antidote to APAP overdose currently approved by the FDA is NAC. However, it has a limited therapeutic window and is only effective when taken within 8 h of consuming APAP [46,51]. This deficiency emphasizes the critical need for novel, late-acting medicines. In this context, natural active ingredients have already received a lot of attention in recent decades. Some natural components, such as ginsenoside Rk3, rosmarinic acid, isorhamnetin, and Emodin, have been found to have hepatoprotective potential in preventing APAP-induced liver injury [52][53][54][55]. AG has been shown to prevent liver injury via binding to and inhibiting HMGB1, decreasing TNF-mediated apoptosis, and inhibiting the fatty acid metabolic pathway [27][28][29][30][31]. In patients with drug-induced liver injury, compound glycyrrhizin's injection, an AG preparation, has a positive hepatoprotective effect by lowering the levels of ALT and AST [56,57]. AG (200 mg/kg) was chosen as a positive medication in this study based on the available literature [31]. Our data showed that AG preadministration significantly reduced APAP-induced hepatotoxicity by decreasing the activities of serum ALT, AST, and LDH, as well as hepatocyte apoptosis.
Plant polyphenols from food (such as CGA) have been shown to protect against and even prevent liver damage thanks to their benefits as natural antioxidants and their low toxicity. It has been demonstrated that the phenylpropanoid molecule CGA, which has significant antioxidant capacity, can prevent liver damage brought about by a variety of medications, including trimethylamine-N-oxide production, thioacetamide, carbon tetrachloride, methotrexate, and APAP [38,[58][59][60]. In this experiment, the dose of CGA in mice was 20-40 mg/kg, which equates to approximately 133-266 mg/day in the human body. Our data showed that CGA (20 to 40 mg/kg) could protect mice against acetaminophen-induced hepatotoxicity. Since CGA is a dietary polyphenolic component that is present in many foods, such as coffee (70-350 mg/cup), apples (0.615-1.181 mg/g), and blueberries (0.85 mg/g) [61][62][63], it is relatively easy to obtain sufficient amounts of CGA from food daily. According to our data, CGA pretreatment dramatically increased survival rates, and liver function was shown to be enhanced by preventing the increase in serum ALT, AST, and LDH that an overdose of APAP causes. In addition, APAP-induced HepG2 cells' cell viability was improved by CGA. Hepatocyte apoptosis and necrosis coexistence have been well-documented as being crucial to APAP overdose-induced hepatotoxicity since it results in ongoing liver damage [64,65]. Apoptosis is typically started by mitochondrial malfunction and is controlled by Bax and Bcl-2 [66]. Results from the TUNEL and Western blotting analyses in the current study demonstrated that CGA dramatically reduced the number of apoptotic cells and reversed the high Bax level and lowered the Bcl-2 level, showing that CGA had anti-apoptosis effects on the hepatotoxicity of APAP. These findings imply that the long-term consumption of food with high content of CGA results in a lower risk of APAP hepatotoxicity.
Autophagy modulates hepatic apoptosis to determine cell fate via complex cross-talk signals. Hepatocyte apoptosis and autophagy may overlap in liver damage, according to recent findings [67]. Limiting autophagy can reduce the hepatotoxicity produced by APAP, but liver damage from APAP treatment worsens after autophagy is stopped by p62 KO 24 h later [68,69]. Inadequate ATP synthesis is caused by mitochondrial malfunction, which also raises mitochondrial ROS, releases an excessive amount of cytochrome c (Cyt-c), upregulates Bax, caspase-3, and caspase-9, and starts the death cascade [70]. As expected, APAP overdose greatly hindered shifts of the LC3 protein from cytoplasmic to autophagosome form (LC3II) and markedly elevated p62 and Tom20 levels, whereas CGA therapy reversed the adverse effects of APAP overdose and significantly boosted LC3II expression on mitochondria. These results suggested that CGA protected against the cytotoxicity of APAP by inhibiting liver cell apoptosis while increasing hepatic autophagy.
APAP overdose frequently causes hepatotoxic insults by damaging mitochondria and increasing ROS. Traditionally, ATP generation and the creation or scavenging of free radicals occur in mitochondria. By eliminating ROS-damaged mitochondria, mitophagy maintains the equilibrium of mitochondrial function and ROS [16], indicating that mitochondria are a major target for APAP hepatotoxicity. According to recent research, mitophagy, particularly PINK1-mediated mitophagy, is crucial in clearing damaged mitochondria during APAP hepatotoxicity [71]. The PINK1/Parkin pathway, a well-known signaling pathway protein that controls mitophagy, can remove harmed or dysfunctional mitochondria [72,73]. Our results demonstrated that APAP decreased the expression of PINK1 and Parkin, as well as LC3II and LC3I, in vivo and in vitro, and increased the colocalization of LC3II and Tom20 on mitochondria, indicating that a PINK1/Parkin-mediated mitophagy deficit participates in and exacerbates APAP hepatotoxicity. Parkin is recruited by PINK1 to the mitochondrial membrane, starting the PINK1/Parkin-mediated mitophagy process [74]. Tom20 is a particular mitochondrial marker, and its expression is frequently linked to reduced mitochondrial damage and increased autophagy. Surprisingly, our findings revealed that CGA dramatically stimulated, in APAP-induced mice, increased levels of PINK1, Parkin, and LC3II/LC3I; reduced the levels of p62; and decreased the colocalization of LC3II and Tom20 on mitochondria, which were signs of mitophagy. The action of CGA in APAP-induced HepG2 cells was largely consistent with mouse studies. Additionally, the protective effect of PINK1 and Parkin increases due to CGA was reversed once PINK1 was knocked down by siPINK1 in vitro. These results suggested that the long-term consumption of food-derived CGA could prevent APAP hepatotoxicity by inducing mitophagy in a way that depends on PINK1. The present study has certain limitations, such as the question of whether CGA can lessen APAP hepatotoxicity when administered therapeutically and in age-matched mice for a certain number of weeks. This will be the direction of our future research.
Conclusions
A crucial mechanism by which APAP causes hepatotoxicity, as demonstrated by the current work, is via increasing apoptosis by inhibiting PINK1-dependent mitophagy. CGA could prevent APAP hepatotoxicity by activating PINK1-dependent mitophagy, inhibiting apoptosis, and decreasing serum aminotransferase activity. Our findings imply that the long-term consumption of foods that have high content of CGA may prevent APAP hepatotoxicity.
Informed Consent Statement: Not applicable.
Data Availability Statement: The data presented in the present study are available on request from the first author or corresponding author. All data are not publicly available due to privacy.
Conflicts of Interest:
The authors declare no conflict of interest.
|
galaxies
Face-on View of Galaxy NGC 4303 Reveals its Arms are Filled with Active Star Formation
Galaxies fill a lot of roles in the universe. The most obvious one is star formation factories. Without that activity, the cosmos would be a very different place. The European Southern Observatory and the Atacama Large Millimeter Array recently zeroed in on the galaxy NGC 4303. Their goal: to take a multi-wavelength view of its star formation activity.
The object was to help astronomers understand how stars form in galactic environments. The resulting image shows a golden glow of molecular clouds of gas threading through the spiral arms and the existence of already-formed stars.
NGC 4303 is a beautiful spiral galaxy located more than 50 million light-years away, in the Virgo Cluster of galaxies. Astronomers rank it as a weakly barred spiral. It also looks like it may have a ring structure within its spiral arms. The arms sparkle with star formation, making it a starburst galaxy. There’s has an active nucleus there, too, likely hiding a supermassive black hole.
This galaxy is classified as a late-type spiral. That means it turned gas into stars more slowly in the past and still has a lot left today. Sure enough, based on this and other studies, it appears very rich in neutral hydrogen. That’s the building block of stars.
The galaxy has a massive collection of stars at its heart. In addition, it sports older star clusters. These all indicate starforming activity in the ancient past. There’s also ample evidence of more recent star-birth activity across the entire galaxy. Bright nebulae highlight places where newborn stars are forming (or about to be born). So, why is this “late-type” galaxy so active when it comes to making stars?
Studying NGC 4303
To answer that requires looking at the galaxy in more than one wavelength of light. Astronomers used the Multi-Unit Spectroscopic Explorer (MUSE) instrument at the Very Large Telescope to study existing stars in the galaxy. It can image the galaxy in one observation. At the same time, it measures the intensity of light coming from various regions. In doing so, it provides a fascinating “3D” look at the galaxy and its components.
The Atacama Large Millimeter Array provided a different view using millimeter waves (close to radio waves). It specifically observes the clouds of hydrogen in the galaxy. The idea is to compare the amount of gas available for star formation to the populations of stars already formed. By using two different instruments, astronomers get a better idea of what triggers star birth. The joint studies also reveal processes and events that enhance the process.
In addition, they can also figure out what hampers the formation of stars in different regions. For example, the creation of supermassive stars can gobble up the available gas. That leaves very little to form smaller stars. In other places, the deaths of supermassive stars in supernova explosions send out shock waves. Those can trigger the process of star birth in nearby molecular clouds. For NGC 4303, astronomers will use data from this and other observations to figure out the history (and future) of its star formation activity.
Multiwavelength Studies of Galactic Star Formation: The Big Picture
This study of NGC 4303 is part of a larger effort called the Physics at High Angular Resolution in Nearby GalaxieS (PHANGS) project. It uses ground-based telescopes, as well as space-based observatories, to make detailed observations of neighboring galaxies. The idea is to look at all aspects of a galaxy’s structure using as many different approaches in as many wavelengths as possible. In particular, the project wants to study the physics and interactions of gas and star formation against a backdrop of galaxy structure and evolution.
PHANGS is joined by a number of other projects doing similar studies of galaxy evolution and star birth at different wavelengths. These include MUSTANG—the Multi-scale Star Formation across Nascent Galaxies project, which looks at the lifecycle of clouds and starforming regions. Data from that program is important in galaxy formation simulations.
In the case of NGC 4303, the extent of both past and future star formation looks quite impressive. The almost uniform distribution of neutral gas clouds across its spiral arms and core predicts a very bright future for this galaxy.
For More Information
A Hypnotising Galaxy
The PHANGS Survey
Carolyn Collins Petersen
Recent Posts
Gravitational Waves From Colliding Neutron Stars Matched to a Fast Radio Burst
A recent study by an Australian-American team has provided compelling evidence that FRBs may be…
3 hours ago
Plans are Underway to Build a 30 Cubic Kilometer Neutrino Telescope
How do astronomers look for neutrinos? These small, massless particles whiz through the universe at…
3 hours ago
China Hints at Its Goals for a Lunar Base
At a recent national space conference, scientists with the Chinese Academy of Sciences shared the…
1 day ago
Artemis II is Literally Coming Together
NASA engineers have completed assembling the core stage of the Artemis II rocket, which will…
1 day ago
It's Time For Your Annual Weather Update for the Outer Solar System
A couple times a year, the Hubble Space Telescope turns its powerful gaze on the…
1 day ago
Europa’s Ice Rotates at a Different Speed From its Interior. Now We May Know Why
Jupiter’s moon, Europa, contains a large ocean of salty water beneath its icy shell, some…
2 days ago
|
Rook, Magpie, Sgc. — February 11th. A fearful south-westerly storm has to-day brought many of our finest old elms to the ground. One of gigantic growth (referred to at Zool. 0500) is 6 feet 7 inches in dia meter at eight feet from the ground, just below the fork, though five feet lower down it measures but 4 feet 2 inches. Its height is calcu lated to be about a hundred feet. This was the monarch of the Bon church grove, and probably the largest elm in the Island. Another tree, next in size, has shared the same fate, both having fallen into the little lake, but fortunately the swans escaped. I may remark here that the cygnet, which is now a full-grown two-year old bird, in perfect adult plumage, has the bill of a dusky greenish yellow at the base, and of a bright pinkish colour on the ridge, the latter hue gradually extending to the sides, but there is not a shade of orange as yet. Another large elm, near the old church, having rooks' nests in it, but no eggs that I know of, has been blown down too. Few birds were able to face the tempest, and I observed a magpie carried away by it, its long tail doubled under the body and protruding beyond the beak.
numbers.
IVoodpigeoii. — Has been more than usually abundant, and I am informed by a neighbour, whose grounds are well-wooded, that they frequently alight in his garden to feed on the cabbages, which I find have the top leaves eaten off, as if by rabbits, but a wire netting protects them from the ravages of the latter.
Redthroated Loon. — Though this species is still on our coast, com paratively iew are to be met wilh now, and they have been found unapproachable, not one having been shot lately.
Great Northern Diver. — A large blackheaded diver — which could be no other than a bird of this species — was met with off Shaukliu towards the middle of the month, but there was no getting
|
THE HUMMINGBIRD HAWKMOTH. 285
scent, that " aromatic soul of flowers" which is principally exhaled at these periods ; delighting in the jasmine, marvel of Peru, phlox, and such tubular flowers; and it will even insert its long, flexible tube into every petal of the carnation, to extract the honeylike liquor it contains. It will visit our geraniums and greenhouse plants, and, whisking over part of them with contemptuous celerity, select some composite flower that takes its fancy, and examine every tube with rapidity, hovering over its disk with quivering wings, while its fine hawklike eyes survey all surrounding dan gers. The least movement alarms it, and it darts away with the speed of an arrow ; yet returns, and with suspicious vigilance continues its employ, feeding always on the wing. Nature seems to have given this creature some essential requisites for its safety ; its activity, when on the wing, renders its capture difficult ; and when it rests, it is on a wall, the bark of a tree, or some dusky body, that assi milates so nearly to its own colour, as to render it almost invisible, though watched to its settlement : the larva is seldom found. We sometimes see it enter our rooms, attracted by flowers in the open windows ; but it seems to be immediately aware of its danger, disappears in an instant, and is safe from capture. Wild and fearful as this creature is by nature, yet continued gentle treatment will re move much of its timidity, and render it familiar to our presence. Perfectly free from any annoyance as they are when ranging from sweet to sweet on
|
Fis. 29.
the cut, of -|-inch round iron, drawn smaller toward the point — and the point made safe by a knob. The other end is furnished with a socket, which receives a handle six or eif^ht feet long. The manner of using it is thus described in Mr. Ste phens's admiralilc "Book of the Farm":
" The hind-leg is hooked in at a, from behind the sheep, and it fills up the narrow part beyond a, while passing along it until it reaches the loop, when ihe animal is caught by the hock, and when secured, its foot ea sily slips lhro\igh the loop. Some caution is required in using the crook, for should the sheen give a sudden start forward to get away, the mo ment it feels the crook the leg will be drawn forcibly through the narrow part, and strike the bone wiih such violence agninst the bend of the loop as to cause the animal considerable pain, and even occasion lameness for some days. On first embracing the leg, the crook should be drawn quickly tovvm-d you, so as to bring the bend of the loop against the leg as high up as the hock, before the sheep has time even to break oft', and be ing secure, its straggles will cease the moment your hand seizes the leg."
No flock-master should be without this implement, as it saves a vast deal of yarding, running, &c., and leads to a prompt examination of every improper or suspicious ap pearance, and a timely application of remedy or preven tive — which would often be deferred if the whole flock had to be driven to a distant yard, to enable the shepherd to catch a particular sheep.
Dexterity in the use of the crook is speedily acquired by any one ; and if a flock are properly tame, any one of its number can be readily caught by it, at salting-time — or, generally, at other times, by a person with whom the flock are familiar. But it is at the lambing-time, when sheep and lambs require to be so repeatedly caught, that the crook is more particularly ser viceable. For this purpose, at this time alone, it will pay for itself ten times over in a single season, in saving time, to say nothing of the advan tage of the sheep.
CKOOK.
Summering Manure. — Notwithstanding all that has been said and written showing that fresh maniu-e immediately applied to the land, or such as is presen'ed in tanks or under cover, or by a mixture with straw or eaith, is at least four times the value of that left in the barn-yard all summer exposed to sun ayd rain, wasting its richness in the air and drenching its fertilizing salts away ; yet many fanners still believe, or act upon the principle of behef that manure is lilie cider, growing better with age ; and thus their dung is safely kept in the yard till August or September, a great nuisance to all around, and a sad loss to the grow ing crops. We are well awai-e that rotted maimre is considered indispensable for certain crops, and therefore may say they prefer to sustain the loss of its rotting to the inconvenience of usin" it in an unfei-mentcd state. Let thtjse who thus think consider that when manure has become i-otted it is then mere humus or vegetable matter, such as decomposed leaves of trees, sti-aw, hay, coni-stalks, muck, tmf, peat, road and ditch scrapings, which may be had on every fami to answer the Fame purpose as rotted manure. How many farmers let all these substances go to waste, thus subjecting themselves to a double loss — a depreciation in the value of their manixre, and a neglect of the vegetable matters on theii- premises and around them.
Chloride of Soda. — Chloride of soda is said, in the London Lancet, a medical work, to be an effectual cure for a burn. It is stated in tliat journal, as an example, that an attorney, in at tem"tinf? to put out llie flames that had attacked die curtains of liis bed, got Ids hands burned and 'blistered, but not broken. He scut for a couple of quarts of the loUon, fourouuces of the solu tion to a pint of water, had it poured into soup-plates, wrapped bis bauds in lint, as no skin was broken, and so kept them for some lime. Next morning be was so perfectly -well that only one email patch of burn remained, yet an hour bad elapsed before the application. It is added that the same remedy is sufiRcieut to" heal scalds and black eye. (660)
|
<?php
namespace Pinq\Tests\Integration\Providers\DSL\Implementation\Preprocessors;
use Pinq\Expressions as O;
use Pinq\Expressions\VariableExpression;
use Pinq\Providers\DSL\Compilation\Processors\Expression;
use Pinq\Queries;
use Pinq\Queries\Functions\IFunction;
/**
* @author Elliot Levin <[email protected]>
*/
class VariablePrefixerProcessor extends Expression\ExpressionProcessor
{
/**
* @var string
*/
private $prefix;
public function __construct($prefix)
{
$this->prefix = $prefix;
}
public static function factory($prefix)
{
return function (Queries\IQuery $query) use ($prefix) {
return Expression\ProcessorFactory::from($query, new self($prefix));
};
}
public function walkVariable(VariableExpression $expression)
{
$name = $expression->getName();
if ($name instanceof O\ValueExpression) {
return $expression->update(
O\Expression::value($this->prefix . $name->getValue())
);
}
return $expression->update(
O\Expression::binaryOperation(
O\Expression::value($this->prefix),
O\Operators\Binary::CONCATENATION,
$name
)
);
}
public function processFunction(IFunction $function)
{
$parameterScopeVariableMap = array_map(function ($variable) { return $this->prefix . $variable; }, $function->getParameterScopedVariableMap());
return $function->update(
$function->getScopeType(),
$function->getNamespace(),
$parameterScopeVariableMap,
$this->walkAll($function->getParameters()->getAll()),
$this->walkAll($function->getBodyExpressions())
);
}
}
|
Electron discharge device
1954 s. w. LEFCOURT EI'AL I 2,693,397
ELECTRON DISCHARGE DEVICE Filed July 1, 1948 SILVER Mf lG/VES/UM .0 I u 1 a 1 I l 0 z a 4 5 6 7 a HOURS OF LIFE INVENTORS Sta/2Z6 11/. Le fi'c auri' FIE-4.- Haber Mayer Alto/hey United States Patent ELECTRON DISCHARGE DEVICE Stanley W. Lefcourt, New York, N. Y., and Robert Mayer,
Havertown, Pa., assign ors to Sylvania Electric Products Inc., a corporation of Massachusetts Application July 1 1948, Serial No. 36,326
2 Claims. (Cl. 313-103) This invention relates to an electron discharge device more particularly to a device of this type which contains a secondary electron emitter and to the method of making such an emitter.
For one reason or another it has heretofore been considered necessary to mechanically attach the secondary electron emitter to a support structure which passes through the tube envelope. This type of structure was considered to be particularly necessary in a microwave dynatron in which the secondary emitter is spaced only a few thousandths of an inch from an oxide coated filament. A structure of this type is shown in the patent application filed by George D. ONeill on March 13, 1948, hearing Serial No. 14,807, now Patent No. 2,679,591.
In view of the two-piece structure, that is, the emitter support rod with the attached electron emitter, it was heretofore necessary to provide a threaded hole at the bottom of the emitter support rod, a thread at the top of the emitter-electrode, a wrench 'hole at the side of the emitter, a thread at the outer edge of the grid frame and a threaded inner edge at the grid shell. Since the presence of these features required special machining of each of the parts, the structure was quite expensive and did not lend itself to high production techniques.
Among the reasons that this type of structure was deemed necessary are the following: The electrode support rod, since it passes through the glass envelope, must be made of a material which will permit good glass-to- --rnetal seals and none of the base materials which had heretofore been used for making the secondary emitter electrodes was suitable for such use, that is, none of the materials would permit the obtaining of the desired high secondary emission characteristics. Furthermore, the silver magnesium alloy which had heretofore been used for this purpose and which was sensitized with cesium is extremely unstable at the high temperatures which would be developed in this region during the period in which the grid frame is sealed to the glass envelope.
An object of this invention is to provide a simplified and more economical structural design for electron discharge devices having an electron emitting electrode.
A further object of this invention is to provide a more stable secondary electron emitter which can be present within a glass envelope at the time glass scaling is carried out in its vicinity.
In accordance with our invention we have found that these and other objects and advantages can be achieved if the secondary emission electrode support rod is made of a nickel chrome iron alloy of the type described in Patent No. 2,284,151 issued to Walter E. Kingston in which the nickel content is 345%, the chromium content 3-15 and the metals of the group consisting of aluminum, zirconium, calcium .1 to 2%, and the balance substantially of iron.
The invention in its several aspects will be better understood from the following detailed description of the illustrative form of dynatron shown in the drawing.
Fig. 1 is a longitudinal section of a planar grid tube showing the improved simple structure,
Fig. 2 is an enlarged fragmentary longitudinal section of Fig. 1, and
Fig. 3 is an enlarged fragmentary longitudinal section showing the electron emitter attached to the old type support rod and Fig. 4 is a chart showing comparative life of two different dy nodes.
A simple embodiment of the features of this in venice .tion is shown in Fig. 1 of the drawings wherein the rod 10 which passes through the glass envelope 12 and is sealed thereto at point 14 is the .secondary .emittingelectrode .or dynode. The base or face of the rod 10 being the sensitized surface 16, facing the oxide coated filament 30 with a screen grid 22 interposed therebetween. The rod 10 in this embodiment of our invention is made of the above-noted nickel chrome alloy which is referred to in the trade as Alloy No. 4 and is further sensitized with a secondary emission material 18.
The grid 22 illustrated in the drawings, is a planar mesh grid mounted on a grid frame 24 which passes through the glass envelope and is sealed thereto forming a skirt 26 on the outside of the tube envelope.
The primary emitter electrode shown in this embodiment of our invention is an oxide coated filament 30 mounted on a mica disc 32.
The fragmentary view of the relevant portions of the tube shown in Fig. 3 illustrate the prior art type design in which the electrode support rod 40 which passes through the envelope in the same manner shown in Fig. l is made of copper rod and the secondary emitter electrode itself is made of a silver magnesium alloy 42 which has been activated with a thin film of cesium 44 being deposited thereon. in view of the fact that the silver magnesium metal is not a good material for obtaining glass-to-metal seals, the electrode material is provided with a thread 46, which is adapted to fit into the thread hole 48 at the bottom of the electrode support 49 and, furthermore, since the electron emitting material is not stable in the presence of heat when sealing the glass envelope to the grid support, a special grid frame 50 with a threaded outer edge 52 is provided to fit into and be adaptable for threading into the inner edge of the grid shell 54. With the aid of these features it was thereby possible to first seal the secondary emitter electrode sup port through and to the glass envelope thereupon seal the envelope to the grid shell 54 after which the secondary electrode or dynode 42 is screwed into the electrode support rod by means of the thread on top of the electrode and the threaded hole on the bottom of the electrode, special wrench holes, 56 and 58 being provided in the electrode and the electrode support for this purpose. After the electrode had been properly fastened to the electrode support rod it was then possible to thread the grid frame, with the grid, into place. Special wrench holes'60 and 62 were also provided in the grid frame for this purpose.
By comparison of the two embodiments shown in the drawings, it can readily be seen that the embodiment illustrated in Fig. 1 is a much simpler structure and much more economical to produce. The fact that the emitter support rod forms a base for the secondary emission surface while simultaneously serving as the material to which glass is directly sealed eliminates the need for threading a hole at the bottom of the electrode support rod, threading the top of the separate small electrode, providing wrench holes at the side of the electrode and the support rod, threading the outer edge of the grid frame and threading the inner edge of the grid shell as well as supplying wrench holes in order that these two may be properly fastened together.
The No. 4 alloy, when used as shown, readily lends itself to sensitization by coating with secondary emission materials such as the alkali metals and the alkali earth metals. Particularly good results have been obtained when thin deposits of the oxides of these metals such as for example barium oxide, cesium oxide and cesium silver oxide have been used.
Not only has the No. 4 alloy proven to be a good material for use as a secondary emitting electrode material because of its good glass-to-metal sealing properties but it has also proven itself to be an excellent medium for sensitization with the alkaline earth or alkali metals. The surfaces so produced have been found to be extremely stable even in the presence of heat such as is encountered in those areas in which glass-to-metal seals are being made. Furthermore, surfaces sensitized in this manner have been found to give long life secondary emitters, even in those cases in which the emitter surface faces the oxide-coated filament and is not provided with a shield therebetween. In those cases in which it has heretofore been deemed necessary to have this secondary emitter surface close to the oxide filament it had been deemed a necessary adjunct that the secondary emitter life would be very short for example when tubes of the type as shown in Fig. l were made with the secondary emitter being cesium on silver magnesium the tube life was approximately 1 hour. However, since using No. 4 alloy as the base metal for sensitization with the thin deposits of the alkali metals and the alkali earth metals tube life has been increased. This is clearly shown in Fig. 4 in which the secondary emission ratio is charted against hours of life. In the illustration there shown the life of a cesium activated silver magnesium dynode is compared with the life of a No. 4 alloy dynode sensitized with barium oxide. The ratio of 1.5 is approximately the minimum usable value. It has further been found that the life of the dynode can be further increased without deleteriously afiecting its heat stable characteristics by sensitizing its surface with a mixture of cesium oxide and silver oxide. Dy nodes having a life of two hundred hours when used in electron discharge devices of the type illustrated have been made and tested.
There are numerous methods by means of which thin deposits of the sensitizing material can be applied to the No. 4 alloy. A preferred example of such method being one in which an alkali metal compound such as cesium carbonate together with silver oxide is applied to the back of the getter in such position that the applied material upon vaporization will deposit upon the secondary electrode surface. This can often be advantageously coupled with a later bombardment of the grid to vaporize and drive off any of the sensitizing compound deposited thereon which revaporized compound may be redeposit on the secondary electrode surface. During operation of the electron discharge device which consists primarily of a filamentary cathode 30, an electrode 22 termed a grid and conveniently formed of wire mesh and a secondary-emissive electrode 16 herein termed a dynode, the grid accelerates the primary electron stream from the cathode to the dynode and also serves to collect the secondary electrons emitted by the dynode. If a fixed potential difference is established between cathode 30 and grid 22 to make the latter positive, and various static voltages are applied to dynode 16, the dynode current will be observed to increase gradually. After a certain point the dynode current will decrease almost linearly to a minimum, even reversing direction, and thereafter it will increase again. This may be understood by recognizing the composite character of the dynode current, including a part of the primary electron emission leaving cathode 30 which penetrates the interstices of grid 22 to impinge upon the dynode 16 and,
subtracted from this, is the secondary electron emission resulting from this primary-electron bombardment. Between certain limits, the decrease of current drawn by the dynode and finally, the, true reversal of current in the dynode as the dynode potential is increased shows the dynatron to be a negative resistance device. This negative resistance characteristic can be variously used, as for amplifying, for detecting, and for modulating.
While the above description and the drawings submitted herewith disclose preferred and practical embodiments of the electron discharge device of this invention it will be understood by those skilled in the art, that the specific details of construction and arrangement of parts as shown and described are by way of illustration and are not to be construed as limiting the scope of the invention.
What is claimed is:
1. In an electron discharge device a glass envelope, a nickel iron chromium alloy rod extending through said glass, said alloy having a nickel content of 38-45%, a chromium content of 315%, .1 to 2% of the metals selected from the group consisting of aluminum, zirconium and calcium and the balance substantially iron, said rod having a sensitized surface formed by a thin deposit of a cesium oxide, silver oxide complex thereon, an oxide coated filament spaced directly opposite said sensitized surface with a planar grid therebetween.
2. In an electron discharge device, a glass envelope, a nickel-iron, chromium alloy rod extending through said glass envelope, said alloy having a nickel content of 38-45 percent, a chromium content of 3-15 percent, .l2 percent of the metal selected from the group consisting of aluminum, zirconium and calcium and the balance substantially iron, said rod having a sensitized surface formed by a thin deposit of the oxides of a metal selected from the group consisting of the alkali and alkaline earth metals thereon, and an oxide coated filament spaced directly opposite said sensitized surface with a planar grid therebetween.
References Cited in the file of this patent UNITED STATES PATENTS Number Name Date 2,284,151 Kingston May 26, 1942 2,353,743 McArthur July 18, 1944 2,390,701 Ferris Dec. 11, 1945
1. IN AN ELECTRON DISCHARGE DEVICE A GLASS ENVELOPE, A NICKEL IRON CHROMIUM ALLOY ROD EXTENDING THROUGH SAID GLASS, SAID ALLOY HAVING A NICKEL CONTENT OF 38-45%, A CHROMIUM CONTENT OF 3-15%, .1 TO 2% OF THE METALS SELECTED FROM THE GROUP CONSISTING OF ALUMINUM, ZIRCONIUM AND CALCIUM AND THE BALANCE SUBSTANTIALLY IRON, SAID ROD HAVING A SENSITIZED SURFACE FORMED BY A THIN DEPOSIT OF A CESIUM OXIDE, SILVER OXIDE COMPLEX THEREON, AN OXIDE COATED FILAMENT SPACED DIRECTLY OPPOSITE SAID SENSITIZED SURFACE WITH A PLANAR GRID THEREBETWEEN.
|
Opening to Pat & Mat AMC Theaters 2009
* 1) AMC Theatres "Coming Soon" (2009-2013) Bumper
* 2) Cloudy with a Chance of Meatballs trailer
* 3) 9 trailer
* 4) Planet 51 trailer
* 5) Alvin and the Chipmunks: The Squeakquel trailer
* 6) Where the Wild Things Are trailer
* 7) The Princess and the Frog trailer
* 8) Ice Age: Dawn of the Dinosaurs trailer
* 9) AMC Theatres "Silence Is Golden" (2002-2011) Bumper
* 10) AMC Theatres "Feature Presentation" (2009-2013) Bumper
* 11) The Incredible Texan Raccoon short film
* 12) 20th Century Fox logo
* 13) Aardman Animations (2000-2009) logo
* 14) Studio PatMat s.r.o “Mat painting on white screen” logo
* 15) Start of the film
|
using System;
using System.ComponentModel;
using System.Windows.Forms;
namespace net.elfmission.WindowsApps
{
/// <summary>
/// Windowsアプリケーションで使用するフォームのスーパークラス。
/// </summary>
public partial class elfForm : Form
{
#region "プロパティ"
/// <summary>
/// 製品情報をタイトルバーに表示するかを表すbool。
/// </summary>
[DefaultValue(false)]
public bool ShowProductInformationAtTitle { get; set; } = false;
#endregion
#region "メソッド"
/// <summary>
/// 画面の位置・サイズを復元します。
/// </summary>
/// <param name="info">画面の復元情報を表すFormRestoreInformations。</param>
protected void restoredForm(FormRestoreInformations info)
{
this.WindowState = info.WindowState;
this.Width = info.FormSize.Width;
this.Height = info.FormSize.Height;
this.StartPosition = info.StartPosition;
if (info.StartPosition == FormStartPosition.Manual)
{
this.Left = info.FormPosition.X;
this.Top = info.FormPosition.Y;
}
}
/// <summary>
/// 問い合わせメッセージを表示します。
/// </summary>
/// <param name="msg">メッセージに表示する文字列。</param>
/// <returns>ユーザの操作結果を表すDialogResult列挙型の内の1つ。</returns>
protected DialogResult showQuestionMessage(string msg)
{
return WindowsApps.Controls.WinControlUtility.ShowQuestionMessage(this, msg);
}
/// <summary>
/// 情報メッセージを表示します。
/// </summary>
/// <param name="msg">表示するメッセージ。</param>
protected void showInformationMessage(string msg)
{
WindowsApps.Controls.WinControlUtility.ShowInformationMessage(this, msg);
}
/// <summary>
/// エラーメッセージを表示します。
/// </summary>
/// <param name="msg">表示する文字列。</param>
protected void showErrorMessage(string msg)
{
WindowsApps.Controls.WinControlUtility.ShowErrorMessage(this, msg);
}
/// <summary>
/// 警告メッセージを表示します。
/// </summary>
/// <param name="msg">表示する文字列。</param>
protected void showWarningMessage(string msg)
{
WindowsApps.Controls.WinControlUtility.ShowWarningMessage(this, msg);
}
/// <summary>
/// Loadイベントを発生させます。
/// </summary>
/// <param name="e">イベントデータを格納しているEventArgs。</param>
protected override void OnLoad(EventArgs e)
{
base.OnLoad(e);
// タイトルに製品情報を表示
if (this.ShowProductInformationAtTitle)
{
this.Text = Application.ProductName + " Ver." + Application.ProductVersion;
}
}
#endregion
#region "コンストラクタ"
/// <summary>
/// デフォルトコンストラクタ。
/// </summary>
public elfForm()
{
InitializeComponent();
}
#endregion
}
}
|
OLD-FASHIONED LILAC. This is an old, old favorite which everyone knows and loves. Tall grower with immense flowers : . . shrub which will never go out of style! 69c each. 3 for $1.95. Postpaid. MOCK ORANGE. Of upright growth reaching a height of about 5 ft. Has very small, dainty leaves of rich dark green. Highly scented, beautiful white flowers. Price: 2-ft. plants. 34c each. Postpaid. SCOTCH BROOM. Rare, a plant of value to any landscape that is in need of color. In April this plant is a solid mass of golden yellow blooms resembling the Sweet Pea. Makes a wonderful cut flower to fill vases. Blooms about 2 months. A native peel of aaa Price: Strong 2-yr. plants, 39c ea. Pos WHITE SNOWBERRY. Desirable shrub with small pink flowers followed by large waxy white berries which hang on the plant throughout the winter months. Very showy. Hardy everywherePrice: 2-ft. plants, 49c each. Postpaid. RED SNOWBERRY. Pink flowers followed by large red, wax-like berries that hang on the plant through the winter. Very showy. Does well everywhere. Excellent for planting in shady places. Price: Strong 2-ft. plants, 39c each. Postpaid. WHITE FLOWERING DOGWOOD. (Cornus Florida). Tree form. Produces solid mass of beautiful white blooms in early spring. Foliage dark green with very attractive leaves. Very hardy. Price: 2 to 3-ft. plants, 39c each: 3 to 4-ft. plants, 49c each. Postpaid. GOLDEN BELL. Erect growing, tall and slender with lovely flowers of rich yellow in early spring. Price: 2-ft. plants, 39c each. Postpaid. WEIGELA ROSEA. Tall-growing with deep pink, trumpet-shaped flowers borne thickly along the stems. Blooms abundantly throughout summer. Price: ob plants, 39c each; 3-ft. plants. 49¢c each. Postpai YELLOW WEIGELA. The beautiful golden flowers of this Weigela make it particularly fine for mass and hedge planting. Bright green leaves borne thickly; trumpet-shaped yellow flowers. Price: 1%-ft. size, 49c: 2 for 89c. Postpaid. WEIGELA HENDERSONIA. One of the best of the es family. The leaves are bright green
CRAPE MYRTLE
Extremely hardy, does well in any soil, can be planted in full or half sun. Blooms from mid-summer until frost, when most flowers are gone. Plant in masses, hedges or as single specimens. Truly, | the most gorgeous flowering shrub. | Colors: Red, pink, purple. Specify color wanted. Price: 2-ft. plants, 49c each. Post-
ORANGE FLOWERING POMEGRANATE.
One of the finest and most gorgeous of the flowering shrubs. Thick, metallic green foliage on strong upright canes; large, double blooms of bright orange splashed yellow, copper and red, followed by inedible orange fruit. Hardy, easy to grow, excellent for background. Strong 2-ft. plants, 39c each: 3-ft., 49c each. PURPLE LEAF PLUM. (Prunus Pissardi) Black bark, with leaves of striking, pinkish-purple color and lovely white blossoms. Price: Strong 2 to 3-ft. plants, 59c each. Postpaid. ALL-RED PLUM. A red-leaf plum which blooms beautifully, then doubles your pleasure by producing a bountiful crop of delicious red-meated plums in the late summer. Well-named — leaves, stems, branches, fruit : .. even the seed... are all a oda 2 to 3-ft. trees, 98c each: 3 for $2.79. PostPo NOWBALL. A rare shrub. Grows to height of 6 feet. Foliage has purple cast shaded dark-green. Large, gorgeous white blooms in early June make it Aslan ee Price: Strong 2-yr. plants, 59c each. pore “FLOWERING PEACH. Large type flowering tree, having same foliage as the fruit tree. Beautiful when in bloom in early spring. Flowers large double red. Price: 2 to 3-ft. plants, 59c each; 3 to 4-ft. plants, 69c each. Postpaid.
WHITE FLOWERING PEACH.
This lovely white flowering tree has the same habits as the Red Flowering Peach only the color of the bloom is white. Price: 2-3 ft. plant, 59c each; 3-4 ft. plant. 69c each: Postpaid. RED LEAF PEACH. Brand new and a dandy. Foliage bright red in spring and summer. Flowers rose-pink. Price: 2-ft. plants, 89c each. Postpaid.
GOLDEN RAIN TREE. Large
round leaves With white blossoms in May followed by gold-yellow foliage in midsummer. Price: Strong 2-ft. plants, 69c each. Postpaid.
spicy fragrance. Grows to about 4 feet, From mid-summer to early fall it is covered with lilac or lavender flowers on heavy dense spikes. Sure_ to bloom this year. Price: 2-ft. plants, 39c each. Postpaid.
ly colored. Slender leaves and long white catkins are borne along stems. Great novelty plant. Price: ace t 2-ft. plants, 49c each. Postpaid. MIMOSA (Silk Tree). Dense-
FLOWERING ALMOND
Of upright growth with lovely pink flowers in early spring. Tiny little leaves borne on long stems make it very useful in any landscape. Hardy. Price: Strong 2-ft. plants, 69c each. Postpaid.
|
// https://www.hackerrank.com/challenges/hackerrank-language/problem
function processData(input) {
let s = 'C:CPP:JAVA:PYTHON:PERL:PHP:RUBY:CSHARP:HASKELL:CLOJURE:BASH:SCALA:ERLANG:CLISP:LUA:BRAINFUCK:JAVASCRIPT:GO:D:OCAML:R:PASCAL:SBCL:DART:GROOVY:OBJECTIVEC';
let i = input.split('\n');
i.shift();
i.forEach(a => {
let st = a.split(' ');
let l = st[1];
let r = new RegExp(`\\b${l}\\b`, 'g')
console.log((s.match(r)) ? 'VALID' : 'INVALID');
});
}
process.stdin.resume();
process.stdin.setEncoding("ascii");
_input = "";
process.stdin.on("data", function (input) {
_input += input;
});
process.stdin.on("end", function () {
processData(_input);
});
/*
import re
s = 'C:CPP:JAVA:PYTHON:PERL:PHP:RUBY:CSHARP:HASKELL:CLOJURE:BASH:SCALA:ERLANG:CLISP:LUA:BRAINFUCK:JAVASCRIPT:GO:D:OCAML:R:PASCAL:SBCL:DART:GROOVY:OBJECTIVEC'
s = s.replace(':', '|')
r = re.compile(r'^[1-9]\d{4}\s' + '(' + s + ')$')
for i in range(int(input())):
print('VALID') if r.match(input()) else print('INVALID')
*/
|
using System.Collections;
using System.Collections.Generic;
using UnityEngine;
namespace Fjord.Common.Components
{
/// <summary>
/// Common shortcuts which should be in all applications.
/// </summary>
public class ShortcutProcessor : MonoBehaviour
{
[Header("Scene to load on F5 Press")]
[SerializeField]
private string _reloadSceneName;
private void Update()
{
if (Input.GetKeyUp(KeyCode.F5))
{
Application.LoadLevel(_reloadSceneName);
}
}
}
}
|
package com.ccclubs.admin.service.impl;
import com.ccclubs.protocol.dto.gb.GBMessage;
import com.ccclubs.protocol.dto.gb.GB_02;
import com.ccclubs.protocol.dto.gb.GB_02_01;
import com.ccclubs.protocol.dto.gb.GB_02_05;
import com.ccclubs.protocol.inf.IRealTimeAdditionalItem;
import com.ccclubs.protocol.util.Tools;
import org.springframework.stereotype.Service;
import com.ccclubs.frm.base.CrudService;
import com.ccclubs.admin.orm.mapper.GbStateMapper;
import com.ccclubs.admin.model.GbState;
import com.ccclubs.admin.service.IGbStateService;
import java.util.ArrayList;
import java.util.List;
/**
* 车辆国标历史信息的Service实现
* @author Joel
*/
@Service
public class GbStateServiceImpl extends CrudService<GbStateMapper, GbState, Integer> implements IGbStateService{
/**
* 需要转换的GBMessage一定要包含GB0201与GB0205
*
* @param gbMessage
*/
@Override
public GbState transferGbMessageToGbState(GBMessage gbMessage) {
GbState gbState=null;
if (null!=gbMessage&&null!=gbMessage.getMessageContents()){
GB_02 gb_02=(GB_02) gbMessage.getMessageContents();
GB_02_01 gb_02_01=null;
GB_02_05 gb_02_05=null;
for (IRealTimeAdditionalItem iRealTimeAdditionalItem:gb_02.getAdditionals()){
if (iRealTimeAdditionalItem.getAdditionalId()==1){
gb_02_01=(GB_02_01) iRealTimeAdditionalItem;
continue;
}
if (iRealTimeAdditionalItem.getAdditionalId()==5){
gb_02_05=(GB_02_05)iRealTimeAdditionalItem;
continue;
}
}
if (!(gb_02_01==null&&gb_02_05==null)){
gbState=new GbState();
gbState.setvin(gbMessage.getVin());
gbState.settimeString(gbMessage.getMessageContents().getTime());
gbState.setHexString(gbMessage.getPacketDescr());
if (gb_02_01!=null){
gbState.setAcceleratedPedalStrokeValueString(gb_02_01.getAcceleratedPedalStrokeValueString());
gbState.setBrakePedalStateString(gb_02_01.getBrakePedalStateString());
gbState.setChargingString(gb_02_01.getChargingString());
gbState.setCurrentString(gb_02_01.getCurrentString());
gbState.setDcDcStatusString(gb_02_01.getDcDcStatusString());
gbState.setGearString(gb_02_01.getGearString());
//gbState.setGsId();
gbState.setInsulationResistanceString(String.valueOf(gb_02_01.getInsulationResistance()));
gbState.setMileageString(gb_02_01.getMileageString());
gbState.setRunningModeString(gb_02_01.getRunningModeString());
gbState.setSocString(gb_02_01.getSocString());
gbState.setSpeedString(gb_02_01.getSpeedString());
gbState.setVehicleStatusString(gb_02_01.getVehicleStatusString());
gbState.setVoltageString(gb_02_01.getVoltageString());
}
if (gb_02_05!=null){
gbState.setLatitudeString(Float.valueOf(gb_02_05.getLatitude()));
gbState.setLongitudeString(Float.valueOf(gb_02_05.getLongitude()));
gbState.setPositionStatusString(gb_02_05.getPositionStatusString());
}
}
}
return gbState;
}
@Override
public List<GbState> transferAllGbMessagesToGbStates(List<GBMessage> gbMessageList) {
List<GbState> gbStateList=null;
if (null!=gbMessageList&&gbMessageList.size()>0){
gbStateList=new ArrayList<>();
for (GBMessage gbMessage:gbMessageList){
gbStateList.add(transferGbMessageToGbState(gbMessage));
}
}
return gbStateList;
}
}
|
// ==========================================================================================================
// Configuration
// ==========================================================================================================
/**
* The CI Env config
* @typedef CiEnv
*
* @property {String} buildNumber - the environment variable that will hold the build number
* @property {String} pr - the environment variable that will hold the PR number (if it's a PR build)
* @property {String} repoSlug - the environment variable that will hold the repo slug (owner/repo)
*/
/**
* The git user
* @typedef GitUser
*
* @property {String} email - the github user email to use for commits
* @property {String} name - the github user name to use for commits
*/
/**
* The CI (continuous integration) config
* @typedef CiConfig
*
* @property {String} buildNumber - the number of the build (in a string) pulled from the env
* @property {CiEnv} env - the environment variables used by the CI system
* @property {GitUser} gitUser - the user to configure git with for making commits
* @property {String} provider - the CI provider (one of "travis" or "teamcity" for now)
*/
/**
* The VCS Env config
* @typedef VcsEnv
*
* @property {String} password - the name of the environment variable that holds the vcs password
* @property {String} readToken - the name of the environment variable that holds the vcs read-only token
* @property {String} username - the name of the environemnt variable that holds the vcs username
* @property {String} writeToken - the name of the environment variable that holds the vcs read-write token
*/
/**
* The VCS Auth config (pulled from the environment using VcsEnv)
* @typedef VcsAuth
*
* @property {String} password - the actual vcs password
* @property {String} readToken - the actual vcs read token
* @property {String} username - the actual vcs username
* @property {String} writeToken - the actual vcs read/write token
*/
/**
* The Vcs config
* @typedef VcsConfig
*
* @property {VcsAuth} auth - the auth info pulled from the env given
* @property {String} domain - the domain for version control system (defaults to github.com for GitHub)
* @property {VcsEnv} env - the environment variables that can be used to interact with the VCS
* @property {String} provider - the VCS provider ("github" or "bitbucket-server" right now)
*/
/**
* The configuration object that can be customized with .pr-bumper.json
* @typedef Config
*
* @property {CiConfig} ci - the CI build configuration
* @property {Boolean} isPr - true if pull request build
* @property {String} owner - the organization/user/project that owns the repository
* @property {String} prNumber - the pull request number (as a string, i.e. "15")
* @property {String} repo - the name of the repository
* @property {VcsConfig} vcs - the VCS configuration
*/
// ==========================================================================================================
// Version Control
// ==========================================================================================================
/**
* The representation of a commit within the GitHub API
* @typedef GitHubCommit
* @property {String} sha - the SHA hash for the commit
*/
/**
* The shape of the PR pulled from GitHub's `/repos/:owner/:repo/pulls` API
* {@link https://developer.github.com/v3/pulls/}
*
* @typedef GitHubPullRequest
* @property {Number} number - the PR #
* @property {String} body - the description of the PR
* @property {String} html_url - the URL for the web interface of the PR
* @property {GitHubCommit} head - representation of the tip commit from the branch being merged
* @property {GitHubCommit} base - representation of the tip commit from the branch being merged into
*/
/**
* The representation of a reference within the Bitbucket Server API
* @typedef BitbucketRef
* @property {String} id - the id of the git ref
* @property {String} latestCommit - the SHA hash for the latest commit in the git ref
*/
/**
* An object to wrap a Bitbucket link
* @typedef BitbucketLink
* @property {String} href - the actual link
*/
/**
* The shape of the PR pulled from Bitbucket's `/projects/:owner/repos/:repo/pull-requests` API
* {@link https://developer.atlassian.com/static/rest/bitbucket-server/4.6.0/bitbucket-rest.html#idp1756896}
*
* @typedef BitbucketPullRequest
* @property {Number} id - the PR #
* @property {String} description - the description of the PR
* @property {BitbucketRef} fromRef - the ref of the source of the pr
* @property {BitbucketRef} toRef - the ref of the destination of the pr
* @property {Object} links - http links
* @property {BitbucketLink[]} links.self - the array of links to this pr
*/
/**
* Generic Pull Request representation
*
* @typedef PullRequest
* @property {Number} number - the PR #
* @property {String} description - the description of the PR
* @property {String} url - the URL for the web interface of the PR
* @property {String} headCommitSha - SHA for the head commit of the incoming branch for the PR
*/
/**
* Generic Pull Request info (used for updating package.json and CHANGELOG.md files)
*
* @typedef PrInfo
* @property {String} scope - the scope of the PR
* @property {String} version - the new version after bumping based on scope
* @property {String} changelog - the changelog text
*/
/**
* A Promise that will be resolved with a PullRequest
*
* @typedef PrPromise
*/
/**
* Generic interface for a version control system (i.e. github.com)
*
* @interface Vcs
*/
/**
* Sometimes, based on the CI system, one might need to create a git remote to
* be able to push, this method provides a hook to do just that.
*
* @function
* @name Vcs#addRemoteForPush
* @return Promise - a promise resolved with the result of the git command
*/
/**
* Push local changes to the remote server
*
* @function
* @name Vcs#getPr
* @param {String} prNumber - the number of the pull request being fetched
* @return PrPromise - a promise resolved with a pull request object
*/
// ==========================================================================================================
// Continuous Integration
// ==========================================================================================================
/**
* Generic interface for a CI system (i.e. travis)
*
* @interface Ci
*/
/**
* Add changed files
*
* @function
* @name Ci#add
* @param {String[]} files - the files to add
* @returns {Promise} - a promise resolved with result of git commands
*/
/**
* Commit local changes
*
* @function
* @name Ci#commit
* @param {String} summary - the git commit summary
* @param {String} message - the detailed commit message
* @returns {Promise} - a promise resolved with result of git commands
*/
/**
* Push local changes to the remote server
*
* @function
* @name Ci#push
* @returns {Promise} - a promise resolved with result of git commands
*/
/**
* Setup the local git environment (make sure you're in a proper branch, with proper user attribution, etc
*
* @function
* @name Ci#setupGitEnv
* @returns {Promise} - a promise resolved with result of git commands
*/
/**
* Create a local tag
*
* @function
* @name Ci#tag
* @param {String} name - the name of the tag to create
* @returns {Promise} - a promise resolved with result of git commands
*/
|
13th. It would be neceffary to examine whether that pure calcareous ftone be fixed on the flate, as the calcareous fhelly ftone is j or whether it be interpofed in beds, or in veins among the flate, as it feems to be at Glan; or whether it forms a particular fyftem like the granite.
14th. Above the granite to the weft, at about two miles diftance from Oughterard, at a place called Lettercraft, there is a flate very like that at Glan, in which it was pretended a vein of lead was difcovered. We have in truth obferved fome quartz and argillaceous veins expofed by the current of the river ; but it is impoflible to fay any thing more of it at prefent. The pieces of lead which we carried from that fpot, came from the trials that have formerly been made there.
15th. On the banks of the river of Oughterard, both in the granite and calcareous parts, one may obferve an ochreous fediment or depofite, often very hard and thick ; which made people imagine that it was contiguous to fome iron mine : the ferruginous tafte of the little fountain which runs above the grotto of Calypfo ftrengthens this opinion ; but as the entire valley traverfed by the river of Oughterard is covered with turf to a very great depth, and as this bog or turf, being decompofed in the bofom of the marflies, muft communicate to the waters which traverfe it per-
|
Student's T-test for A\B testing of a mobile widget
I would like to run a t-Test (Two sampling assuming equal variances) in order to evaluate the lift observed in an A\B test of a mobile ad campaign. My main KPI is Revenue per 1000 views.
My data consist of the following dimensions: Date, Publisher, Group_name (the variation of the test) .
I have two questions:
1. Is it correct to have my t-test run on an aggregated pivot of the data, while calculating the average KPI per day? for example:
date
A
B
2019-02-23
2.64
3.37
2019-02-24
2.89
3.92
2019-02-25
3.70
5.21
2019-02-26
3.57
4.06
2019-02-27
2.78
3.86
2019-02-28
3.12
3.57
AVERAGE of RPM
3.12
4.00
Considering the underlying data has also Publisher level of details, I'm trying to figure out what Average should I use in the pivot - Weighted Average or Simple Average. Following the above example of the simple average, here's the pivot of weighted average:
date
A
B
2019-02-23
1.41
1.71
2019-02-24
1.27
1.54
2019-02-25
1.31
1.63
2019-02-26
1.46
1.58
2019-02-27
1.35
1.71
2019-02-28
2.15
2.33
AVERAGE of RPM
1.49
1.74
Which one, if any, is the correct method?
Thanks
EDIT:
More details regarding my design:
My product is a mobile widget which shows recommendations for other content on the internet, which could be either organic or promoted content. The Widget is embedded at the bottom of several publishers sites, and I generate revenue when customers click on any of the content. I have two possible setups for the widget - the current (Group A) - shows 1 organic recommendation and 2 promoted recommendations; and the new setup (Group B) shows 2 promoted recommendations and then 1 organic recommendation.
I now run an experiment and splitting my traffic equally and randomly between the two groups for 7 days.
After concluding the experiment, I'm calculating my Revenue per 1,000 page views (my KPI), and I noticed a lift of 17% in favor of Group B.
Trying to statistically test my results, I'm trying to run a Two-Sample Assuming Equal Variances T-test in Excel.
Question is, What array of values should I input to the excel in order to get my results? I now understand that aggregating the results by date is probably not the way, however, I cannot just test "Mean A" vs. "Mean B" in this test.
My raw data looks like this:
| date | publisher_id | platform | group_name | page_views | revenue | Revenue_per_1k_page_views |
|------------|--------------|----------|------------|------------|---------|---------------------------|
| 2019-02-23 | 106 | Mobile | A | 30,494 | 82.93 | 2.71 |
| 2019-02-23 | 106 | Mobile | B | 30,079 | 100.82 | 3.35 |
| 2019-02-24 | 106 | Mobile | A | 24,098 | 87.79 | 3.64 |
| 2019-02-24 | 106 | Mobile | B | 22,846 | 100.00 | 4.37 |
Why would you compute the KPI per day? Is there good reason to believe the effect is heterogenous between groups across days of the week?
I thought computing the KPI across days is necessary in order to plot the 2 distributions and calculate the variance.
The distribution and variance of what? If the AB test was properly randomized, and the intervention did not explicitly try to modulate the KPI on day of week, then doing this results in lower precision estimates. Can you explain the experimental design a little more? WHat was the intervention?
Thanks so much for your support. I have edited my post with further details. hope this clarifies my question.
do you only have information in this aggregated form?
Yes, see example at the end of my post
I'm going to get a little mathy here.
Let $y_{x, j, i}$ be the $i^{th}$ amount of revenue earned from a single click from a user in group $x$ on the $j$th day of the experiment. Your data presently consist of the quantities
$$ R_{x, j} = \sum_i^{n_{x,j}} y_{x, j.i}$$
where $n_{x,j}$ is the size of each arm on each day. Assuming the $y$ are iid, this we can apply the central limit theorem.
$$ R_{x,j} \sim \mathcal{N}(n_{x,j} \mu_x, n_{x, j}\sigma^2) $$
Where I have assumed here that only the means differ by group and not the variance.
We can use the revenue in a linear model to estimate the effect of the exposure in the following way. Let $z$ be a binary indicator variable for exposure to the treatment. The means can be modelled as
$$ R_{x, j}/n_{x, j} = \beta_0 + \beta_1 z + \epsilon $$
and weighted by the number of views. This can be done in R via
z = c(0, 1, 0, 1)
n = c(30494, 30079, 24098, 22846)
rv = c(82.93, 100.82, 87.79, 100)/n
model = lm(rv~z, weights = n)
summary(model)
summary(model)
Call:
lm(formula = rv ~ z, weights = n)
Weighted Residuals:
1 2 3 4
-0.07119 -0.07676 0.08008 0.08808
Coefficients:
Estimate Std. Error t value Pr(>|t|)
(Intercept) 0.0031272 0.0004797 6.518 0.0227 *
z 0.0006672 0.0006838 0.976 0.4321
---
Signif. codes:
0 ‘***’ 0.001 ‘**’ 0.01 ‘*’ 0.05 ‘.’ 0.1 ‘ ’ 1
Residual standard error: 0.1121 on 2 degrees of freedom
Multiple R-squared: 0.3225, Adjusted R-squared: -0.0162
F-statistic: 0.9522 on 1 and 2 DF, p-value: 0.4321
```
Is there supposed to be a difference in the indexing of $y_x,j,i$ and $y_x,i,j$ or is it just a typo?
@user1916067 Typo, corrected thanks
Thanks Demetri!
If the data you are showing in the table is all your data, I would suggest a simple approach - your KPI is higher for option B in every single group, so it is obviously better.
This is informally, a non-parametric test. If Group A and B were the same, you would expect A to win half the time and B to win half the time. In this case, B won all 6 times. This is equivalent to saying that you flipped a coin 6 times and got all 6 heads.
|
Mr.+Ball's+Writing+Group
Jenna, Kayleigh, Katie, Sydney, Tamsyn, Kyle, and Mike....This page is for YOU!
Here is a list of all the websites you might need to check through this project. This will grow.
1001 Middle School Home Our page
|
Saddle node bifurcation
Let $g_\mu:\mathbb R\to \mathbb R$ be a family of smooth maps with bifurcation parameter $\mu\in \mathbb R$. I want to show that
if $g_\mu^2$ has a saddle node bifurcation as $\mu$ passes through $\mu_*$ and $g^2_\mu$ has a unique fixed point $x_*$ at $\mu=\mu_*$, then the 2 fixed points of $g_\mu^2$ that emerge from the saddle-node bifurcation at $\mu_*$ must also be fixed points of $g_\mu$.
My idea:
For $\mu>\mu^*$, let $\{a,b\}\subset \mathbb R$ be the two distinct fixed points that emerge from the saddle-node bifurcation at $\mu_*$. Since $g_\mu^2(a)=a$ and $g^2_\mu(b)=b$, $\{a,b,g_\mu(a),g_\mu(b)\}$ are fixed points of $g_\mu^2$. By the fact that $P^*$ is the only fixed point of $g^2_\mu$ at $\mu=\mu^*$, we get that $g^2_\mu$ has only 2 distinct fixed points. In particular,
$$\{a,b,g_\mu(a),g_\mu(b)\}=\{a,b\} \quad \iff \quad g_\mu(a)= a\, \& g_\mu(b)= b \quad or \quad g_\mu(a)=b \, \& \, g_\mu(b)=a$$
I'm not complitely sure of why the case with $g_\mu(a)=b \, \& \, g_\mu(b)=a$ is not possible. Is something related to the smoothness of $g_\mu$ at $\mu=\mu^*$?
|
Talk:Prayer for Ukraine
Sheet music
The file shown at the top of the article has some mistakes (wrong slurs, wrong rhythm in bar 14). I have uploaded my on Commons. As a quite new user, I do not want to change the picture on my own. Thaddäus Rudolf (talk) 15:56, 8 March 2022 (UTC)
Literary translation by Dmytro Shostak
In the Lyrics section there is an English "Literary translation by Dmytro Shostak." Is there more information available somewhere as to who he is and when he did the translation? Is there a reference we can add? I've done a brief Google search but didn't find anything logical. papageno (talk) 02:31, 26 May 2023 (UTC)
* papageno, Dmytro Shostak in Ukrainian Wiki.
* first post translation on Facebook
* Dmytro Shostak in Facebook. --Микола Василечко (talk) 04:56, 26 May 2023 (UTC)
* Many thanks, Микола Василечко. --papageno (talk) 23:15, 27 May 2023 (UTC)
|
We present a novel coding-based technique for remote monitoring of passive
optical networks which exploits the wavelength-to-time mapping effect of
broadband short pulses in a highly dispersive medium. In this scheme, each
encoder consists in a single FBG written at the same central wavelength but
each one having a unique spectral bandwidth. The ultra-compactness and low-cost
of the encoders allow them to be potentially integrated inside the customers'
terminal. We experimentally demonstrate the feasibility of the proposed method
for the supervision of current and future high-density networks.
|
Talk:United Nations Space Command/@comment-11135771-20161012000512
The EAF would like to join the United Nations Space Coalition.
---
1. "Have you been, or are currently in the SSA?"
No.
2. "What celestial body does your head of government reside on?"
Enceladus.
3. "What kind of government is your state?"
Stratocratic Semi-Minarchic Parliamentary Republic.
4. "Who will be your representative?"
Fleet Admiral Miranda Atkins.
5. "Will you bring any advisors for your representative?"
Vice Admiral Marcus Derialt, Head of Military Research Adam Quinton.
6. "Will you accept the Credit (cR) for your currency?"
Yes.
|
Providing litigation, advocacy, and educational work in all areas of gay, lesbian, bisexual and transgender civil rights and the rights of people living with HIV, GLAD has a full-time legal staff and a network of cooperating attorneys across New England."
Directors
Accessed August 2007:
* Johanna Schulman, MBA, CFP, ChFC, President
* Peter E. Kassel, Vice President
* Rick McCarthy, Treasurer
* Renda Mott
Board Members
* Sandy Anderson
* David Brown
* Jo Davis
* Lisa J. Drapkin
* Peter J. Epstein
* Joanne Herman
* Wilbur Herrington
* Jane Hiscock
* Stefan Krug
* Chuck Latovich
* Navah Levine
* Marianne Monte
* Steven Patrick
* Jose Portuondo
* Dianne R. Phillips
|
Mongoose deep populate a virtual field
I have a schema structure that is '3 deep' and I find that I can't display information that is at the third level. I'm not sure if it's because this a virtual field, or if I'm doing something wrong.
The collections are programme>project>output. The programme schema looks up the projects like this....
const programmeSchema = new mongoose.Schema({
name: {
type: String,
},
projects:
[{ type: mongoose.Schema.ObjectId, ref: 'Project' }],
...
})
Which returns the project. My project schema (middle level) has a virtual field for the outputs collection (third level), like so....
projectSchema.virtual('outputs', {
ref: 'Output',
foreignField: 'project',
localField: '_id'
})
Which works fine when I find and display a single project. However, when I try and display the documents from the outputs collection at the programme (top) level, I can't do it. I've tried various different populates, such as.....
await Programme.findOne({ _id: req.params.id }).populate({
path: 'projects',
populate: {
path: 'outputs'
}
})
but I'm stumped. I've googled around but aside from one article that I struggled to follow, I can't find anything about this (deep populating a virtual field).
Please could someone tell me where I am going wrong?
I'm looking for the same. Did you find an answer?
@IvánSánchez this is what I did in the end:
let outputs = await Output.find({
project: {
$in: programme.projects.map(project => project._id)
}
})
|
import { ADD_MESSAGE, SET_CURRENT_USERID, ADD_HISTORY } from '../constants';
import { fromJS } from 'immutable';
const INITIAL_STATE = fromJS({
userID: 0,
messages: [],
lastMessageTimestamp: null,
});
function appReducer(state = INITIAL_STATE, action = {}) {
// Switch para definir quais ações e instruções serão passadas
switch (action.type) {
case SET_CURRENT_USERID:
return state.update('userID', () => action.payload);
case ADD_MESSAGE:
return state.update('messages', (messages) => messages.concat(action.payload));
case ADD_HISTORY:
return state
.update('messages', (messages) => messages.unshift(...action.payload.messages))
.update('lastMessageTimestamp', () => action.payload.timestamp);
default:
return state;
}
}
export default appReducer;
|
Fiction:New Dawn/An Honoruable Visit
Va'Si'La'Ko
Arrival=
Shrine to History=
The Magnificence of History=
The Arena
Aspirants=
Open Melee=
Blood, Scales And Sand=
|
[](https://github.com/strongback/strongback-cli/blob/master/LICENSE.txt)
[](https://travis-ci.org/strongback/strongback-cli)
[](https://gitter.im/strongback/users)
[](https://gitter.im/strongback/dev)
[](https://groups.google.com/forum/#!forum/strongback)
[](http://stackoverflow.com/questions/tagged/strongback)
Copyright Strongback Authors. Licensed under the [MIT License](https://github.com/strongback/strongback-cli/blob/master/LICENSE.txt).
## Strongback Command Line Interface (CLI)
[Strongback](http://strongback.org) is a Java library for FRC robots, and to use it you must first install the library onto your development machine and set it up properly. This can be tedious and somewhat complicated, so we created the Strongback Command Line Interface (CLI) tool. It's a small self-contained executable program for Linux, Windows, and MacOS that makes it easy to install, upgrade, and use the Strongback Java Library. It can:
* list the Strongback Java Library versions that are available
* install, upgrade, restore, or uninstall the Strongback Java Library version
* create a new Java project that uses Strongback
* decode a binary data file recorded by the Strongback library running on a robot
* show information about the installed Strongback and WPILib for Java
## Running the Strongback CLI
There are separate Strongback Command Line Interface (CLI) executables for these operating systems:
* Windows 32-bit (x86)
* Linux (64-bit x86)
* MacOS or OS X 10.7 and higher
### Windows
Look at the [latest releases](https://github.com/strongback/strongback-cli/releases) of this utility, and download the file that ends with `...-windows.zip` for the latest stable release. Extract the ZIP file's single `strongback.exe` file into any directory that is already included in or that [you can add to the `%PATH%` environment variable](http://www.howtogeek.com/118594/how-to-edit-your-system-path-for-easy-command-line-access/). We recommend your home directory, e.g., `C:\Users\<you>`.
After you've extracted the file and [added the directory to your `%PATH%`](http://www.howtogeek.com/118594/how-to-edit-your-system-path-for-easy-command-line-access/), open up a command window and run the following command from several different directories:
> strongback info
This will show you the installed versions of the Strongback Java Library and WPILib for Java library.
**NOTE:** If you are using the Git Bash terminal or any other Linux terminal emulator on Windows, you _must_ use `strongback.exe` rather than `strongback` everytime your run the Strongback CLI.
### Linux
The Strongback CLI tool can go anywhere _except your home directory_. We recommend a `bin` directory in your home account. To create the `bin` directory and add it to your path, use the following commands:
$ cd ~
$ mkdir -p ~/bin
$ echo "PATH=\${HOME}/bin:\${PATH}" >> ~/.bashrc
$ source ~/.bashrc
Then, use the following commands to download the `strongback` executable and place it into your `bin` directory, though be sure to replace both `1.2.2` sequences in the URL with the [latest version](https://github.com/strongback/strongback-cli/releases):
$ cd ~/bin
$ curl -L https://github.com/strongback/strongback-cli/releases/download/v1.2.2/strongback-cli-1.2.2-linux.tar.gz | tar -xvz
That's it! Open up a new terminal and run the following:
$ strongback info
This will show you the installed versions of the Strongback Java Library and WPILib for Java library.
### MacOS and OS X
The Strongback CLI tool can go anywhere _except your home directory_. We recommend a `bin` directory in your home account. To create the `bin` directory and add it to your path, use the following commands:
$ cd ~
$ mkdir -p ~/bin
$ echo "PATH=\${HOME}/bin:\${PATH}" >> ~/.bashrc
$ source ~/.bashrc
Then, use the following commands to download the `strongback` executable and place it into your `bin` directory, though be sure to replace both `1.2.2` sequences in the URL with the [latest version](https://github.com/strongback/strongback-cli/releases):
$ cd ~/bin
$ curl -L https://github.com/strongback/strongback-cli/releases/download/v1.2.2/strongback-cli-1.2.2-macos.tar.gz | tar -xvz
That's it! Open up a new terminal and run the following:
$ strongback info
This will show you the installed versions of the Strongback Java Library and WPILib for Java library.
## Viewing help
The Strongback CLI has built-in help, which you can see by running `strongback help` to display something like:
Usage:
strongback <command> [<args>]
Available commands include:
decode Converts a binary data/event log file to a readable CSV file
help Displays information about using this utility
info Displays the information about this utility and what's installed
install Install or upgrade the Strongback Java Library
new-project Creates a new project configured to use Strongback (only 1.x)
releases Display the available versions of the Strongback Java Library
version Display the currently installed version
uninstall Remove an existing Strongback Java Library installation
Additional help is available for each command with:
strongback help <command>
We've already seen the `info` command, and the `version` is similar but more concise. Let's look at several other commands.
## Installing or upgrading Strongback Java Library
The Strongback CLI makes it easy to list and install the available versions of the Strongback Java Library and to install any of these. Run the following command to list the available versions:
$ strongback releases
This will check the [Strongback releases](https://github.com/strongback/strongback-cli/releases) and output something similar to:
Found 10 releases of the Strongback Java Library:
1.1.7
1.1.6
1.1.5
1.1.3
1.1.2
1.1.1
1.1.0
1.0.3
1.0.2
1.0.1
To install one of these releases, simply run `strongback install <version>` and supply the desired version number (e.g., `strongback install 1.1.7`). Or, if you want the latest version, simply run `strongback install`. If you already have that version installed, the tool will simply tell you this and return. Otherwise, it will archive your existing version (if you have one installed) and then install the version you specified.
You can use this same command to restore a version that was installed previously, allowing you to easily switch between different installed versions. For example, imagine that you've recently installed version 1.1.6 but want to try 1.1.7. You can upgrade to 1.1.7 with `strongback install 1.1.7` and then later switch back to your previous 1.1.6 installation with `strongback install 1.1.6`. To use 1.1.7, simply run `strongback install 1.1.7` again.
Whenever you install a new version, the CLI will archive any previously installed version in the `~/strongback-archives` directory. Reinstalling one of these simply extracts that archive rather than downloading the archive from the [Strongback releases](https://github.com/strongback/strongback-cli/releases).
## Creating a new robot project
You can use the Strongback CLI tool to create a new iterative Java robot project for Eclipse set up to use Strongback, or update an existing Java robot project to use Strongback. Simply run open a terminal, change to the directory where you want the project created, and run the following command:
$ strongback new-project MyRobotProject
and replace `MyRobotProject` with the name of your project. This will not overwrite any of the existing files, so to do that add the `--overwrite` flag:
$ strongback new-project --overwrite MyRobotProject
By default, the Java package will be `org.frc<teamNumber>` where `<teamNumber>` is read from your WPILib for Java installation. If you want to use a different package, then supply the `--package <packageName>` flag. For example:
$ strongback new-project --package io.alphateam.robot MyRobotProject
See `strongback help new-project` for additional options.
## Decoding a robot data log
The Strongback Java Library has a _data recorder_ capable of recording various channels of data while your robot runs. The resulting data is captured in a binary file on the robot, so you need to download the file from the robot and then decode it. The Strongback CLI's `decode` command will convert the binary file into a _comma separated values_ (or CSV) file that you can import into Google Sheets, Excel, Tableau, or many other programs.
For example, imagine that you've set up your robot to use Strongback's data recorder to capture two channels, and you've named these channels `Foo` and `Bar`. The raw binary file will look something like the following (new lines and brackets added for clarity and are not part of the file format):
[l o g]
[3]
[4] [2] [2]
[4][T i m e] [3][F o o] [3][B a r]
[00 00 00 00] [00 52] [00 37]
[00 00 00 0A] [04 D5] [23 AF]
[00 00 00 14] [3F 00] [12 34]
[FF FF FF FF]
If this is in a file named `robot.dat` downloaded from the robot onto your computer, then the following Strongback CLI command will convert this binary file to a CSV file:
$ strongback decode robot.dat robot.csv
The CSV file will look like:
Time, Foo, Bar
0, 82, 55,
10, 1237, 9135,
20, 16128, 4660
The first row contains the comma-separated names of the channels, followed by a newline character. Each of the subsequent line lists the integer value of the data encoded to the precision specified in your robot program. The `Time` channel is always first and the values are in milliseconds.
## Uninstalling the Strongback Java Library
To uninstall the Strongback Java Library, simply run
$ strongback uninstall
and your existing installation (if you have one) will be archived.
## Uninstalling all of Strongback
To fully uninstall all of Strongback, including the archives of existing installations, run the following commands:
$ strongback uninstall --remove-archives
and then remove the `strongback` CLI tool.
|
How to determine what is the environment when bootstrap
What is the config that will determine which environment that it will point to when bootstrapping the app?
It always point to development while when I do sencha app build, it create the production folder in the build folder.
when calling sencha app build you can pass environment type like production, development, testing.
hi, thanks, yeah, i know that. but i just wondering when i just use sencha app build without any environment, what is the default? because weirdly, the generated html pointed to development while the code is built into production folder. I wonder is some of my settings wrong.
running sencha app watch generates development profile, running sencha app build generates production. to access generated production application you should navigate in a browser to /build/production/{app_name}, also sometimes maybe your development version will work correctly, but your production build may fail, in that case run sencha app build testing and navigate to /build/testing/{app_name} to check errors
|
DISCUSSION
Investigations of sound scattering of biological origin are being pursued for their bearing on studies of animal behaviour, distribution and ecology (Hersey and Moore, 1949; Moore, 1950), physiology (Kampa and Boden, 1954^/ 1954^) and on fisheries biology (Richardson, 1952; Haffner, 1952). Not all of the physical characteristics of those invertebrate organisms which cause scattering are understood as yet (Smith, 1951, 1954), but the air bladder in certain fish is regarded as an excellent scatterer of sound (Marshall, 1951; Hersey and Backus, 1954). The principles emerging from investigations into these various aspects of the subject may be generally applicable, but such principles are only to be derived from specific, detailed observations from many different localities. Scattering layer development may vary from one area to another. Some of the variation is attributable to the distributions of the different organisms which are able to effect the scattering. Moore (1950) has discussed such variations in scattering in relation to the distributions of several species of euphausiids in the north Atlantic. On the other hand, strong development of layers could result from those high concentrations of animals which may be associated with areas in which intermixing of contiguous bodies of water of differing properties is taking place. Thus localised scattering might well occur in the upwelling waters believed to be present at several localities about New Zealand (Garner, 1953). On a larger scale, scattering could be associated with the —possible— extensive disruption of the water layering and the resultant mixing of the waters where north-south moving masses cross the Chatham Rise (Fig. 1). This topographic barrier to unrestricted flow rises from about 2800 m. to within 450 m. of the surface and lies Fig. 8. Probable fish records combined with layers of plankton (on the left of the record). The latter are visible as three or four ascending layers cutting through the dense fish record; "Discovery II” record, D3.
|
/* eslint-disable complexity */
import axios from 'axios'
//Action Constants
const GET_CART = 'GET_CART'
const GET_GUESTCART = 'GET_GUESTCART'
const ADD_ITEM = 'ADD_ITEM'
const ADD_ITEM_GUEST = 'ADD_ITEM_GUEST'
const DELETE_ORDER = 'DELETE_ORDER'
const DELETE_GUEST_ORDER = 'DELETE_GUEST_ORDER'
const UPDATE_QUANTITY = 'UPDATE_QUANTITY'
const UPDATE_QUANTITY_GUEST = 'UPDATE_QUANTITY_GUEST'
const CHECKOUT_ORDER = 'CHECKOUT_ORDER'
//Action Creators
export const getCart = cart => {
return {
type: GET_CART,
cart
}
}
export const getGuestCart = cart => {
return {
type: GET_GUESTCART,
cart
}
}
export const addItem = cart => {
return {
type: ADD_ITEM,
cart
}
}
export const addItemGuest = cart => {
return {
type: ADD_ITEM_GUEST,
cart
}
}
export const deleteOrder = cart => {
return {
type: DELETE_ORDER,
cart
}
}
export const deleteGuestOrder = cart => {
return {
type: DELETE_GUEST_ORDER,
cart
}
}
export const updateQuantity = cart => {
return {
type: UPDATE_QUANTITY,
cart
}
}
export const updateQuantityGuest = cart => {
return {
type: UPDATE_QUANTITY_GUEST,
cart
}
}
export const getCheckout = cart => {
return {
type: CHECKOUT_ORDER,
cart
}
}
//Thunks
//Thunk for getting all user items in cart
export const fetchCart = () => {
return async dispatch => {
try {
const guestCart = JSON.parse(localStorage.getItem('cart'))
if (guestCart) {
const experienceIdArr = Object.keys(guestCart)
experienceIdArr.map(async experienceId => {
await axios.put(`/api/cart/${experienceId}`, {
packageQty: guestCart[experienceId]
})
})
window.localStorage.clear()
const {data} = await axios.get(`/api/cart`)
if (data) {
dispatch(getCart(data))
}
} else {
const {data} = await axios.get(`/api/cart`)
if (data) {
dispatch(getCart(data))
}
}
} catch (error) {
console.log(error)
}
}
}
//Thunk for getting guest cart
export const fetchGuestCart = () => {
return async dispatch => {
try {
let guestCart = JSON.parse(localStorage.getItem('cart'))
let experiences = []
for (let key in guestCart) {
if (guestCart.hasOwnProperty(key)) {
let {data} = await axios.get(`/api/experiences/${key}`)
data.orderDetail = {
packageQty: guestCart[key]
}
experiences.push(data)
}
}
dispatch(getGuestCart(experiences))
} catch (error) {
console.log(error)
}
}
}
//Thunk for adding an item in cart
export const addItemThunk = itemId => {
return async dispatch => {
try {
await axios.get('/api/cart')
const {data} = await axios.put(`/api/cart/${itemId}`)
dispatch(addItem(data))
} catch (error) {
console.log(error)
}
}
}
// thunk -- adding an item in guest cart
export const addItemForGuest = experienceId => {
return async dispatch => {
try {
let guestCart = JSON.parse(localStorage.getItem('cart'))
if (!guestCart) {
window.localStorage.setItem('cart', JSON.stringify({}))
guestCart = JSON.parse(localStorage.getItem('cart'))
guestCart[experienceId] = 1
window.localStorage.setItem('cart', JSON.stringify(guestCart))
} else {
guestCart[experienceId] = 1
window.localStorage.setItem('cart', JSON.stringify(guestCart))
}
let experiences = []
for (let key in guestCart) {
if (guestCart.hasOwnProperty(key)) {
let {data} = await axios.get(`/api/experiences/${key}`)
data.orderDetail = {
packageQty: guestCart[key]
}
experiences.push(data)
}
}
dispatch(addItemGuest(experiences))
} catch (error) {
console.log(error)
}
}
}
// thunk -- removing a guest order from guest cart
export const removeGuestOrder = experienceId => {
return async dispatch => {
try {
const guestCart = JSON.parse(localStorage.getItem('cart'))
delete guestCart[experienceId]
window.localStorage.setItem('cart', JSON.stringify(guestCart))
let experiences = []
for (let key in guestCart) {
if (guestCart.hasOwnProperty(key)) {
let {data} = await axios.get(`/api/experiences/${key}`)
data.orderDetail = {
packageQty: guestCart[key]
}
experiences.push(data)
}
}
dispatch(deleteGuestOrder(experiences))
} catch (error) {
console.log(error)
}
}
}
// thunk -- removing an order in cart
export const removeOrder = experienceId => {
return async dispatch => {
try {
const {data} = await axios.delete(`/api/cart/${experienceId}`)
dispatch(deleteOrder(data))
} catch (error) {
console.log(error)
}
}
}
//thunk -- increase qty for guest cart
export const increaseQtyGuest = experienceId => async dispatch => {
try {
const guestCart = JSON.parse(localStorage.getItem('cart'))
if (guestCart.hasOwnProperty(experienceId)) {
guestCart[experienceId]++
}
window.localStorage.setItem('cart', JSON.stringify(guestCart))
let experiences = []
for (let key in guestCart) {
if (guestCart.hasOwnProperty(key)) {
let {data} = await axios.get(`/api/experiences/${key}`)
data.orderDetail = {
packageQty: guestCart[key]
}
experiences.push(data)
}
}
dispatch(updateQuantityGuest(experiences))
} catch (error) {
console.log(error)
}
}
//thunk -- decrease qty for guest cart
export const decreaseQtyGuest = experienceId => async dispatch => {
try {
const guestCart = JSON.parse(localStorage.getItem('cart'))
if (guestCart.hasOwnProperty(experienceId)) {
guestCart[experienceId]--
}
window.localStorage.setItem('cart', JSON.stringify(guestCart))
let experiences = []
for (let key in guestCart) {
if (guestCart.hasOwnProperty(key)) {
let {data} = await axios.get(`/api/experiences/${key}`)
data.orderDetail = {
packageQty: guestCart[key]
}
experiences.push(data)
}
}
dispatch(updateQuantityGuest(experiences))
} catch (error) {
console.log(error)
}
}
// thunk -- increase qty
export const increaseQty = (orderId, expId) => async dispatch => {
try {
const {data} = await axios.put(`/api/cart/${expId}/increase`, {orderId})
dispatch(updateQuantity(data))
} catch (error) {
console.log(error)
}
}
// thunk -- decrease qty
export const decreaseQty = (orderId, expId) => async dispatch => {
try {
const {data} = await axios.put(`/api/cart/${expId}/decrease`, {orderId})
dispatch(updateQuantity(data))
} catch (error) {
console.log(error)
}
}
// thunk -- checking out
export const checkoutOrder = () => {
return async dispatch => {
try {
await axios.put('/api/cart/checkout')
dispatch(getCheckout())
} catch (error) {
console.log(error)
}
}
}
//initialState
const defaultCart = {
experiences: []
}
//Reducer
export default function(state = defaultCart, action) {
switch (action.type) {
case GET_CART:
return {...action.cart}
case GET_GUESTCART:
return {...state, experiences: [...action.cart]}
case ADD_ITEM:
return {
...action.cart
}
case ADD_ITEM_GUEST:
return {...state, experiences: [...action.cart]}
case DELETE_ORDER:
return {...action.cart}
case DELETE_GUEST_ORDER:
return {...state, experiences: [...action.cart]}
case UPDATE_QUANTITY:
return {...action.cart}
case UPDATE_QUANTITY_GUEST:
return {...state, experiences: [...action.cart]}
case CHECKOUT_ORDER:
return defaultCart
default:
return state
}
}
|
Metrics/Params selection dropdown
Fixes https://github.com/G-Research/fasttrackml/issues/864.
Hi Fabio, I have been testing this ticket and wanted to share some small issues I found:
I noticed that when we type something, and then press the left key (say we want to edit (loss|accuracy) to (epochs|accuracy)), the text in the search disappears, and an error shows on console:
When pressing the right arrow repeatedly, the original query is recovered. But this might be confusing for someone who uses, for example Ctrl+Shift+Left key to quickly change part of their query.
There's also a small typo on the "Invalid Regular Expression" popup. I would change it to simply "Invalid Regex" to preserve the look of the popup in smaller screen sizes (currently it covers up the input box when width < 1360px or so).
Hi Fabio, I have been testing this ticket and wanted to share some small issues I found:
I noticed that when we type something, and then press the left key (say we want to edit (loss|accuracy) to (epochs|accuracy)), the text in the search disappears, and an error shows on console:
When pressing the right arrow repeatedly, the original query is recovered. But this might be confusing for someone who uses, for example Ctrl+Shift+Left key to quickly change part of their query.
There's also a small typo on the "Invalid Regular Expression" popup. I would change it to simply "Invalid Regex" to preserve the look of the popup in smaller screen sizes (currently it covers up the input box when width < 1360px or so).
Hey! @jescalada thanks for the review, I changed the popup message,
for the error with the select all and the left arrow I see that this happens as well in the original aim, good catch!
I think we can maybe merge this and create another issue for that
|
ANGLING FOE OITANANICHE 81
to the lake. This, however, is not likel}', since trout quite resem bling those of Leven are found in many Northern lakes. The flesh is of a fine pink color, the eating admirable. During summer and autumn, when examined (and I have opened hundreds to ascertain the fact) the trout has its stomach filled with flies and insects, the ordinary food of the common river-trout; but, in addition, it is ofteu found to have been living on a small bucdnum, or fresh- water wbelk, with which the shallow waters of the lake abound."
This ouananiohe-like fish must not he confounded with another resident of Loch Leven — also distinct from the common river-trout — called by Dr. Knox the char-trout, and which lives on entomostraom, and comes into season in December, January, and February. The Loch Leven trout proper, like the ouananiche, resemble the salmon in their habits; for in autumn, or at the approach of winter, they leave the lake for the streams which feed it, returning, no doubt, early in spring. The splendid peculiarities of this near Scotch relative of the Canadian ouananiche were not unknown to Sir "Walter Scott, who introduces the sub ject of the Loch Leven trout in Chapter XXIY. of T/ie Abbot, in an ideal conversation between Queen Mary Stuart and Eoland Graeme, as follows :
"With the peculiar tact and delicacy which no woman possessed in greater perfection, she [Queen Mary] began to soothe by degrees the vexed spirit of the magnanimous attendant. The excellence of the fish he had taken in his expedition, the'high flavor and beau tiful red color of the trout which have long given distinction to the lalce, led her first to express her thanks to her attendant for so agreeable an addition to her table, especially upon a jour de jeune ; and thus brought on inquiries into the place where the fish had been taken, their size, their peculiarities, the times when tbey were in season, and a comparison between the Loch Leven trouts and those which are found in the rivers and lakes of the south of Scot-
|
<?php
namespace App\Http\Livewire;
use Livewire\Component;
use Illuminate\Support\Facades\View;
class UserManagement extends Component
{
public function __construct(){
View::share('newlinktitle', 'Create user');
View::share('newlink', 'dashboard');
}
public function render()
{
return view('livewire.user-management');
}
}
|
Identifying unused capacity in wireless networks
ABSTRACT
A method may include determining a capacity metric for sectors in a network, estimating a usage metric for each of the sectors for periods of time and determining a number of user devices that can access data services based on the capacity metric and the usage metric. The method may also include storing information identifying the determined number of user devices, receiving a request from a first user device for access to data services during a first period of time and accessing the stored information to determine whether the number of user devices that can access data services for the first period of time is greater than zero. The method may further include providing access via the wireless network to the first user device during the first period of time, in response to determining that the number of user devices that can access data services is greater than zero.
RELATED APPLICATION
The present application is a continuation of U.S. application Ser. No. 15/245,910 filed Aug. 24, 2016, the contents of which are hereby incorporated herein by reference in their entirety.
BACKGROUND INFORMATION
Wireless broadband network service providers typically provide a customer with a predetermined amount of data usage over a period of time, such as one month, based on the customer's data plan. If the customer exceeds the predetermined amount of data usage associated with his/her plan, the service provider will charge the customer a fee for the additional amount of data usage above the plan limit, based on parameters established by the customer's particular data plan. Such data service plans typically make a customer cautious in using high bandwidth applications (e.g., data streaming applications) to avoid exceeding his/her data plan limit.
BRIEF DESCRIPTION OF THE DRAWINGS
FIG. 1 illustrates an exemplary environment in which systems and methods described herein may be implemented;
FIG. 2 illustrates an exemplary configuration of components implemented in a portion of the network of FIG. 1;
FIG. 3 illustrates an exemplary configuration of logic components included in one or more of the devices of FIG. 1;
FIG. 4 illustrates an exemplary configuration of logic components implemented by one of the devices of FIG. 1;
FIG. 5 illustrates an exemplary configuration of logic components implemented in another one of the devices of FIG. 1;
FIG. 6 is a flow diagram illustrating processing by various components illustrated in FIG. 1 in accordance with an exemplary implementation;
FIG. 7 illustrates a mapping table generated in accordance with the processing of FIG. 6;
FIG. 8 is a flow diagram associated with requesting data services in accordance with an exemplary implementation; and
FIGS. 9A and 9B illustrate information displayed by the user device of FIG. 1 in accordance with an exemplary implementation.
DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS
The following detailed description refers to the accompanying drawings. The same reference numbers in different drawings may identify the same or similar elements. Also, the following detailed description does not limit the invention.
Implementations described herein relate to estimating network utilization during various periods of time based on historic and/or expected network usage. In one exemplary implementation, a service provider dynamically estimates future network usage and determines an expected excess network capacity during various future periods of time. The service provider may determine the expected excess network capacity on a per sector, cell or other level. The service provider may then offer slots of time for using the wireless service when excess network capacity is expected to exist. For example, the service provider may offer a certain number of users access to data service during time slots that otherwise would be unused. In some instances, the service provider may offer unlimited data access during the time slots that are available for free as a part of a bundled plan or for a per-slot charge, with the data usage during these time slots not counting against the customer's monthly plan limit.
When customers use the wireless service during time slots that would otherwise be unused, overall network utilization increases as a result of the increase in efficiency of the resource usage. For example, use of cell capacity and network capacity may be increased resulting in optimized cell and network capacity and bandwidth usage. In addition, having a more fully loaded or utilized network allows the service provider to more accurately determine full network capacity under actual conditions. For example, loading the network to full or near full capacity by using otherwise unused time slots may allow the service provider to determine how much data capacity/load the wireless network can actually handle, as opposed to a theoretical maximum load. In addition, monitoring the wireless network under fully or nearly fully loaded conditions may allow the service provider to identify locations where additional network resources are needed to ensure and/or improve network availability and reliability.
FIG. 1 is a block diagram of an exemplary environment 100 in which systems and methods described herein may be implemented. Environment 100 may include user devices 110-1 through 110-N, network support system (NSS) 120, service provider 130 and network 150.
User devices 110-1 through 110-N (individually referred to as user device 110-x or 110 and collectively as user devices 110) may include a mobile device, such as wireless or cellular telephone device (e.g., a conventional cell phone with data processing capabilities), a smart phone, a personal digital assistant (PDA) that can include a radiotelephone, etc. In another implementation, user devices 110 may include any type of mobile computer device or system, such as a personal computer (PC), a laptop, a tablet computer, a notebook, a netbook, a wearable computer (e.g., a wrist watch, eyeglasses, etc.), a game playing device, a music playing device, a home appliance device, a home monitoring device, etc., that may include communication functionality. User devices 110 may connect to network 150 and other devices in environment 100 (e.g., NSS 120, service provider 130, etc.) via any conventional technique, such as wired, wireless, optical connections or a combination of these techniques. User device 110 and the person associated with user device 110 (e.g., the party holding or using user device 110) may be referred to collectively as user device 110 in the description below.
NSS 120 may include one or more computing devices or systems used to estimate utilization of network 150. For example, NSS 120 may communicate with base stations, eNodeBs, gateways, specialized data monitoring devices, etc., to determine loading conditions on network 150. NSS 120 may also access historical data usage associated with network 150 during various times of day to estimate future network load conditions, such as whether excess capacity will be available during various time periods, as described in more detail below.
Service provider 130 may include one or more computer devices and systems associated with providing wireless services via network 150. For example, service provider 130 may store information regarding service plans for a large number of subscribers (also referred to herein as customers) and track data usage for each subscriber over a period of time (e.g., one month). Service provider 130 may communicate with NSS 120 to identify future time periods that may be offered to subscribers for data service, as described in more detail below.
Network 150 may include one or more wired, wireless and/or optical networks that are capable of receiving and transmitting data, voice and/or video signals. For example, network 150 may include one or more public switched telephone networks (PST Ns) or other type of switched network. Network 150 may also include one or more wireless networks and may include a number of transmission towers for receiving wireless signals and forwarding the wireless signals toward the intended destinations. Network 150 may further include one or more satellite networks, one or more packet switched networks, such as an Internet protocol (IP) based network, a local area network (LAN), a wide area network (WAN), a personal area network (PAN), a long term evolution (LTE) network, a WiFi network, a Bluetooth network, an intranet, the Internet, or another type of network that is capable of transmitting data. Network 150 provides wireless packet-switched services and wireless Internet protocol (IP) connectivity to user devices 110 to provide, for example, data, voice, and/or multimedia services.
The exemplary configuration illustrated in FIG. 1 is provided for simplicity. It should be understood that a typical network may include more or fewer devices than illustrated in FIG. 1. For example, environment 100 may include a large number (e.g., thousands or more) of user devices 110 and multiple NS Ss 120. In addition, network 150 may include additional elements, such as eNodeBs, base stations, switches, gateways, routers, monitoring devices, etc., that aid in routing data and collecting information regarding network conditions.
In addition, various functions are described below as being performed by particular components in environment 100. In other implementations, various functions described as being performed by one device may be performed by another device or multiple other devices, and/or various functions described as being performed by multiple devices may be combined and performed by a single device.
FIG. 2 is an exemplary block diagram illustrating a portion of network 150. In the implementation depicted in FIG. 2, network 150 is a long term evolution (LTE) network. It should be understood, however, that embodiments described herein may operate in other types of wireless networks, such as networks operating with other networking standards, such Global System for Mobile Communications (GSM), Universal Mobile Telecommunications System (UMTS), IS-2000, etc.
Network 150 may include an evolved packet core (ePC) that includes an evolved Node B (eNodeB) 220, mobile management entity (MME) 230, serving gateway (SGW) 240, packet gateway (PGW) 250, home subscriber server (HSS) 260 and policy and charging rules function (PCRF) 270. Eno deB 220 may be part of an evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (eU TRAN).
eNodeB 220 may include one or more devices and other components having functionality that allow user devices 110 to wirelessly connect to network 150. eNodeB 220 may be associated with one or more cells/sectors. For example, each cell or sector in network 150 may include one or more radio frequency (RF) transceivers pointed in a particular direction. In one implementation, some of the eNodeBs 220 may be associated with multiple sectors (e.g., 2, 3 or more) of network 150. In such an implementation, an eNodeB 220 may include multiple RF transceivers pointed in different directions to service different geographic areas. The term “sector” as used herein shall be broadly construed as any geographic area associated with an eNodeB, base station or other element of a radio network, and may be used interchangeably with the term “cell.” Each sector in network 150 may also be associated with multiple carriers. For example, an eNodeB 220 may include multiple radios that operate at different frequencies or different frequency bands in the same sector.
eNodeB 220 may interface with MME 230. MME 230 may include one or more devices that implement control plane processing for network 150. For example, MME 230 may implement tracking and paging procedures for user devices 110, may activate and deactivate bearers for user devices 110, may authenticate respective users of user devices 110, and may interface with non-LTE radio access networks. A bearer may represent a logical channel with particular quality of service (QoS) requirements, and can be used in some embodiments to control packet flows as described herein. MME 230 may also select a particular SGW 240 for a particular user device 110. MME 230 may interface with other MME devices (not shown) in network 150 and may send and receive information associated with user devices 110, which may allow one MME 230 to take over control plane processing of user devices 110 serviced by another MME 230, if the other MME 230 becomes unavailable.
SGW 240 may provide an access point to and from user devices 110, may handle forwarding of data packets for user devices 110, and may act as a local anchor point during handover procedures between eNodeBs 220. SGW 240 may interface with PGW 250. PGW 250 may function as a gateway to a core network, such as a wide area network (WAN) (not shown) that allows delivery of Internet protocol (IP) services to user devices 110.
HSS 260 may store information associated with user devices 110 and/or information associated with users of user devices 110. For example, HSS 260 may store user profiles that include authentication and access authorization information. Each user/subscription profile may include a list of user devices 110 associated with the subscriptions as well as an indication of which user devices 110 are active (e.g., authorized to connect to network 150).
PCRF 270 may implement policy charging and rule functions, such as providing quality of service (QoS) requirements, bandwidth and/or charges for a particular service for user devices 110. PCRF 270 may determine how a certain service data flow will be treated, and may ensure that user plane traffic mapping and treatment is in accordance with a user's subscription profile.
Although FIG. 2 shows exemplary components of network 150, in other implementations, network 150 may include fewer components, different components, differently arranged components, or additional components than depicted in FIG. 2. For example, network 150 may include a large number of eNodeBs 220, MMES 230, SG Ws 240, PG Ws 250 HS Ss 260 and PCR Fs 270. Additionally, or alternatively, one or more components of network 150 may perform functions described as being performed by one or more other components.
FIG. 3 illustrates an exemplary configuration of NSS 120. Other devices in environment 100, such as user device 110 and service provider 130 may be configured in a similar manner. Referring to FIG. 3, NSS 120 may include bus 310, processor 320, memory 330, input device 340, output device 350 and communication interface 360. Bus 310 may include a path that permits communication among the elements of NSS 120.
Processor 320 may include one or more processors, microprocessors, or processing logic that may interpret and execute instructions. Memory 330 may include a random access memory (RAM) or another type of dynamic storage device that may store information and instructions for execution by processor 320. Memory 330 may also include a read only memory (ROM) device or another type of static storage device that may store static information and instructions for use by processor 320. Memory 330 may further include a solid state drive (SDD). Memory 330 may also include a magnetic and/or optical recording medium (e.g., a hard disk) and its corresponding drive.
Input device 340 may include a mechanism that permits a user to input information to NSS 120, such as a keyboard, a keypad, a mouse, a pen, a microphone, a touch screen, voice recognition and/or biometric mechanisms, etc. Output device 350 may include a mechanism that outputs information to the user, including a display (e.g., a liquid crystal display (LCD)), a printer, a speaker, etc. In some implementations, a touch screen display may act as both an input device and an output device.
Communication interface 360 may include one or more transceivers that NSS 120 (or user device 110 or service provider 130) uses to communicate with other devices via wired, wireless or optical mechanisms. For example, communication interface 360 may include one or more radio frequency (RF) transmitters, receivers and/or transceivers and one or more antennas for transmitting and receiving RF data via network 150. Communication interface 360 may also include a modem or an Ethernet interface to a LAN or other mechanisms for communicating with elements in a network, such as network 150 or another network.
The exemplary configuration illustrated in FIG. 3 is provided for simplicity. It should be understood that NSS 120 (or user device 110 or service provider 130) may include more or fewer devices than illustrated in FIG. 3. In an exemplary implementation, NSS 120 (or user device 110 or service provider 130) perform operations in response to processor 320 executing sequences of instructions contained in a computer-readable medium, such as memory 330. A computer-readable medium may be defined as a physical or logical memory device. The software instructions may be read into memory 330 from another computer-readable medium (e.g., a hard disk drive (HDD), SSD, etc.), or from another device via communication interface 360. Alternatively, hard-wired circuitry may be used in place of or in combination with software instructions to implement processes consistent with the implementations described herein. Thus, implementations described herein are not limited to any specific combination of hardware circuitry and software.
FIG. 4 is an exemplary functional block diagram of components implemented in NSS 120. In an exemplary implementation, all or some of the components illustrated in FIG. 4 may be implemented by processor 320 executing software instructions stored in memory 330.
NSS 120 may include network monitoring logic 410, data capacity logic 420, database 430, time slot management logic 440 and communication logic 450. In alternative implementations, these components or a portion of these components may be located externally with respect to NSS 120.
Network monitoring logic 410 may include logic to identify data usage on network 150 during actual loading conditions in real time or near real time. In one implementation, network monitoring logic 410 may communicate with various gateways, eNodeBs and network monitoring devices located throughout network 150 to identify data usage on network 150. In addition, network monitoring logic 410 may identify total data traffic on a per sector basis. For example, network monitoring logic 410 may gather radio performance measurements from each sector site in network 150 over various periods of time. Network monitoring logic 410 may store this information in database 430.
Data capacity logic 420 may include logic to identify the capacity of each sector in network 150. In some instances, the capacity may vary over time. For example, based on addition of new equipment in a particular cell, the capacity may increase. Alternatively, if equipment is being serviced in a particular sector, the network capacity for that cell may decrease. The data capacity for a particular sector may also incorporate various metrics, such as cell bandwidth, spectral efficiency, propagation characteristics, etc. Data capacity logic 420 may store current capacity information in database 430.
Database 430 may includes one or more data storage devices that store one or more databases of information associated with network 150. For example, as described above, network monitoring logic 410 may store data usage information on a per sector level granularity in database 430. In addition, data capacity logic 420 may store data capacity information for network 150 on a per sector level granularity in database 430.
Time slot management logic 440 may include logic to determine the current or expected unused capacity of network 150 on a per sector basis at any given time or over a period of time. For example, time slot management logic 440 may estimate an amount of data capacity in each sector that is expected to be unused for each of a number of different future periods of times (also referred to herein as time slots). Time slot management logic 440 may determine if excess data capacity can and should be provisioned or offered to various customers, as described in more detail below.
Communication logic 450 may include logic to communicate with elements in environment 100 directly or via network 150. For example, communication logic 450 may provide alerts to customers or subscribers associated with service provider 130. For example, communication logic 450 may signal customers that time slots for data usage (e.g., streaming downloads) are available at particular periods of the time, as described in more detail below. Communication logic 450 may also provide information to service provider 130 regarding customers' usage of data.
Although FIG. 4 shows exemplary components of NSS 120, in other implementations, NSS 120 may include fewer components, different components, differently arranged components, or additional components than depicted in FIG. 4. In addition, functions described as being performed by one of the components in FIG. 4 may alternatively be performed by another one or more of the components of NSS 120.
FIG. 5 is an exemplary functional block diagram of components implemented in user device 110 of FIG. 1. Referring to FIG. 5, wireless data program 500 and its various logic components are shown in FIG. 5 as being included in user device 110. For example, wireless data program 500 may be stored in memory 330 of user device 110. In alternative implementations, these components or a portion of these components may be located externally with respect to user device 110.
Wireless data program 500 may be an application program associated with the user's data plan provided by service provider 130. Wireless data program 500 may include software instructions executed by processor 320 that allows a user associated with user device 110 to request data usage during particular periods of time, or receive alerts from NSS 120 and/or service provider 130 indicating that “unlimited” data is available during particular periods of time. In some implementations, service provider 130 may not track or count the additional data usage against the user's data plan limits and may allow for unlimited data usage during particular periods of time, as described in more detail below.
Wireless data program 500 may include user interface logic 510, communication logic 520 and display logic 530. User interface logic 510 may include logic to facilitate requesting or accepting use of data services via network 150. For example, user interface logic 510 may include a graphical user interface (GUI) that allows a user to input information requesting or accepting a particular time slot for network access and use. In addition, the GUI of user interface logic 510 may allow a user to input information responding to an offer for data usage, as described in detail below.
Communication logic 520 may include logic for communicating with other devices in environment 100. For example, communication logic 520 may transmit and/or receive information from NSS 120 and service provider 130 via network 150. As an example, communication logic 520 may allow user device 110 to request use of an available time slot for a data streaming session. As another example, communication logic 520 may allow user device 110 to receive offers from NSS 120 and/or service provider 130 regarding use of excess network capacity.
Display logic 530 may include logic to display information received from, for example, NSS 120 and service provider 130. In one exemplary implementation, display logic 530 may output information to output device 350 of user device 110, such as an LCD or another type of display. As an example, display logic 530 may display a message from NSS 120 or service provider 130 indicating that unlimited data usage is available for a current or future time period. In some implementations, display logic 530 may also display how much time is remaining in a current unlimited data usage session, as described in more detail below.
FIG. 6 is a flow diagram illustrating exemplary processing associated with determining available excess capacity in a wireless network, such as network 150. Processing may begin with NSS 120 estimating data volume (DV) capacity for sectors in network 150 (block 610). For example, data capacity logic 420 may determine the capacity of each sector in network 150 in megabytes per hour (MB/hour), megabits per second (Mb/s) or some other value. In some implementations, as described above, some of the eNodeBs 220 in network 150 may include multiple RF carriers per sector. In such implementations, data capacity logic 420 may determine the capacity for each carrier in each sector (referred to herein as a sector carrier). In addition, when estimating DV capacity in network 150, data capacity logic 420 may take into consideration underlying metrics associated with network 150, such as cell bandwidth, spectral efficiency, data propagation characteristics, etc. Data capacity logic 420 may store this information in database 430 (block 610).
NSS 120 may also estimate DV usage for each sector (block 620). For example, network monitoring logic 410 may estimate DV usage based on the actual usage of each sector and/or sector carrier in each sector over a predetermined number of time periods. In one implementation, network monitoring logic 410 may calculate DV usage as a percentage (e.g., 85%) of the actual usage on each sector carrier over the last N number of days in 15 minute time aggregation intervals, wherein N is any integer number (e.g., 1 day, 5 days, 7 days, etc.). It should also be understood that other time intervals may be used (e.g., 30 minute intervals, 60 minute intervals, etc.). In each case, network monitoring logic 410 estimates DV usage to capture local demand profile information for relatively short time intervals. Different systems may use different values for the aggregation intervals. Network monitoring logic 410 may store this information in database 430 (block 620).
NSS 120 may also calculate data throughput (TP) for each sector (block 630). For example, network monitoring logic 410 may calculate data TP for each sector carrier in each sector over each selected time interval (e.g., 15 minute intervals). Calculating TP accounts for typical cell load that is observed in the particular sector carrier in the particular time interval. In some implementations, target throughput may also be estimated based on usage for different types of data, such as a high definition (HD) video stream. The target TP may be useful when the available capacity on a sector exceeds what is required to support applications, such as HD video streaming.
NSS 120 may further estimate active user (AU) capacity for each sector (block 640). For example, data capacity logic 420 may determine the number of users that can be active for each sector carrier of network 150 during each selected period of time, also referred to herein as transmission time interval (TTI) or time window. When estimating AU capacity in network 150, data capacity logic 420 may take into consideration underlying metrics associated with network 150, such as cell bandwidth, spectral efficiency, data propagation characteristics, etc.
NSS 120 may also calculate an average active user usage (AUUsg) value for each sector (block 640). For example, network monitoring logic 410 may estimate the average active user usage based on a percentage of the actual usage of each sector carrier over the last N days in each T minute time window. In one implementation, network monitoring logic 410 may estimate the average active user usage as about 85% of the actual active user usage for each sector carrier over the last N days in each T minute time window. Estimation of active user usage captures usage profile and demand that is observed in the particular sector carrier in the particular time interval. In alternative implementations, other percentages may be used (e.g., average plus one standard deviation, average plus two standard deviations, etc.).
NSS 120 may then calculate the number of additional user devices that can be supported in each sector in each time window (block 650). For example, the additional number of user devices Z, where Z is an integer value, may correspond to the number of user devices that can access a particular sector/carrier above the number of user devices that are expected to use that sector/carrier in network 150 during a particular period of time. In other words, the number Z may correspond to additional time slots of data usage that are expected to be unused based on historical data usage. In one implementation, time slot management logic 440 may calculate Z using equation 1 below. Z=Max[0,Floor(MIN((DV capacity−DV usage)/(C*TP),AU capacity−AU usage))] Equation 1 That is, time slot management logic 440 may calculate a number of users Z that can be supported by each sector carrier as the maximum of zero and a variable “Floor” in equation 1, corresponding to the minimum of the value calculated by subtracting DV usage from DV capacity and dividing the result by a constant “C” multiplied by the throughput (TP), and the value calculated by subtracting AU usage from AU capacity. In one implementation, the constant C in equation 1 is a value associated with converting Megabits per second into Megabytes per hours and is equal to the value 450. For example, C in equation 1 (which is multiplied by TP in the denominator of the first value from which the minimum value (i.e., NIN) is selected) may correspond to converting Megabits/second into Megabytes/hour and in one implementation is equal to 3600 seconds/hour divided by 8 bits/byte, which is equal to 450. Time slot management logic 440 may then take the maximum of zero and the minimum of the two values calculated for the variable “Floor” in equation 1. Time slot management logic 440 may repeat this calculation for each sector carrier for each period of time. NSS 120 uses the calculated Z values to populate a mapping table that identifies the number of slots for each interval of time that are available for use in each sector (block 660).
FIG. 7 illustrates mapping table 700, which includes eNodeB field 710, sector field 720, carrier field 730 and time window field 740. Mapping table 700 may be stored in database 430. eNodeB field 710 identifies various eNodeBs 220 in network 150. Sector field 720 identifies various sectors served by the corresponding eNodeBs 220. Each eNodeB 220 may service more than one sector (e.g., three or more sectors) in network 150, as illustrated in FIG. 7. For example eNodeB 210001 services the sectors, designated as sectors 1, 2 and 3. Carrier field 730 identifies a particular RF carrier associated with an eNodeB 220. For example, as described above, each eNodeB 220 may include multiple radios that operate at different frequencies or different frequency bands within the same sector. For example, eNodeB 210002 in sector 1 includes two sector carriers, designated as carriers 1 and 2.
Time window field 740 (also referred to herein as time slots field 740) includes a number of 15 minute intervals of time throughout the day (a portion of which are illustrated in table 700). The values in the entries in time window field 740 correspond to the Z values calculated in accordance with Equation 1 above, and identify the number of available time slots which are expected to be unused and available for customers' use within each time window 740. For example, in entry 702-1, which corresponds to eNodeB 210001, sector 1, carrier 1, there is one time window available for the time period 1:00-1:15, three time windows available for the time period 1:15-1:30, five time windows available for the time period 1:30-1:45, etc., as indicated in time window field 740 for entry 702-1. Time slots granted to user devices 110 may encompass multiple consecutive time windows, subject to availability in successive time windows.
Service provider 130 may make the identified time slots available to customers. For example, in one implementation, customers may request time slots via wireless data program 500. In some instances, a user may request a time slot and NSS 120 may process the request on a first come, first served basis. In other instances, NSS 120 and/or service provider 130 may advertise the availability of the time slots to customers based on the customers' historic usage patterns and/or geographic locations. For example, NSS 120 and/or service provider 130 may access historic data usage indicating that a particular customer uses large amounts of data at a particular location and/or at a particular time of day (e.g., at home between 8:00 PM and 9:00 PM). In this case, NSS 120 may send an offer to user device 110 associated with that particular customer indicating that unlimited data usage is available for that period of time at that particular customer's geographic location.
As described above, in some implementations, data usage during the time slots illustrated in mapping table 700 may correspond to an unlimited amount of data usage during that period of time. In addition, service provider 130 may not count or track usage corresponding to the requested time slots against the customers' data plan limits. For example, in one implementation, if a customer associated with user device 110-1 requests a time slot serviced by eNodeB, sector 1 at 1:15-1:30 and NSS 120 grants the request, service provider 130 will not count data usage during this time slot against the customer's monthly allotment. In some instances, service provider 130 may make an offer to the customer for the unlimited data usage during the time slot. In some instances, service provider 130 may charge the customer a relatively low fee for the unlimited data usage during the requested time slot (e.g., $1 or less for a one hour data session). In another instance, service provider 130 may offer the customer an option to view or evaluate certain content in exchange for the unlimited data usage during the requested time slot. This allows service provider 130 to more fully and efficiently utilize network capacity. As a result, overall network utilization increases. In addition, having a more fully loaded or utilized network allows service provider 130 to more accurately determine full network capacity under actual conditions, as opposed to a theoretical maximum capacity. In addition, monitoring network 150 under fully or nearly fully loaded conditions may allow service provider 130 to identify locations where additional network resources (e.g., eNodeBs, gateways, routers, etc.,) are needed to ensure or increase network availability and reliability.
NSS 120 may refresh mapping table at predetermined periods of time (block 670). For example, NSS 120 may update mapping table daily, weekly, monthly, etc. In each case, mapping table 700 stores information identifying time periods in which excess network capacity is expected to exist. In addition, mapping table 700 may be regenerated to account for updated historical usage information. However, the refreshing or updating of mapping table 700 may exclude traffic volume changes associated with usage attributed to excess capacity in the time slots associated with mapping table 700 during the previous period of time.
FIG. 8 is a flow diagram illustrating processing associated with requesting time slots in network 150. Processing may begin with a user associated with user device 110 launching or accessing wireless data program 500. The user of user device 110 may then provide input requesting a time slot of a certain duration beginning at a certain time (block 810). For example, the user, via a GUI provided by user interface logic 510, may request a particular time slot for streaming data (e.g., watch a live sporting event, download a movie, listen to music, etc.). Communication logic 520 may forward the request to NSS 120. The request from user device 110 may include a cell ID identifying the cell to which user device 110 is currently connected. The request from user device 110 may also include the duration of the request (e.g., 30 minutes, 40 minutes, etc.). In alternative implementations, after wireless data program 500 is launched, communication logic 520 may signal NSS 120 requesting information identifying available time slots for accessing network 150. In response, communication logic 450 of NSS 120 may forward information to user device 110 indicating the available time slots.
Assume that user device 110 has transmitted a request for a time slot of a certain duration to NSS 120. NSS 120 receives the request and may store the request in a first in, first out (FIFO) queue for incoming requests. NSS 120 may pull each request from the FIFO queue in sequence and process the request. NSS 120 may identify cell information from the request, such as the cell/sector identifier (ID) and a sector carrier on which the request was received, and also identify the duration of the request (block 820). NSS 120 then queries table 700 using the sector ID, sector carrier and the duration of the request to determine if the requested time slot duration is available (block 830). That is, NSS 120 compares the requested duration to the maximum consecutive 15 minutes slots that are available in the particular sector and carrier. If an adequate number of time slots in the appropriate sector with the appropriate carrier are available to fulfill the request, NSS 120 provisions the time slot to user device 110 (block 840).
For example, assume that a user device 110 attached to eNodeB 210002, sector 1 and communicating via sector carrier 2, requests a 45 minutes time slot at 1:05. Referring to table 700, time window field 740 for time period 1:30-1:45 in entry 702-5 indicates that zero time slots are available from 1:30-1:45 (i.e., no time slot is available). In some implementations, NSS 120 may grant user device 110 a partial time slot, such as a time slot from only 1:05-1:30, since no time slots are available from 1:30-1:45 (block 850). In other implementations, if the full time period is not available (block 830—no), time slot management logic 440 may identify an alternative time slot in which the full time period is available (block 850). For example, time slot management logic 440 may identify time slots from 1:45 through 2:30 as being available since each of those time periods has values greater than zero. Time slot management logic 440 may offer those time slots to the user. In other implementations, NSS 120 may signal user device 110 that the requested time slot is not available.
Assume that the time slot, a partial time slot or an alternative time slot was granted to user device 110. NSS 120 may send user device 110 a message indicating that the time slot has been granted for unlimited data usage during the granted time slot. User device 110 may receive the message from NSS 120 and display logic 530 of wireless data program 500 may output the message. For example, referring to FIG. 9A, user device 110, corresponding to a smart phone device in this example, may display message 910 via an output screen of user device 110. The message may indicate “unlimited data session available for 25 minutes,” as illustrated in FIG. 9A. In this scenario, after provisioning the 1:05-1:30 time slot, NSS 120 subtracts one time slot from each of the entries for the 1:00-1:15 time window and the 1:15-1:30 time window in entry 702-5 shown in mapping table 700 to ensure that mapping table 700 includes an accurate count of available time slots.
As another example, assume that a user attached to eNodeB 210055, sector 3 via carrier 1 requests a 30 minute time slot at 1:30. NSS 120 checks table 700 and determines that time slots in entry 702-12 (corresponding to eNodeB 210055, sector 3, carrier 1) are available from 1:30 through 2:30. In this case, NSS 120 may offer additional time slots beyond the requested 30 minute time slot at an incremental cost. For example, NSS 120 may provision the 30 minute time slot from 1:30-2:00 and offer the user the time slot between 2:00 and 2:30 for an additional small fee or in exchange for the customer agreeing to receive content from service provider 130. In either case, when NSS 120 provisions the 30 minute time slot, time slot management logic 440 subtracts one from each appropriate time slot (i.e., time slot 1:30-1:45 and 1:45-2:00) in entry 702-12. If, however, the user chooses the additional 30 minute time slot (i.e., from 2:00-2:30), time slot management logic 440 subtracts one from each additional time slot (i.e., 2:00-2:15 and 2:15-2:30) in entry 702-12.
In some implementations, NSS 120 may identify that a time slot associated with a granted user session is coming to an end (block 860). In this case, NSS 120 may send a message to user device 110 indicating that a current session is coming to an end (block 860). For example, in some instances NSS 120 may send a message to user device 110 a short period of time (e.g., 5 minutes) prior to the ending of a data session. User device 110 may receive the message and output the message to the user, as illustrated in FIG. 9B. Referring to FIG. 9B, user device 110 may display message 920 indicating that “unlimited data session is ending in 5 minutes,” and query whether the user would like to continue the unlimited data session. For example, the message may be “do you want to continue the unlimited data session for another 30 minutes?” In this manner, NSS 120 may provide the user with additional opportunities to access unlimited data usage via network 150.
As described above, NSS 120 may provision requests from user devices 110 on a first come, first served in basis. In other implementations, NSS 120 may account for user mobility in granting slots. For example, in some implementations, NSS 120 may check mapping table 700 for the availability of time slots in the sector to which a user device is currently attached and to sectors within a predetermined radius (e.g., 5 miles, 10 miles, 30 miles, etc.) of the user's current sector. That is, NSS 120 may check mapping table for available time slots within a distance or radius of the current sector in case the user moves to a new location outside the original sector. In this case, NSS 120 checks for availability in geographically adjacent sectors within the predetermined distance or radius. In some implementations, NSS 120 may make sure that time slots are available in the geographically adjacent sectors prior to determining whether to grant a customer's request for an unlimited data session.
In some implementations, NSS 120 may also check whether time slots associated with particular carrier frequencies are available in neighboring sectors prior to granting a time slot. This also accounts for user mobility over time. Still further, in some implementations, features such as carrier aggregation may be disabled when accessing available time slots. For example, carrier aggregation may aggregate multiple bands on a user device 110 simultaneously, such that a user device 110 can use, for example, a 700 Megahertz (MHz) band and another advanced wireless services (AWS) band simultaneously for downloads. In this case, granting time slots to such a user device 110 may have more impact on network 150 than if carrier aggregation is not used. To mitigate such impact, carrier aggregation may be turned off/disabled when accessing time slots identified in mapping table 700. In another alternative implementation, if a device is known to be carrier aggregation capable, then the number of slots for both carriers can be reduced by one when a request/session is granted.
In addition, in some implementations, NSS 120 and/or service provider 130 may account for time and/or location restrictions in allotting time slots via mapping table 700. For example, NSS 120 may exclude certain areas in a city (e.g., a busy downtown business district) during working hours (e.g., 9:00 AM to 5:00 PM), or a sports stadium during a sporting event from mapping table 700. That is, time slot management logic 440 may reduce the number of available time slots (e.g., to a small number or zero) in an area that is expected to be crowded with user devices 110 that are expected to fully load network 150 during those time periods. Advance information from various systems, such as sports/concert ticketing systems, provided through application programming interfaces (APIs) may be used to determine the expected number of users at a particular location during a period of time.
As described above, time slot management logic 440 may process requests from user devices 110 on a first come, first served basis. In other implementations, NSS 120 may grant time slots to user devices that would cause less impact on overall processing throughput. For example, NSS 120 may make radio frequency (RF) power measurements, such as received signal received power (RSRP) measurements, to determine an approximate location of user device 110 based on the RSRP associated with a request. In this case, time slot management logic 440 may favor a user device 110 that has a greater RSRP value, indicating that the user is closer to the center of the sector. As a result, such a user is expected to have less impact on spectrum resources per megabyte volume than a user located on an edge portion or outer area of a sector. In this implementation, NSS 120 gives preferences to user device 110 that has less impact on overall network efficiency.
In addition, in some implementations, network 150 may support multiple scheduler classes of service. That is, traffic can be assigned to different quality of service (QoS) classes. In this case, NSS 120 may favor classes of service that will have less impact on network 150, thereby mitigating impact on other types of expected traffic.
Implementations described herein provide for estimating unused capacity on a network. The unused capacity may then be offered to customers during relatively short intervals of time. In some instances, the unused capacity may be offered as unlimited data usage over the granted periods of time and the amount of data usage during these time periods will not count against a customer's monthly data plan allotment. In some instances, the “extra” data usage will be charged to the customer at a relatively low rate, as compared to the customer's charges for data usage via the customer's regular data plan. In other instances, the extra data may be provided in exchange for the user agreeing to receive, view and/or rank content provided by the service provider or another third party.
The foregoing description of exemplary implementations provides illustration and description, but is not intended to be exhaustive or to limit the embodiments to the precise form disclosed. Modifications and variations are possible in light of the above teachings or may be acquired from practice of the embodiments.
For example, features have been described above with respect to estimating a capacity metric and a usage metric to identify the number of available time slots. In other implementations, other metrics that account for the number of connections on an eNodeB, the physical resource block utilization (PRBU) or the transmission time interval utilization (TTIU) may be used to identify available unused capacity. In each case, historical data usage and estimated capacity may be used to estimate unused capacity for future periods of time. The unused capacity may then be offered to customers, resulting in a more fully loaded network. In addition, offering unused to capacity to customers for unlimited usage during various periods of time may increase the utilization of network 150 during traditionally off-peak hours. This off-peak usage may result in a less congested network during typical peak times, thereby resulting in increased data throughput on network 150 and increased customer satisfaction.
In addition, implementations described above refer to estimating data capacity associated with eNodeBs that support multiple sectors and multiple sector carriers. It should be understood that implementations described herein can be used with a network in which eNodeBs or cell sites support one sector and/or one carrier. Still further, implementations have been described herein as measuring data capacity and usage on a sector carrier level granularity. In other implementations, data capacity and usage could be measured/estimated on a higher or lower granularity (e.g., a sector level, a sub-carrier level, etc.).
Further, while series of acts have been described with respect to FIGS. 6 and 8, the order of the acts may be different in other implementations. Moreover, non-dependent acts may be implemented in parallel.
It will be apparent that various features described above may be implemented in many different forms of software, firmware, and hardware in the implementations illustrated in the figures. The actual software code or specialized control hardware used to implement the various features is not limiting. Thus, the operation and behavior of the features were described without reference to the specific software code—it being understood that one of ordinary skill in the art would be able to design software and control hardware to implement the various features based on the description herein.
Further, certain portions of the invention may be implemented as “logic” that performs one or more functions. This logic may include hardware, such as one or more processors, microprocessor, application specific integrated circuits, field programmable gate arrays or other processing logic, software, or a combination of hardware and software.
In the preceding specification, various preferred embodiments have been described with reference to the accompanying drawings. It will, however, be evident that various modifications and changes may be made thereto, and additional embodiments may be implemented, without departing from the broader scope of the invention as set forth in the claims that follow. The specification and drawings are accordingly to be regarded in an illustrative rather than restrictive sense.
No element, act, or instruction used in the description of the present application should be construed as critical or essential to the invention unless explicitly described as such. Also, as used herein, the article “a” is intended to include one or more items. Further, the phrase “based on” is intended to mean “based, at least in part, on” unless explicitly stated otherwise.
What is claimed is:
1. A computer-implemented method, comprising: estimating unused data capacity on a wireless network associated with at least one carrier in each of a plurality of sectors for each of a plurality of periods of time; storing information identifying the estimated unused data capacity for each of the at least one carrier in each of the plurality of sectors for each of the plurality of periods of time; receiving a request from a first user device for access to data services during a first one of the plurality of periods of time, wherein the first user device is associated with a first carrier and a first sector of the plurality of sectors; accessing the stored information to determine whether the unused data capacity via the first carrier in the first sector for the first period of time is available; and providing access to data services via the wireless network to the first user device during the first period of time, in response to determining that the unused data capacity via the first carrier in the first sector for the first period of time is available.
2. The computer-implemented method of claim 1, wherein the estimating unused data capacity comprises: determining at least one capacity metric for each of the at least one carrier associated with each of the plurality of sectors in the wireless network, estimating at least one usage metric for each of the at least one carrier associated with each of the plurality of sectors for each of the plurality of periods of time, and determining a number of user devices that can access data services via each of the at least one carrier in each of the plurality of sectors for each of the plurality of periods of time, based on the at least one capacity metric and the at least one usage metric.
3. The computer-implemented method of claim 1, wherein the estimating unused data capacity comprises: determining an active user capacity value identifying a maximum number of user devices that can simultaneously access data services for each of the at least one carrier associated with each of the plurality of sectors in the wireless network, determining an active user usage value identifying an estimated number of active user devices that are expected to simultaneously access data services for each of the at least one carrier associated with each of the plurality of sectors in the wireless network, and determining, based on the active user capacity value and the active user usage value, a number of user devices that can access data services via each of the at least one carrier in each of the plurality of sectors for each of the plurality of periods of time.
4. The computer-implemented method of claim 1, wherein the storing information identifying the estimated unused data capacity comprises storing the information in a mapping table, the method further comprising: updating the mapping table at predetermined times based on actual usage information for the wireless network; and decrementing, in the mapping table, the unused data capacity for the first carrier in the first sector for a time window corresponding to the first period of time in response to providing access to data services to the first user device during the first period of time.
5. The computer-implemented method of claim 1, wherein the first user device is associated with a first customer having a data plan, the method further comprising: excluding data usage by the first user device during the first period of time from being applied against a data limit associated with the data plan.
6. The computer-implemented method of claim 1, further comprising: receiving a second request from a second user device for access to data services during a second period of time, wherein the second user device is associated with a second carrier in a second sector of the wireless network; accessing the stored information to determine whether the unused data capacity via the second carrier in each of the second sector and at least one sector that is located geographically adjacent to the second sector is available; and providing access to data services to the second user device during the second period of time in response to determining that the unused data capacity via the second carrier in each of the second sector and the at least one geographically adjacent sector for the second period of time is available.
7. The computer-implemented method of claim 1, further comprising: receiving a second request from a second user device and a third request from a third user device for access to data services during a second period of time, wherein each of the second user device and the third user device is associated with a second sector in the wireless network; and favoring or providing priority to one of the first user device or the second user device with respect to granting either the second request or the third request based on at least one of power measurements associated with signals received via the first user device and the second user device or class of service associated with the second request and the third request.
8. The computer-implemented method of claim 1, wherein the storing information identifying the estimated unused data capacity comprises: storing information in a mapping table, wherein the mapping table identifies a number of user devices in each of the plurality of sectors, for each of the plurality of periods of time, that are expected to be available for use based on historical data usage information.
9. The computer-implemented method of claim 1, further comprising: identifying data usage patterns associated with a second user device, wherein the second user device is associated with a customer of a service provider associated with the wireless network; sending, to the second user device and based on the identified data usage patterns, an offer for unlimited data usage via the wireless network during a second one of the plurality of periods of time; receiving, from the second user device, an acceptance of the offer; and excluding data usage by the second user device during the second period of time from being applied against a data limit associated with a data plan of the customer.
10. The computer-implemented method of claim 9, further comprising: sending, to the second user device, a message indicating that the second period of time is ending in a predetermined period of time and querying whether a user associated with the second user device would like to continue receiving unlimited data usage for a third period of time.
11. The computer-implemented method of claim 1, further comprising: providing, to the first user device, an offer for data services for a period of time other than the first period of time, in response to determining that unused data capacity via the first carrier in the first sector for the first period of time is not available.
12. A system, comprising: a memory; and at least one device configured to: estimate unused data capacity on a wireless network associated with at least one carrier in each of a plurality of sectors for each of a plurality of periods of time, store information identifying the estimated unused data capacity for each of the at least one carrier in each of the plurality of sectors for each of the plurality of periods of time, receive a request from a first user device for access to data services during a first one of the plurality of periods of time, wherein the first user device is associated with a first carrier and a first sector of the plurality of sectors, access the stored information to determine whether the unused data capacity via the first carrier in the first sector for the first period of time is available, and provide access to data services via the wireless network to the first user device during the first period of time, in response to determining that the unused data capacity via the first carrier in the first sector for the first period of time is available.
13. The system of claim 12, wherein when estimating unused data capacity, the at least one device is configured to: determine at least one capacity metric for each of the at least one carrier associated with each of the plurality of sectors in the wireless network, estimate at least one usage metric for each of the at least one carrier associated with each of the plurality of sectors for each of the plurality of periods of time, and determine a number of user devices that can access data services via each of the at least one carrier in each of the plurality of sectors for each of the plurality of periods of time, based on the at least one capacity metric and the at least one usage metric.
14. The system of claim 12, wherein when estimating unused data capacity, the at least one device is configured to: determine an active user capacity value identifying a maximum number of user devices that can simultaneously access data services for each of the at least one carrier associated with each of the plurality of sectors in the wireless network, determine an active user usage value identifying an estimated number of active user devices that are expected to simultaneously access data services for each of the at least one carrier associated with each of the plurality of sectors in the wireless network, and determine, based on the active user capacity value and the active user usage value, a number of user devices that can access data services via each of the at least one carrier in each of the plurality of sectors for each of the plurality of periods of time.
15. The system of claim 12, wherein the first user device is associated with a first customer having a data plan, and wherein the at least one device is further configured to: exclude data usage by the first user device during the first period of time from being applied against a data limit associated with the data plan.
16. The system of claim 12, wherein the at least one device is further configured to: identify data usage patterns associated with a second user device, wherein the second user device is associated with a customer of a service provider associated with the wireless network, and send, to the second user device and based on the identified data usage patterns, an offer for unlimited data usage via the wireless network during a second one of the plurality of periods of time.
17. The system of claim 12, wherein the at least one device is further configured to: provide, to the first user device, an offer for data services for a period of time other than the first period of time, in response to determining that unused data capacity via the first carrier in the first sector for the first period of time is not available.
18. A non-transitory computer-readable medium having stored thereon sequences of instructions which, when executed by at least one processor, cause the at least one processor to: estimate unused data capacity on a wireless network associated with at least one carrier in each of a plurality of sectors for each of a plurality of periods of time; store information identifying the estimated unused data capacity for each of the at least one carrier in each of the plurality of sectors for each of the plurality of periods of time; receive a request from a first user device for access to data services during a first one of the plurality of periods of time, wherein the first user device is associated with a first carrier and a first sector of the plurality of sectors; access the stored information to determine whether the unused data capacity via the first carrier in the first sector for the first period of time is available; and provide access to data services via the wireless network to the first user device during the first period of time, in response to determining that the unused data capacity via the first carrier in the first sector for the first period of time is available.
19. The non-transitory computer-readable medium of claim 18, wherein the first user device is associated with a first customer having a data plan, and wherein the instructions further cause the at least one processor to exclude data usage by the first user device during the first period of time from being applied against a data limit associated with the data plan.
20. The non-transitory computer-readable medium of 18, wherein the instructions further cause the at least one processor to: identify data usage patterns associated with a second user device, wherein the second user device is associated with a customer of a service provider associated with the wireless network; and send, to the second user device and based on the identified data usage patterns, an offer for unlimited data usage via the wireless network during a second one of the plurality of periods of time.
|
In this paper, we adapt Recurrent Neural Networks with Stochastic Layers,
which are the state-of-the-art for generating text, music and speech, to the
problem of acoustic novelty detection. By integrating uncertainty into the
hidden states, this type of network is able to learn the distribution of
complex sequences. Because the learned distribution can be calculated
explicitly in terms of probability, we can evaluate how likely an observation
is then detect low-probability events as novel. The model is robust, highly
unsupervised, end-to-end and requires minimum preprocessing, feature
engineering or hyperparameter tuning. An experiment on a benchmark dataset
shows that our model outperforms the state-of-the-art acoustic novelty
detectors.
|
User:Spinfx
Greetings
Hello all, Spinfx here.
Biomes saved (all have lakes unless mentioned otherwise):
- surface + forest (i.e. default)
- underground + forest (i.e. default)
- sky + forest (i.e. default); I didn't have to do anything, sky lakes are a thing now in v1.3
- surface + jungle
- underground + jungle
- surface + snow
- underground + snow
Quickstart Guide
Upgrading Advice
* can attack from a safe distance compared to using swords,
* and deals enough damage to prevent things from degenerating into a battle of attrition.
Before You Go
Getting Diggy With It
Other Games
* Age of Decadence - an interesting looking old-school RPG
* Legends of Eisenwald - I'm a sucker for SRPGs, this looks interesting
- Spinfx 16:15, 2 September 2012 (UTC)
- Spinfx 14:47, 3 September 2012 (UTC)
- Spinfx 05:56, 28 January 2013 (UTC)
- Spinfx 09:20, 13 October 2013 (UTC)
- Spinfx (talk) 15:01, 16 August 2015 (UTC)
- Spinfx (talk) 12:55, 18 August 2015 (UTC)
- Spinfx (talk) 02:48, 28 September 2015 (UTC)
|
1/1
9 files
SWINGS AND SCALES OF DEMOCRACY: THE “TRANSGENDER EPIDEMIC” AND RESISTANCE TO ANTIGENDERISM
dataset
posted on 2021-03-25, 09:19 authored by Rodrigo Borba, Danillo da Conceição Pereira Silva
ABSTRACT Brazilian democracy moves like a pendulum: from time to time its limits are expanded or retracted (Avritzer 2019). After a virulent dictatorial period, re-democratization was strengthened in the first decade of the 21st century. Public policies for the enfranchisement of the LGBT+ population were particularly important in this process. The rise of bolsonarism has been pushing the democratic pendulum back to its extreme opposite. This, however, does not go unchallenged. Against this backdrop, we analyze the online circulation of a poster for a lecture about a “transgender epidemic”, which was due to take place the Legislative Assembly of Porto Alegre in March 2020. Such textual disputes may help us reconceptualize the current state of Brazilian democracy as a friction between distinct scalar projects (Carr and Lempert, 2016). The textual trajectories we analyze suggest that the back and forth movement of democracy is not linear as Avritzer (2019) seems to assume. The illiberal retraction of recent years coexists with values forged in periods of democratic expansion, which explains the fact that the lecture was canceled due to online protests. Such resistance suggests that de-democratizing scalar projects are neither homogeneous nor totalizing, which allows new political collectivities to contest attempts to disenfranchise them.
History
|
fix: CoordinationTask doesn't reschedule itself when token release claim fails
Steps to reproduce
When using a RDBMS as Event Store/Bus and Token Store, and the database goes offline, the scenario below occurs:
The CoordinationTask starts abortAndScheduleRetry logic;
In abortAndScheduleRetry, the application tries to release claim in token store, but as the database is offline, this throws another exception;
The completable future chain is not handling exceptional completation, and because it, the task reschedule are not being executed;
When the database comes online again, as the reschedule is not happening and there is no CoordinationTask running, the application does not recover by itself, requiring a restart of the JVM.
Expected behaviour
The coordination task reschedule should execute always.
So, when the DB comes online again, the application can reconnect and continue processing events.
Actual behaviour
The application does not recover by itself, and does not generate a log record reporting this situation. Also, the related event processor don't handle the new events when the database goes online again, requiring a restart of the JVM.
Hi @smcvb!! Thank you very much for your time and attention!!
I agree that separating the Token Store and Event Store solutions would be ideal, but due some policies and restrictions of my project, I won't be able to go down that path for now.
About the logging pointers, I applied your suggestions (Thanks for the tips!!)
About the branching issue, as Github won't let me change the source branch, I "pointed" my master to your axon-4.5.x and I merged my changes into a single commit. Therefore, this PR is one commit ahead of axon-4.5.x at this moment!
Although this contribution is very, very small, I am very happy to make it! Axon is a great framework, and it is bringing very positive results to my projects!!
@fabio-couto, just to manage expectations, but are the comments shared by me and Allard something you can pick up?
If you don't have time for this soon-ish, I'll take over to speed up the release of Axon Framework 4.5.10.
@smcvb, I made a new commit with the suggested changes.
If more adjustments are needed, or if there's anything I can help with, please let me know!
|
package com.ykfa.leetcode.exercise.junior.array;
import java.util.HashMap;
import java.util.Map;
/**
* @author yingkefa
* @date 2020年03月06日10:16:03
*/
public class Solution1 {
public static void main(String[] args) {
int[] nums = new int[] {1, 1, 2};
int len = removeDuplicates(nums);
// 在函数里修改输入数组对于调用者是可见的。
// 根据你的函数返回的长度, 它会打印出数组中该长度范围内的所有元素。
for (int i = 0; i < len; i++) {
System.out.println(nums[i]);
}
}
public static int removeDuplicates(int[] nums) {
int rs = 0;
for (int i = 1; i < nums.length; i++) {
if (nums[rs] != nums[i]) {
rs = rs + 1;
nums[rs] = nums[i];
}
}
return rs + 1;
}
public static int removeDuplicates1(int[] nums) {
Map<Integer, Integer> map = new HashMap<>();
int rs = 0;
for (int i = 0; i < nums.length; i++) {
if (!map.containsKey(nums[i])) {
nums[rs] = nums[i];
map.put(nums[i], nums[i]);
rs++;
}
}
return rs;
}
}
/**
* 给定一个排序数组，你需要在原地删除重复出现的元素，使得每个元素只出现一次，返回移除后数组的新长度。
*
* 不要使用额外的数组空间，你必须在原地修改输入数组并在使用 O(1) 额外空间的条件下完成。
*
* 示例 1:
*
* 给定数组 nums = [1,1,2],
*
* 函数应该返回新的长度 2, 并且原数组 nums 的前两个元素被修改为 1, 2。
*
* 你不需要考虑数组中超出新长度后面的元素。 示例 2:
*
* 给定 nums = [0,0,1,1,1,2,2,3,3,4],
*
* 函数应该返回新的长度 5, 并且原数组 nums 的前五个元素被修改为 0, 1, 2, 3, 4。
*
* 你不需要考虑数组中超出新长度后面的元素。 说明:
*
* 为什么返回数值是整数，但输出的答案是数组呢?
*
* 请注意，输入数组是以“引用”方式传递的，这意味着在函数里修改输入数组对于调用者是可见的。
*
* 你可以想象内部操作如下:
*
* // nums 是以“引用”方式传递的。也就是说，不对实参做任何拷贝 int len = removeDuplicates(nums);
*
* // 在函数里修改输入数组对于调用者是可见的。 // 根据你的函数返回的长度, 它会打印出数组中该长度范围内的所有元素。 for (int i = 0; i < len; i++) {
* print(nums[i]); }
*/
|
Learning patterns/Supporting volunteers in administration
Supporting volunteers in administration
problemGroups of volunteers doing Wikimedia activities may become overwhelmed and demotivated by the amount of administration work that is required to be done to sustain their activities.
solutionConsider a number of ways to support volunteers in administration, including refining roles in your organization or hiring temporary or permanent paid administrative help.
creatorJwild
endorse
created on6 December, 2013
What problem does this solve?Edit
As volunteer groups grow their activities and impact, they may accrue an increasing amount of administrative work which needs to be done in order to sustain activities. For example, this could be applying for funding, submitting reimbursements, organizing events, answering helplines (phone, email, etc.).
What is the solution?Edit
One important driver for hiring an employee or contractor for Wikimedia organizations seems to be the increased amount of administrative time being stuck on the volunteers running other activities. This could be paperwork for receiving grants/funds, booking travel, administering expenses, etc. Before you consider bringing on an employee to do administrative work, consider the following alternatives:
1. Avoid taking on onerous administrative duties in the first place. For example, consider functioning as an informal group until you have a significant record of success with program activities to justify funding for administrative work. Keep in mind that hiring and managing staff itself may be a time-consuming task involving significant administrative work, so make sure that the long term benefits for your organization will be worth it.
2. Assess ways to make your organization function better. Consider reorganizing your project roles or organizational roles to make sure the work is shared and better supported within the volunteer team.
3. Recruit volunteers with the skills and interests needed to do administrative tasks.
4. Bring on a firm or temporary employee to handle some administrative duties associated with your projects or operational activities. (E.g. an accounting firm to help your organization with accounts on a periodic basis.)
General considerations for hiring an administrative employeeEdit
• Be mindful of the work that volunteers are currently doing, and be sure not to devalue that work or demotivate those volunteers as you are considering bringing on an administrative employee. Be sure to involve them in the conversations. Bringing on an employee for the first time may sometimes cause conflicts within your organization, especially if leadership or volunteers do not feel good about this choice. Getting money to hire an employee may always seems like a good thing, but you will want to consider the consequences for your organization carefully, as bringing on a long term employee will create an ongoing responsibility for your organization's leadership.
• Volunteer organizations doing excellent program work may benefit from bringing on staff to do administrative tasks, but funding for administrative work will always be tied to program results. If you're not able to show that you're already doing effective program work and that an administrative employee will allow you to do more, you are unlikely to receive funding for the employee.
• Consider that funding options for full-time and part-time staff may be different if your organization or group is asking for funds from one of the Wikimedia Foundation Grants Programs for your activities. For example, funding for part-time staff is available from the Project and Event Grants Program or the Annual Plan Grants Programs, while funding for permanent full-time staff is only available through the Annual Plan Grants Programs.
• Be careful not to hire permanent or long term staff that isn't necessary for the long-term! For example, if paperwork is only required once or twice a year, maybe just bring on a contractor for that period of time. Or, if there is an event that needs to be planned, consider bringing on a short-term contractor for just the event.
• Be clear and specific about what you will need this person to do. Be honest in the job description! Make sure to accurately portray the amount of administrative work that is required for the position (see quotes from 2013 First Employee study).
• Hire the right person. Extend your search beyond people you currently know or people who are currently on the board, to ensure that you hire the person with the skills and experience needed to succeed in this position, as well as the interest and motivation to do the work planned. A volunteer who is brilliant at managing programs may not be well-suited for administrative work. For a small organization, hiring the right employee (or the wrong one) can make a huge difference.
ExamplesEdit
Wikimedia D.C., 2013 Bootstrapping report
"The biggest lesson to learn is applicable to all U.S.-based chapters, present and future: forming a chapter should involve experts in non-profit governance from the start to handle the incorporation and tax-exemption recognition processes. While between the several Wikimedia DC founders we had some knowledge, enough minor details were overlooked to cause considerable delay to the process."
Wikimedia Österreich (WMAT), 2012 Annual plan report
"The extent of administrative tasks related to the grant process (application, reporting, closing)is a further strain for the limited personal resources, usually it is easier to spark volunteers for supporting projects, photo contests or events rather than for administrative tasks and accounting."
EndorsementsEdit
See alsoEdit
Related patternsEdit
External linksEdit
ReferencesEdit
|
Postgres v2: Add support for DeleteWithPrefix
Related to #3262
Adds DeleteWithPrefix to the PostgreSQL state store v2.
Notes:
This cannot work with CockroachDB, because CockroachDB does not offer sufficient support for UDFs which are needed to implement this. We will investigate how to add support for CockroachDB later. For now, the component can be instantiated without support for DeleteWithPrefix, so it can be used with CockroachDB
Because of lack of CockroachDB support, this has not been implemented in v1, due to the fact that the components for v1 are more "intertwined". Will be done in a separate PR.
Added conformance tests for YugabyteDB
Note that using YugabyteDB requires installing the "crypto" extension. See: https://yugabytedb.tips/?p=2178 We should investigate if we can have Dapr do that automatically.
Enabling conformance tests for Yugabyte really should be a separate PR
Agree. I'll leave it here for now so I can test that the feature works with Yugabyte too, but I'll move it out before marking the PR as ready for review.
|
Which of these advanced learner's dictionary definitions of "adversity" is reliable?
I looked up adversity in three different advanced learner's dictionaries and here are the results.
Longman Dictionary of Contemporary English 5th Edition: "a situation in which you have a lot of problems that seem to be caused by bad luck"
Cambridge Advanced Learner's Dictionary 4th Edition: "a difficult or unlucky situation or event"
Oxford Advanced Learner's Dictionary 9th Edition: "a difficult or unpleasant situation"
Personally, I feel like the Cambridge and Oxford definitions are too vague and generic for the need for a word like adversity aside from more frequently occurring words such as difficulty or trouble, which can only bring about more tiresome "the-difference-between" questions. Based on the applications of the word in my textbook which are typically in the context of "being caused by bad luck" (born blind, involved in a plane crash, stuck in a snowstorm, etc.), I feel like the Longman definition should be the reliable one. What do you think?
The first two definitions are very close, though CALD's 'first 'or' is probably better replaced with a slash (and/or). But CALD's 'unlucky' is less hedged than Longman's 'that seem to be caused by bad luck', and may be considered unjustified by those not believing in a malevolent 'fate'.
A lot depends on what you call "bad luck". "Adversity" does not simply involve failing to win the lottery.
Luck is not an essential element of the definition of the term even though it is often used in situations where bad fortune is part of the cause.
Yep, someone climbing Mt Everest faces adversity, even if nothing "unlucky" happens to them.
@HotLicks Failing to win the lottery doesn't seem to be "a situation in which you have a lot of problems" though. You'd simply say "Nah, maybe better luck next time".
@HotLicks I think what the definition means is that an adversity should involve problems/difficulties that you have no control over, hence the "bad luck" part. A mere difficulty or trouble can be caused by yourself (=something you could have managed but chose not to, e.g. didn't cram yesterday, fail the test today)
@Vun-HughVaw - Except I have a relative who spent at least $50,000 of his parents' money failing to win the lottery.
@HotLicks Except that's not caused by bad luck. Your relative just screwed himself by spending that much of his parents' money on lottery. He should have had a choice not to play the lottery.
@Vun-HughVaw - It all depends on your point of view. He had a "system" that was "guaranteed to win".
|
package linkedlists;
public class SumLists {
public static Node sumLists(Node l1, Node l2, int carry){
if(l1 == null && l2 == null && carry ==0)
return null;
int value = carry;
if(l1 != null)
value += l1.data;
if(l2 != null)
value += l2.data;
Node result = new Node(value%10);
if(l1 != null || l2 != null){
Node more = sumLists(l1 == null ? null:l1.next, l2 == null ? null:l2.next, value>10 ? 1:0);
result.next = more;
}
return result;
}
static class PartialSum{
public Node sum = null;
public int carry = 0;
}
public static int length(Node l1){
int length = 0;
Node temp = l1;
while(temp != null){
length++;
temp = temp.next;
}
return length;
}
public static Node padZero(Node l, int padding){
Node head = l;
for(int i=0; i< padding; i++){
head = addBefore(head,0);
}
return head;
}
public static Node addBefore(Node head, int value){
Node node = new Node(value);
if(head != null)
node.next = head;
return node;
}
public static Node addLists(Node l1, Node l2){
int len1 = length(l1);
int len2 = length(l2);
if(len1<len2){
padZero(l1,len2-len1);
}
else{
padZero(l2,len1-len2);
}
PartialSum sum = addListsHelper(l1,l2);
if(sum.carry == 0)
return sum.sum;
else
return addBefore(sum.sum,sum.carry);
}
private static PartialSum addListsHelper(Node l1, Node l2) {
if(l1 == null && l2 == null)
return new PartialSum();
PartialSum sum = addListsHelper(l1.next,l2.next);
int value = sum.carry + l1.data + l2.data;
Node result = addBefore(sum.sum, value % 10);
sum.sum = result;
sum.carry = value/10;
return sum;
}
public static void main(String args[]){
Node exam = new Node(7);
Node head = exam;
exam.appendToTail(1);
exam.appendToTail(6);
Node exam2 = new Node(5);
Node head2 = exam2;
exam2.appendToTail(9);
exam2.appendToTail(2);
Node n = head;
while(n!=null){
System.out.print(n.data+" ");
n=n.next;
}
System.out.print("\n");
n = head2;
while(n!=null){
System.out.print(n.data+" ");
n=n.next;
}
System.out.print("\n");
n = addLists(head,head2);
while(n!=null){
System.out.print(n.data+" ");
n=n.next;
}
}
}
|
Wikipedia:Articles for deletion/Psychoembryology
The result of the debate was delete. Sango 123 (e) 23:03, 17 April 2006 (UTC)
Psychoembryology
This term gets only three Google results. Unfortunately, none of them work. From the results page, two of them appear to be mentions in a list. The word is not shown in the third result, but it is not promising. If this was a real field of study, I would expect far more results, with at least several of them being of decent quality. The article mentions cellular memories (mispelled in the article), which seems to be pseudoscience from my brief investigation. Here is one statement about them. "Cellular memories are stored in the DNA, which we receive from our ancestors. Cellular memory is created whenever we experience trauma or make an emotional decision. And if you believe in such things, cell memory comes in from other lifetimes, other aspects of ourselves in other dimensions." I believe that this article should be deleted as non-notable pseudoscience. -- Kjkolb 12:07, 11 April 2006 (UTC)
* Delete per nom. Metamagician3000 12:37, 11 April 2006 (UTC)
* Delete: a pseudoscience without followers, and looks like a bad Babelfish translation of some sort. The two links are unimpressive (Yahoo free hosting?) Zetawoof(ζ) 22:25, 11 April 2006 (UTC)
* delete as per nom, also qualifies as Nonsense IMnsHO Pete.Hurd 19:13, 16 April 2006 (UTC)
|
Method and device for measuring bio-impedance data of a person
ABSTRACT
A method and a device for determining biological impedance data of a person, in which least one impedance value is measured with the use of at least two electrodes and is transmitted to an evaluation unit. In the area of at least one output device, information concerning the person is made available for assuming an optimum body posture for the measurement of the biological impedance.
The invention relates to a method for determining the biological impedance of a person, wherein at least one impedance value is measured by using at least two electrodes and is transmitted to an evaluation unit.
Moreover, the invention relates to a device for determining the biological impedance values of a person, wherein the device has at least two electrodes for measuring at least one biological impedance value and the electrodes are coupled for transmitting measurement values to an evaluation unit.
Such methods and devices are typically carried out with the use of so-called body composition analyzers (BCA). Such devices are frequently equipped with two pairs of electrodes on which the person to be measured stands. Moreover, two additional electrodes are frequently provided for each hand of the person.
When using such devices and carrying out the method, it has been found that the quality of the measurement values is substantially influenced by the concrete body posture of the person. In the case of unfavorable body posture, measurement values can occur which lead to incorrect or imprecise measurement values.
Therefore, it is the object of the present invention to improve a method of the type mentioned in the introduction in such a way that the measuring accuracy is increased.
In accordance with the invention, this object is met by making available, in the area of at least one output device, information concerning the person for assuming an optimum body posture for measuring the biological impedance.
It is another object of the present invention to construct a device of the type mentioned in the introduction in such a way that the carrying out of precise measurements is reinforced.
In accordance with the invention this object is met in that the evaluation unit is coupled to an output unit, wherein the output unit is configured for making available information concerning an optimum body posture of the person.
The use of an output unit for making available information concerning a body posture of the person to be measured, makes it possible to provide the person with information concerning the assuming of a body posture or for correcting an already assumed body posture.
This can be carried out, for example, visually in the area of a display, acoustically, or by optically marking of the body parts to be positioned.
A good capacity for observation of the information is facilitated by visually representing the information.
In particular, an optimization of the body posture is reinforced by carrying out at least a partial measurement of an actual body posture of the person.
A simple realization by means of technical devices is reinforced by determining the body posture of the person by means of a camera.
In accordance with another embodiment, it is also being considered to determine the body posture through a mechanical measuring device, particularly a tactile device. In addition, by mounting movement sensors and/or triangulation, the position of the hand electrodes in space can be determined (similar to de.wikipedia.org/wiki/Wii-Fernbedienung).
A further improvement of the measuring quality can be achieved by providing the information on the basis of a comparison of an actual body posture to a desired body posture.
In the drawings, embodiments of the invention are schematically illustrated. In the drawing:
FIG. 1 shows a perspective partial illustration of a hand grip of a body composition analyzer,
FIG. 2 is a perspective illustration of a person who stands on a body composition analyzer,
FIG. 3A is a schematic illustration of a visual display with indicators for a correction of the body posture,
FIG. 3B illustrates a display in accordance with FIG. 3A with an indication concerning an already corrected body posture,
FIG. 4 is a perspective illustration of another device in which the person to be measured has grasped two hand grips.
In accordance with the illustration in FIG. 1, a hand 1 of a person 2 to be measured is positioned in the area of a grip 3 of a device for determining biological impedance data. In the area of the grip 3, a plurality of electrodes 4, 5 are arranged. At least in the area of several of the electrodes 4, 5, illuminating displays 6 are arranged, for example, light emitting diodes.
The illuminating displays 6 can, for example, by means of a green or red color, signal a correct or an incorrect positioning of the hand 1.
FIG. 2 is a schematic illustration of the person standing on the device for measuring biological impedance data. The person 2 has grasped the grip 3 in the area of several electrodes 4, 5. In viewing direction in front of the person 2, a display 7 can be seen. The display 7 may be for example, a screen or LED.
In the area of a standing surface 8, electrodes 9, 10 for the feet 11, 12 of the person 2 are arranged. A scale 13 for determining the weight of the person 2 may be positioned in the area of the standing surface 8.
In the illustrated embodiment, the grip 3 extends comparable to a railing in a semicircle. Moreover, the grip 3 is arranged inclined relative to the horizontal direction for reinforcing a positioning of the electrodes 4, 5 which is favorable for gripping.
Several pairs of electrodes 4, 5 may be arranged along the hand grip 3. In this connection each pair provides a position for the hands of the user. The correct body posture of the user can be obtained, for example, with the use of an electrical recognition of the respective pairs of electrodes contacting the person.
For example, it is possible in a first use by an assistant to determine a correct positioning for the hand of the person to be measured. This position can be stored, for example, in an electronic patient file. During the next use a comparison is made whether the respective user has once again contacted the electrodes in the position which is already known as being correct. A report back to the person to be measured or the assistant can be carried out, for example, in the area of hand grip 3 by illuminating green or red LED 6. When correctly positioned, the green LED would be controlled or when incorrectly positioned the red LED would be controlled.
FIG. 3A shows an indicator 7 constructed as a display with an illustration of a person 2 who has grasped the hand electrodes 14, 15. In the area of the indicator 7, correction displays 16, 17 are provided for the left and the right hand of the person 2. The correction displays 16, 17 may signal, for example, whether the respective hand should be raised or lowered to a greater extent, or whether the respective hand has to be positioned further to the left or to the right.
In accordance with the illustration in FIG. 3B, it is signaled that no correction of the hand position is required.
FIG. 4 shows another person that holds a hand electrode 14 in the right hand.
Considered in particular is the use of contactless measuring devices. An optical measurement can be carried out with the use of a camera or without the use of a camera. For example, light barriers, laser scanners or carrying out a triangulation can be used. Also generally usable are electric measuring methods, as well as capacitive measurements. Another measurement can be carried out with the use of ultrasound.
1-17. (canceled)
18. A method for determining biological impedance data of a person, comprising the steps of: measuring at least one impedance value using at least two electrodes; transmitting the measured value to an evaluation unit; and, in an area of at least one display device, making information available for the person for assuming an optimum body posture for measuring the biological impedance.
19. The method according to claim 18, wherein the information is depicted visually.
20. The method according to claim 18, including at least a partial determination of an actual body posture of the person is carried out.
21. The method according to claim 20, including recording the body posture of the person with a camera.
22. The method according to claim 20, including recording the body posture with a mechanical measuring device.
23. The method according to claim 20, including recording the body posture with an electrical and/or capacitive measuring device.
24. The method according to claim 20, including recording the body posture with an ultrasound measuring device.
25. The method according to claim 20, including recording the body posture with an optical measuring device.
26. The method according to claim 20, including recording the body posture with a contactless measuring device.
27. The method according to claim 18, including signaling information concerning a body posture by at least one illuminated display in an area of at least one of the electrodes.
28. The method according to claim 18, wherein the information is issued on the basis of a comparison of an actual body posture with a desired body posture.
29. A device for determining biological impedance data of a person, the device comprising: at least two electrodes for measuring at least one biological impedance value; an evaluation unit for transmitting measurement values, the electrodes being coupled to the evaluation unit; and an output device for making available information concerning an optimum body posture of the person, the evaluation unit being coupled to the output device.
30. The device according to claim 29, wherein the output device is constructed for showing visual information.
31. The device according to claim 29, further comprising at least one measuring device for determining an actual body posture of a person.
32. The device according to claim 31, wherein the measuring device is a camera.
33. The device according to claim 31, wherein the measuring device is a mechanical measuring device.
34. The device according to claim 29, wherein the evaluation unit is operatively constructed to carry out a desired value/actual value comparison with respect to the body posture of the person.
|
and must render great assistance to the Queen; and the Queen's
confidence in his judgment having so much increased, this consequence
was the more natural. The Prince must, however, be very cautious at
first, and in a little time he would fall into it. He must be
very careful not to alarm the Queen, by Her Majesty for an instant
supposing that the Prince was carrying on business with Peel without
her cognisance.
If it were possible for any one to advise Peel, he would recommend
that he should write fully to Her Majesty, and _elementarily_, as Her
Majesty always liked to have full knowledge upon everything which was
going on. He would advise the Queen to be cautious in giving a verbal
decision, that she should not allow herself to be _driven into a
corner_, and forced to decide where she felt her mind was not made up
and required reflection.
Peel should be very careful that intelligence came first from him
direct. King William was very particular upon this point, so was the
Queen.
I asked Lord Melbourne if he had considered the future position of
himself with the Queen, and also of Peel with the Queen. He said he
owned he had not and would avoid entering into any discussion--he felt
sure that he should be regarded with extreme jealousy, not so much by
Peel as by the party. He would be looked upon as Lord Bute had been in
his relation to George III.,--always suspected of secret
intercourse and intrigue. He would make me the medium of any written
communication.
With regard to Peel's position with the Queen, he thought that
circumstances must make it. He thought the Queen must see him oftener
than King William did him, as he thought the present state of things
would require more frequent intercourse. The late King used to see
him once a week after the Levée, seldom oftener; all the rest of the
business was transacted by correspondence, but this mode, though it
had its merits in some respect, very much impeded the public business.
The less personal objections the Queen took to any one the better, as
any such expression is sure to come out and a personal enemy is
made. It was also to be recollected that Peel was in a very different
position now, backed by a large majority, to when the other overture
was made. He had the power _now_ to extort what he pleased, and he
fancied he saw the blank faces of the heads of the Party when Peel
told them that he had agreed to the dismissal or resignation of only
three of the Queen's ladies.
Lord Melbourne said the Queen was afraid she never could be at ease
with Peel, because his manner was so embarrassed, and that conveyed
embarrassment also to her, which it would be very difficult to get
over.
The Queen took leave of Lord Melbourne to-day. Her Majesty was much
affected, but soon recovered her calmness.
Peel had his first audience at half-past three o'clock.
[Pageheading: MELBOURNE'S OPINION OF THE PRINCE]
_Viscount Melbourne to Queen Victoria._
_30th August 1841_ (6 P.M.).
Lord Melbourne presents his humble duty to your Majesty. The
announcement has been made in both Houses of Parliament. A few words
were said by Lord Stanley[73] in the House of Commons, and nothing in
the House of Lords.
Lord Melbourne cannot satisfy himself without again stating to your
Majesty in writing what he had the honour of saying to your Majesty
respecting his Royal Highness the Prince. Lord Melbourne has formed
the highest opinion of His Royal Highness's judgment, temper, and
discretion, and he cannot but feel a great consolation and security
in the reflection that he leaves your Majesty in a situation in
which your Majesty has the inestimable advantage of such advice and
assistance. Lord Melbourne feels certain that your Majesty cannot do
better than have recourse to it, whenever it is needed, and rely upon
it with confidence.
Lord Melbourne will be anxious to hear from your Majesty as to what
has passed with Sir R. Peel. Your Majesty will, Lord Melbourne is
sure, feel that the same general secrecy which your Majesty has always
observed respecting public affairs is more particularly necessary at
the present moment.
Lord Melbourne earnestly hopes that your Majesty is well and composed,
and with the most anxious wishes for your Majesty's welfare and
happiness, remains ever your Majesty's most devoted and attached
Servant, and he trusts that he may add, without presumption, your
Majesty's faithful and affectionate Friend.
[Footnote 73: Who now became Colonial Secretary.]
[Pageheading: THE HOUSEHOLD]
_Memorandum: Viscount Melbourne to Queen Victoria._
Your Majesty might say, if to your Majesty it seems good, that in
consequence of the Addresses voted by both Houses of Parliament, your
Majesty's servants had tendered their resignations, and that for the
same reason your Majesty had accepted those resignations. That your
Majesty's present servants possessed your Majesty's confidence,
and that you only parted with them in deference to the opinion of
Parliament.
That your Majesty naturally had recourse to Sir Robert Peel as
possessing the confidence of the great Party which constitutes the
majority of both Houses, and that you were prepared to empower him to
form an Administration.
That your Majesty did not conceive that the giving him this commission
of itself empowered him to advise the removal of the officers of your
Majesty's Household; that you conceive that all that the Constitution
required was that the Sovereign's Household should support the
Sovereign's Ministers; but that you were prepared to place at his
disposal, and to take his advice upon all the offices of the Household
at present filled by members of either House of Parliament, with
the exception of those whom your Majesty might think proper to
name, _i.e._, Lord Byron[74]--and it should be understood that this
exception was not to extend further than to him.
If Sir Robert Peel should wish that in case of Lord Byron's remaining
it should be considered as a fresh appointment made by his advice,
this wish might properly be acceded to.
_The Ladies._--If any difficulty should arise it may be asked to be
stated in writing, and reserved for consideration. But it is of great
importance that Sir Robert Peel should return to London with full
power to form an Administration. Such must be the final result, and
the more readily and graciously it is acquiesced in the better.
Your Majesty must take care not to be driven to the wall, and to
be put into a situation in which it is necessary to Aye or No. No
positive objection should be taken either to men or measures.
It must be recollected that at the time of the negotiation in 1839
Lord Melbourne and Lord John Russell were still at the head of a
majority in the House of Commons. This is not the case now.
[Footnote 74: George Anson, seventh Lord Byron (1789-1868),
cousin and successor of the poet.]
[Pageheading: THE NEW CABINET]
THE CABINET OF LORD MELBOURNE,
_As it stood in September 1841._
_First Lord of the Treasury_ VISCOUNT MELBOURNE.
_Lord Chancellor_ LORD (afterwards Earl of)
COTTENHAM.
_Chancellor of the Exchequer_ Mr FRANCIS BARING
(afterwards Lord Northbrook).
_Lord President of the Council_ MARQUIS OF LANSDOWNE.
_Lord Privy Seal_ EARL OF CLARENDON.
_Home Secretary_ MARQUIS OF NORMANBY.
_Foreign Secretary_ VISCOUNT PALMERSTON.
_Colonial Secretary_ LORD JOHN (afterwards
Earl) RUSSELL.
_First Lord of the Admiralty_ EARL OF MINTO.
_President of the Board of Control_ Sir JOHN CAM HOBHOUSE
(afterwards Lord Broughton).
_Secretary at War_ Mr T. B. (afterwards
Lord) MACAULAY.
_President of the Board of Trade_ Mr LABOUCHERE (afterwards
Lord Taunton).
_Chief Secretary for Ireland_ VISCOUNT MORPETH
(afterwards Earl of Carlisle).
_First Commissioner of Land Revenue_ VISCOUNT DUNCANNON
(afterwards Earl of Bessborough).
_Chancellor of the Duchy of Lancaster_ Sir GEORGE GREY.
THE CABINET OF SIR ROBERT PEEL,[75]
_As formed in September 1841._
_First Lord of the Treasury_ Sir ROBERT PEEL.
_Lord Chancellor_ LORD LYNDHURST.
_Chancellor of the Exchequer_ Mr. H. GOULBURN.
(_Without Office_) DUKE OF WELLINGTON.
_Lord President of the Council_ LORD WHARNCLIFFE.
_Lord Privy Seal_ DUKE OF BUCKINGHAM.
_Home Secretary_ Sir JAMES GRAHAM.
_Foreign Secretary_ EARL OF ABERDEEN.
_Colonial Secretary_ LORD STANLEY
(afterwards Earl of Derby).
_First Lord of the Admiralty_ EARL OF HADDINGTON.
_President of the Board of Control_ LORD (afterwards Earl of)
ELLENBOROUGH
_Secretary at War_ Sir HENRY (afterwards
Viscount) HARDINGE.
_President of the Board of Trade_ EARL OF RIPON.
_Paymaster-General_. Sir EDWARD KNATCHBULL.
[Footnote 75: The Peel Ministry of 1841 was unique in
containing three ex-Premiers: Sir Robert Peel himself, the
Earl of Ripon, and the Duke of Wellington, who succeeded Lord
Goderich as Premier in 1828. Ripon's career was a curious one;
he was a singularly ineffective Prime Minister, and indeed did
not, during the course of his Ministry (August 1827-January
1828), ever have to meet Parliament. He was disappointed
at not being invited to join the Wellington Ministry,
subsequently joined the Reform Ministry of Lord Grey, but
followed Lord Stanley, Sir James Graham, and the Duke of
Richmond out of it. In August 1841 he moved the vote of want
of confidence in the Melbourne Ministry, and became President
of the Board of Trade in Peel's Government. In 1846 it fell to
him, when President of the Board of Control, to move the Corn
Law Repeal Bill in the Lords.
The only later instance of an ex-Premier accepting a
subordinate office was in the case of Lord John Russell, who,
in 1852, took the Foreign Office under Aberdeen, subsequently
vacating the office and sitting in the Cabinet without office.
In June 1854, he became Lord President of the Council, and
left the Ministry when it was menaced by Roebuck's motion.
When Lord Palmerston formed a Ministry in 1855, Lord John,
after an interval, became Colonial Secretary, again resigning
in five months. Finally, in 1859, he went back to the Foreign
Office, where he remained until he succeeded Palmerston as
Premier in 1865.
The Government also contained three future Premiers, Aberdeen,
Stanley, and Gladstone.]
[Pageheading: INTERVIEW WITH PEEL]
[Pageheading: HOUSEHOLD APPOINTMENTS]
[Pageheading: THE QUEEN'S DISTRESS]
_Queen Victoria to Viscount Melbourne._
WINDSOR CASTLE _30th August 1841._
... The first interview with Sir Robert Peel has gone off well, and
only lasted twenty minutes; and he sends the Queen to-morrow, in
writing, the proposed arrangements, and will only come down on
Wednesday morning. He first wished to come to-morrow, but on the
Queen's saying that he need not to do that, but might send it and only
come down Wednesday, he thought the Queen might prefer having it to
consider a little, which she said she certainly should, though she
meant no want of confidence. The Queen, in the first instance, stated
that she concluded he was prepared for her sending for him, and then
stated exactly what Lord Melbourne wrote, viz., the resignation having
taken place in consequence of the Addresses--the Queen's great regret
at parting with her present Ministers--the confidence she had in them,
and her only acceding in consequence of the Addresses in Parliament,
and then that consequently she looked to him (Sir Robert Peel) as
possessing the confidence of both Houses of Parliament to form an
Administration. He made many protestations of his sorrow, at what must
give pain to the Queen (as she said to him it did), but of course said
he accepted the task. The Duke of Wellington's health too uncertain,
and himself too prone to sleep coming over him--as Peel expressed
it--to admit of his taking an office in which he would have much to
do, but to be in the Cabinet, which the Queen expressed her wish he
should. He named Lord De Grey[76] as Lord Lieutenant of Ireland,
and Lord Eliot[77] as Secretary for Ireland, who, he said, were both
moderate people. The Queen said she gave up to him the officers of
State and those of her Household who were in Parliament, and he then
asked if Lord Liverpool would be agreeable as Lord Steward (the Queen
said he would), and if she would object to Lord Jersey as Master of
the Horse (she said she would not), as she believed he understood it
perfectly. He said he was so anxious to do everything which could be
agreeable to the Queen, that he wished her to name whom she should
like as Lord Chamberlain; she said he might suggest some one, but as
he would not, and pressed the Queen to name whoever she pleased,
she said she should like the Duke of Rutland, and he said he would
certainly name it to him. The Queen said that Lord Melbourne had
always been very particular to name no one who might be disagreeable
to her in the Household, and Sir R. Peel said he felt this, and
should be most anxious to do what could be agreeable to me and for my
comfort, and that he would even sacrifice any advantage to this. The
Queen mentioned the three Ladies' resignation, and her wish not to
fill up the three Ladies' places immediately. She mentioned Lady
Byron,[78] to which he agreed immediately, and then said, as I had
alluded to those communications, he hoped that he had been understood
respecting the _other_ appointments (meaning the Ladies), that
provided I chose some who had a leaning towards the politics of the
Administration, I might take any I liked, and that he quite understood
that I should notify it to them. The Queen said this was her rule, and
that she wished to choose moderate people who should not have scruples
to resign in case another Administration should come in, as changing
was disagreeable to her. Here it ended, and so far well. He was
very anxious the Queen should understand _how_ anxious he was to do
everything which was agreeable to the Queen. The Queen wishes to know
if Lord Melbourne thinks she should name the Duchess of Buccleuch
Mistress of the Robes, on Wednesday, and if she shall ask Sir Robert
to sound the Duchess, or some one else, and then write to appoint her?
She thinks of proposing Lady de la Warr and Lady Abercorn by and by as
the two Ladies, but these she will sound herself through other people,
or Lady Canning, or Lady Rosslyn, in case these others should not take
it. She should say she meant to sound those, and no more. What the
Queen felt when she parted from her dear, kind friend, Lord Melbourne,
is better imagined than described; she was dreadfully affected for
some time after, but is calm now. It is very, very sad; and she cannot
quite believe it yet. The Prince felt it very, very much too, and
really the Queen cannot say how kind and affectionate he is to her,
and how anxious to do everything to lighten this heavy trial; he was
quite affected at this sad parting. We do, and shall, miss you so
dreadfully; Lord Melbourne will easily understand what a change it
is, after these four years when she had the happiness of having Lord
Melbourne always about her. But it will not be so long till we meet
again. Happier and brighter times will come again. We anxiously hope
Lord Melbourne is well, and got up well and safe. The Queen trusts he
will take care of his valuable health, now more than ever.
[Footnote 76: Thomas, Earl de Grey (1781-1859); he was the
elder brother of Lord Ripon, who had been previously known
as Mr Robinson and Viscount Goderich, and whose son, besides
inheriting his father's and uncle's honours, was created
Marquis of Ripon.]
[Footnote 77: Afterwards third Earl of St Germans.]
[Footnote 78: Lady Byron had been Miss Elizabeth
Chandos-Pole.]
_Memorandum by Mr Anson._
WINDSOR CASTLE, _31st August 1841._
I was sent up to Town to-day to see Lord Melbourne and Sir Robert
Peel. I found Lord Melbourne as usual up in his bedroom. He had
received the account of Her Majesty's first interview with Peel, which
he thought very satisfactory. Sir Robert very much regretted that he
should have been the instrument of obliging Her Majesty to change her
Government. The Queen had said to Sir Robert that though she did not
conceive the Minister could demand any of the Household appointments,
still it was Her Majesty's intention to give up to him the great
offices of State, and all other places in the Household filled by
people in Parliament. He was to send his proposed list for offices the
next day and be at Windsor the morning after that. Lord Melbourne
had written to the Queen the night before, stating his opinion of the
Prince--that he had great discretion, temper, and judgment, and that
he considered him to be well worthy of Her Majesty's confidence, and
that now was the time for Her Majesty to feel comfort and assistance
from giving him her fullest confidence. He had just received the
Queen's answer to this, saying what "pleasure it had given the Queen
to receive his letter with this expression of his opinion of her
beloved husband, and that what he said could not fail to increase
the confidence which she already felt in him. He was indeed a great
comfort to her in this trying moment; at times she was very low indeed
though she strove to bear up. It would always be a satisfaction to
her to feel secure of Lord Melbourne's faithful and affectionate
friendship to her and the Prince. She hoped after a time to see him
here again, and it would always be a pleasure to her to hear from him
frequently."
From South Steet I went to Sir Robert Peel's. I told him I came to
speak to him about Lord Exeter, whom the Prince proposed to make
the head of his Household, should it not interfere with any of Sir
Robert's arrangements for the Queen. Sir Robert said he was so good a
man and one that he felt sure the Prince would like, and he therefore
thought he had better propose the situation to him at once.
[Pageheading: MELBOURNE'S OFFICIAL FAREWELL]
_Viscount Melbourne to Queen Victoria._
SOUTH STREET, _31st August 1841._
Lord Melbourne had the pleasure of receiving last night both your
Majesty's letters, the one dated four o'clock, and written immediately
after your Majesty's interview with Sir R. Peel, the other dated
half-past nine. Lord Melbourne thanks your Majesty much for them both,
and for the expressions of kindness contained in them. Lord Melbourne
will ever consider the time during which your Majesty is good enough
to think that he has been of service to your Majesty the proudest as
well as the happiest part of his life.
Lord Melbourne has read with great care your Majesty's very clear and
full account of what passed. It appears to Lord Melbourne that nothing
could be better. Sir Robert Peel seems to have been anxious to act
with the utmost respect and consideration for your Majesty, and your
Majesty most properly and wisely met him half-way. In the spirit
in which the negotiation has been commenced I see the prospect of a
termination of it, which will be not so unsatisfactory to your
Majesty as your Majesty anticipated, and not, Lord Melbourne trusts,
disadvantageous to the country....
Lord Melbourne concludes with the most anxious wishes for your
Majesty's happiness and with expressing a great admiration of the
firmness, prudence, and good sense with which your Majesty has
conducted yourself.
Lord Melbourne begs to be remembered to His Royal Highness most
respectfully, most affectionately.
_Viscount Melbourne to Queen Victoria._
_31st August 1841._
Lord Melbourne presents his humble duty to your Majesty, and has just
received your Majesty's letter. Lord Melbourne rejoices much to learn
that your Majesty feels more composed and that you are well. Recollect
how precious is your Majesty's health, and how much health depends
upon tranquillity of mind....
Lord Melbourne will either write to Sir Francis Chantrey[79] to-morrow
morning, or call upon him and settle without further delay about the
Bust. There is no end of subscriptions to Monuments, but perhaps your
Majesty will do well to subscribe to Sir David Wilkie's.[80]
Your Majesty is very good about the blue Ribband, but Lord Melbourne
is certain that upon the whole, it is better for his own position and
character that he should not have it.
[Footnote 79: Sir Francis Chantrey, the sculptor, born in
1781, died on 25th November 1841.]
[Footnote 80: Sir David Wilkie, Painter-in-Ordinary to the
Queen, had died on 1st June, aged fifty-six.]
[Pageheading: PEEL'S RECEPTION]
_The Earl of Clarendon[81] to Viscount Melbourne.[82]_
GROSVENOR CRESCENT, _31st August 1841._
MY DEAR MELBOURNE,--You may like to know that Peel was perfectly
satisfied with his reception yesterday, and does full justice to the
Queen's declaration of her regret at parting with her Ministers, which
he said it was quite natural she should feel, and quite right she
should express. This I know from undoubted authority, and from a
person who came to enquire of me whether I could tell what impression
Peel had produced upon the Queen, which of course I could not.
He assured the Queen that he had had no communication with his
friends, and was not prepared to submit an Administration for her
approval, but he is to see her again to-morrow morning.
The only appointment yet settled is De Grey to Ireland; he was very
unwilling, but Peel insisted. Yours sincerely,
CLARENDON.
[Footnote 81: The retiring Lord Privy Seal.]
[Footnote 82: Letter forwarded by Lord Melbourne to the
Queen.]
[Pageheading: FAREWELL AUDIENCES]
_Viscount Palmerston to Queen Victoria._
CARLTON TERRACE, _31st August 1841._
... Viscount Palmerston begs to be allowed to tender to your Majesty
the grateful thanks of himself and of Viscountess Palmerston for your
Majesty's gracious expressions towards them. Viscount Palmerston sees
with deep regret the termination of those duties in your Majesty's
service, in the course of which he has had the honour of experiencing
from your Majesty so much condescending personal kindness, and
such flattering official confidence; and it affords him the highest
gratification to have obtained your Majesty's approbation.
_Viscount Melbourne to Queen Victoria._
SOUTH STREET, _2nd September 1841._
Lord Melbourne presents his humble duty to your Majesty. He received
your Majesty's letter yesterday evening, and was very glad to learn
from it that your Majesty was not ill satisfied with Sir Robert Peel,
and that the arrangements were going on smoothly, which it is highly
desirable that they should. Your Majesty should desire Sir Robert
Peel to give notice to all those who have insignia of office, such
as Seals, Wands, to give up, to attend at Claremont on Friday; but of
course he will do this of himself. Your Majesty will have much to go
through upon that day and much that is painful. Your Majesty should
spare yourself and be spared as much as possible. It will not be
necessary for Lord Melbourne to go down. He may be considered as
having resigned at the Audience which he had of your Majesty at
Windsor, and Lord Melbourne has ventured to tell Lord Lansdowne that
he thinks he need not do so either, and that your Majesty will excuse
his attendance. Lord Melbourne need say nothing about the Secretaries
of State, with all of whom your Majesty is so well acquainted; but
perhaps your Majesty will not omit to thank Mr Baring[83] cordially
for his services. He is a thoroughly honest man and an able public
servant. If your Majesty could say to the Lord Chancellor,[84] "that
you part with him with much sorrow; that you are sensible that much of
the strength of the late Administration was derived from the manner
in which he discharged the duties of his office, and that you consider
his retirement a great and serious loss to the country," it would
certainly be no more than he deserves.
It is thought by some who know him here that the Duke of Rutland will
be so extremely pleased with the offer being made, and that by your
Majesty yourself, that he will accept it; but he is a year older than
Lord Melbourne, and therefore hardly fit for any very active duty....
The appointment of Colonel Arbuthnot will of course be very agreeable
to the Duke of Wellington. The Arbuthnots are quiet, demure people
before others; but they are not without depth of purpose, and they are
very bitter at bottom.
Your Majesty will not forget the two Knights for Mr de la Beche[85]
and Major Monro.
Lord Melbourne begins to hope that this affair will be got through
more satisfactorily and with less annoyance than your Majesty
anticipated. As long as your Majesty is desirous of receiving his
communications, he will be always most careful to give your Majesty
his impartial opinion and the best advice which he has to offer. His
most fervent prayer will always be for your Majesty's welfare and
happiness.
[Footnote 83: The retiring Chancellor of the Exchequer.]
[Footnote 84: Lord Cottenham.]
[Footnote 85: Sir Henry T. de la Beche, an eminent geologist.]
[Pageheading: MELBOURNE'S LAST OFFICIAL LETTER]
_Viscount Melbourne to Queen Victoria._
SOUTH STREET, _2nd September 1841._
....Lord Melbourne hopes and trusts that when to-morrow is over your
Majesty will recover from that depression of spirits under which your
Majesty now labours. Lord Melbourne never doubted that it would be
so, but is glad to learn from your Majesty the support and consolation
which your Majesty finds in the advice and affection of the Prince.
This is the last letter which Lord Melbourne will send in a box. He
will to-morrow morning return his keys to the Foreign Office, and
after that your Majesty will be good enough to send the letters, with
which you may honour Lord Melbourne, through Mr Anson.
Lord Melbourne most anxiously wishes your Majesty every blessing.
[Pageheading: COUNCIL AT CLAREMONT]
_Viscount Melbourne to Queen Victoria._
SOUTH STREET, _3rd September 1841._
Lord Melbourne earnestly hopes that your Majesty is well after this
trying day.[86] Lord Melbourne has thought and felt for your Majesty
all this morning. But now that the matter is settled it will be
necessary that your Majesty should take a calm and composed view of
the whole situation, which Lord Melbourne trusts that your Majesty
will find by no means unsatisfactory.
And first with respect to public affairs. In the concerns of a
great nation like this there will always be some difficulties and
entanglements, but upon the whole the present state is good and the
prospect is good for the future. There is no reason to expect that
Sir Robert Peel will either be desirous or be able to take a very
different course from that which has been taken by your Majesty's late
servants, and some difficulties will certainly be removed, and some
obstacles smoothed, by the change which has lately taken place.
With respect to the effect which will be produced upon the comfort of
your Majesty's private life, it would be idle in Lord Melbourne,
after what your Majesty has said, to doubt of the manner in which your
Majesty will feel the change, which must take place in your Majesty,
to long accustomed habits and relations. But your Majesty may rest
assured of Lord Melbourne's devoted and disinterested attachment
to your Majesty, and that he will devote himself to giving to your
Majesty such information and advice as may be serviceable to your
Majesty with the sole view of promoting your Majesty's public
interests and private happiness.
Lord Melbourne hopes, and indeed ventures to expect, that your
Majesty, upon reflection and consideration of the real state of
circumstances, will recover your spirits, and Lord Melbourne has
himself great satisfaction in thinking upon the consideration of
the advice which he has given, that it has not tended to impair your
Majesty's influence and authority, but, on the contrary, to secure to
your Majesty the affection, attachment, approbation, and support of
all parties.
In the course of this correspondence Lord Melbourne has thought it his
duty to your Majesty to express himself with great freedom upon
the characters of many individuals, whose names have come under
consideration, but Lord Melbourne thinks it right to say that he may
have spoken upon insufficient grounds, that he may have been mistaken,
and that the persons in question may turn out to be far better than he
has been induced to represent them.
[Footnote 86: A Council had been held at Claremont for the
outgoing Ministers to give up their Seals of Office, which
were bestowed upon Sir Robert Peel and the incoming Cabinet.]
[Pageheading: MELBOURNE ON THE NEW MINISTRY]
_Viscount Melbourne to Queen Victoria._
SOUTH STREET, _4th September 1841._
Lord Melbourne presents his humble duty to your Majesty. He was most
happy to hear yesterday the best account of everything that had taken
place at Claremont. Everybody praised, in the highest manner, the
dignity, propriety, and kindness of your Majesty's deportment, and if
it can be done without anything of deceit or dissimulation, it is well
to take advantage of the powers and qualities which have been given,
and which are so well calculated to gain a fair and powerful influence
over the minds and feelings of others. Your Majesty may depend upon
it, that the impression made upon the minds of all who were present
yesterday, is most favourable. Of course, with persons in new and
rather awkward situations, some of whom had never been in high office
before, all of whom had not been so now for some years, there was a
good deal of embarrassment and mistakes. Forms which are only gone
through at long intervals of time, and not every day, are necessarily
forgotten, and when they are required nobody knows them. But Lord
Melbourne cannot really think that they looked cross; most probably
they did look shy and embarrassed. Strange faces are apt to give the
idea of ill humour....
Lord Melbourne anxiously hopes that your Majesty is well and happy
to-day.
_Viscount Melbourne to Queen Victoria._
SOUTH STREET, _5th September 1841._
Lord Melbourne presents his humble duty to your Majesty. Your Majesty
may depend upon it, that if Lord Melbourne hears anything respecting
your Majesty, which it appears to him to be important or advantageous,
that your Majesty should know, Lord Melbourne will not fail to convey
it to your Majesty.
Lord Melbourne encloses the exact names of the two gentlemen to whom
Knighthood has been promised by your Majesty....
Your Majesty is very good, very good indeed, to think of doing what
your Majesty mentions for Fanny; but Lord Melbourne fears that it
would hardly suit with their present situation, or with the comfort of
their domestic life. But Lord Melbourne mentioned the matter yesterday
to his sister, and he encloses the letter which she has written to him
this morning, after reflecting upon the subject. By that letter your
Majesty will perceive that Jocelyn is not so much in debt, as Lord
Melbourne's letter had led your Majesty to suppose....
Lord B---- is a very old friend of Lord Melbourne's. They were at Eton
together, and intimate there. He is a gentlemanly man and a good man,
but not very agreeable. Few of the P----s are, and very bitter in
politics; but still Lord Melbourne is glad, for old acquaintance'
sake, that your Majesty has taken him. Lord Melbourne must again
repeat that when he writes with so much freedom about individual
characters, it is only to put your Majesty in possession of what he
knows respecting them, and not with a view of inducing your Majesty to
object to their being appointed....
Might not Fanny have the Bedchamber Woman's place? It would be a help
to her, and would not take her away from home. This only strikes Lord
Melbourne as he is writing.
[Pageheading: MELBOURNE ON PEEL]
_6th September 1841._
Lord Melbourne wrote the above yesterday, but had no opportunity of
sending it, as there was no post. Lord Melbourne has since seen Lady
Palmerston, and finds that his last suggestion about Fanny will not
do.
Lord Melbourne encloses Lady Palmerston's two notes upon the subject,
which will explain to your Majesty what she wishes. But if Jocelyn is
himself to get a place, this will be a better arrangement, and puts an
end to all the others.
What Lady Palmerston says about Sir R. Peel is very unjust. There
is no shabbiness whatever in his not coming to a decision upon the
factory question.[87]
[Footnote 87: Lady Palmerston (no doubt in sympathy with Lord
Ashley) expected some factory legislation to be announced.]
_Queen Victoria to the Countess of Gainsborough._[88]
CLAREMONT, _6th September 1841._
MY DEAREST LADY GAINSBOROUGH,--I had the pleasure of receiving your
two kind letters of the 24th and 25th ult. yesterday, and thank you
much for them. I am so happy that you are _really_ better....
I hoped that you would be pleased at what you thank me for; you see
I _did not_ forget what you told me once at Windsor when we were
out driving, and I assure you that Lord Melbourne was very anxious
to do it. Last week was a most painful, trying one to me, and this
separation from my truly excellent and kind friend Lord Melbourne,
_most_ distressing. You will understand _what_ a change it must be to
me. I am, however, so happy in my home, and have such a perfect angel
in the Prince, who has been such a comfort to me, that one must be
thankful and grateful for these blessings, and take these hard trials
as lessons sent from above, for our best.
Our little girl makes great progress, and suffers comparatively but
very little from her teething. We came here to be _quiet_ for a few
days, as this place is so very private.
The Baroness will write to Lord Gainsborough to say that I wish much
you would take Lady Lyttelton's waiting, which begins on 23rd of
November.
The Prince begs to be kindly named to you, and I to Fanny and your
brother, and pray believe me always, dearest Lady Gainsborough, ever
yours most affectionately,
VICTORIA R.
Pray thank Fanny for her kind letter.
[Footnote 88: Formerly, as Lady Barham, a Lady of the
Bedchamber. Lord Barham had been created Earl of Gainsborough
in the course of the year (1841).]
[Pageheading: LORD CHAMBERLAIN'S DEPARTMENT]
_Queen Victoria to Sir Robert Peel._
_7th September 1841._
The Queen wishes that Sir Robert Peel would mention to Lord De la
Warr[89] that he should be very particular in always naming to the
Queen any appointment he wishes to make in his department, and always
to take her pleasure upon an appointment before he settles on them;
this is a point upon which the Queen has always laid great stress.
This applies in great measure to the appointment of Physicians and
Chaplains, which used to be very badly managed formerly, and who were
appointed in a very careless manner; but since the Queen's accession
the Physicians and Chaplains have been appointed only for merit and
abilities, by the Queen herself, which the Queen is certain Sir Robert
Peel will at once see is a far better way, and one which must be of
use in every way. Sir Robert Peel may also tell Lord De la Warr that
it is unnecessary for him to appear in uniform, as the Queen
always dispenses with this in the country. This applies also to the
Ministers, who the Queen does not expect or wish should appear in
uniform at Councils which are held in the country. The Queen concludes
that it will be necessary to hold a Council some time next week to
swear in some of the new Officers who are not Privy Councillors; but
Sir Robert Peel will be able to tell the Queen when he thinks this
will be necessary.
[Footnote 89: See _ante_, p 156.(Ch. VIII, 7th May, 1839)]
[Pageheading: DIPLOMATIC APPOINTMENTS]
_Queen Victoria to Sir Robert Peel._
_8th September 1841._
There is a subject which the Queen wishes to mention to Sir Robert
Peel, as she is at present so little acquainted with Lord Aberdeen;
the Queen is very desirous that, if it were possible, Sir Hamilton
Seymour should not be removed from Brussels. The Queen believes that
his political views are not violent either way, and she knows that he
is peculiarly agreeable to her Uncle, which has, therefore, prompted
her to write this to Sir Robert Peel. The Queen seizes the same
opportunity to say that she is also very anxious that a moderate
and conciliatory person should be sent to Lisbon, as it is of great
importance there.
[Pageheading: THE FRENCH AMBASSADOR]
_Queen Victoria to the King of the Belgians._
CLAREMONT, _8th September 1841._
MY DEAREST UNCLE,--I begin my letter to-day, for fear I should have no
time to write to-morrow. Your kind letter gave me great pleasure, and
I must own your silence on all that was going on distressed me very
much! It has been indeed a sad time for me, and I am still bewildered,
and can't believe that my excellent Lord Melbourne is no longer
my Minister, but he will be, as you say, and has _already_ proved
himself, _very_ useful and _valuable_ as my friend out of office.
He writes to me often, and I write to him, and he gives really the
fairest and most impartial advice possible. But after seeing him for
four years, with very few exceptions--_daily_--you may imagine that I
_must_ feel the change; and the longer the time gets since we parted,
the _more_ I feel it. _Eleven days_ was the _longest_ I ever was
without seeing him, and this time will be elapsed on Saturday, so you
may imagine what the change must be. I cannot say what a comfort and
support my beloved Angel is to me, and how well and how kindly
and properly he behaves. I cannot resist copying for you what Lord
Melbourne wrote to me about Albert, the evening after we parted; he
has already praised him greatly to me, before he took leave of me. It
is as follows:
"Lord Melbourne cannot satisfy himself without again stating to your
Majesty in writing what he had the honour of saying to your Majesty
respecting H.R.H. the Prince. Lord Melbourne has formed the highest
opinion of H.R.H.'s judgment, temper, and discretion, and he cannot
but feel a great consolation and security in the reflection that
he leaves your Majesty in a situation in which your Majesty has the
inestimable advantage of such advice and assistance. Lord Melbourne
feels certain that your Majesty cannot do better than have recourse to
it, whenever it is needed, and rely upon it with confidence."
This naturally gave me great pleasure, and made me very proud, as it
comes from a person who is no flatterer, and would not have said it if
he did not think so, or feel so. The new Cabinet you have by this time
seen in the papers.
The Household (of which I send you a list) is well constituted--_for
Tories_.
Lord Aberdeen has written to me to say Bourqueney has announced Ste
Aulaire[90] as Ambassador. This is very well, but let me beg you, for
decency's sake, to stop his coming immediately; if _even not meant_
to, it would have the effect of their sending an ambassador the moment
the Government changed, which would be too marked, and most _offensive
personally_ to _me_. Indeed Guizot behaved very badly about refusing
to sign the Slave Trade Treaty[91] which they had so long ago settled
to do; it is unwise and foolish to irritate the late Government who
may so easily come in again; for Palmerston will _not_ forgive nor
_forget_ offences, and then France would be worse off than before,
with England. I therefore _beg_ you to stop Ste Aulaire for a little
while, else _I_ shall feel it a great personal offence.
_9th._--I have had a letter from Lord Melbourne to-day, who is much
gratified by yours to him.... Now adieu! Believe me, always, your
devoted Niece,
VICTORIA R.
[Footnote 90: See _post_, p. 334. (Ch. X, 1st October, 1841)]
[Footnote 91: A treaty on the subject was signed in London,
on 20th December, between Great Britain, France, Austria,
Prussia, and Russia.]
[Pageheading: QUEEN ADELAIDE]
_Queen Adelaide to Queen Victoria._
SUDBURY HALL, _8th September 1841._
MY DEAREST NIECE,--I have not ventured to disturb you with a letter
since we parted, knowing how fully your time was employed with
business of importance. I cannot any longer now refrain to enquire
after you, after all you have gone through lately, and I must
congratulate you with all my heart on having so well completed your
difficult task.
There is but one voice of praise, I hear, of your perfect composure
and beautiful conduct during the trying scenes of last week. It has
gratified me more than I can express, for I had fully expected it of
you, and it has made me very happy to find that it has been generally
remarked and has given so much satisfaction. Everybody feels deeply
for you, and the devotion and zeal in your service is redoubled by
the interest your trying position has evoked. May our Heavenly Father
support and guide you always as hitherto, is my constant prayer!
I hope that the selection of your Government is to your own
satisfaction, and though the change must have been trying to you, I
trust that you will have perfect confidence in the able men who form
your Council. Our beloved late King's anxious wishes to see Wellington
and Peel again at the head of the Administration is now fulfilled. His
blessing rests upon you.
Excuse my having touched upon this subject, but I could not keep
silent whilst the heart is so full of earnest good wishes for your and
the country's prosperity.
I hope that an article of the newspapers, of the indisposition of your
darling child, is not true, and that she is quite well. God bless and
protect her!...
I am much amused with reading your Life by Miss Strickland,[92] which,
though full of errors, is earnest on the whole, and very interesting
to _me_. However, I wish she would correct the gross errors which
otherwise will go down to posterity. She ought to have taken first
better information before she published her work....
With my affectionate love to dear Prince Albert, believe me ever, my
dearest Niece, your most devoted and affectionate Aunt,
ADELAIDE.
[Footnote 92: Miss Agnes Strickland (1808-1874), who also
edited _Letters of Mary Queen of Scots_, etc.]
_Memorandum by Mr Anson._
CLAREMONT, _9th September 1841._
The Ministerial arrangements are now nearly completed. Writs for new
elections moved last night.
Wrote to Sir Robert, telling him the Queen ought to have heard from
him respecting the adjournment of the House of Commons, instead of
seeing it first in the public papers. Told him also of its being the
Queen's wish that a short report of the debates in each House should
always be sent to Her Majesty, from him in the Commons and from the
Duke of Wellington in the Lords.
The Queen had a letter to-day from the Queen Dowager, which was kindly
meant, but which made Her Majesty rather angry, complimenting Her
Majesty on the good grace with which she had changed her Government,
and saying that the late King's blessing rested upon her for calling
the Duke of Wellington and Peel to her Councils, etc....
[Pageheading: THE QUEEN CRITICISES APPOINTMENTS]
_Queen Victoria to Sir Robert Peel._
_9th September 1841._
The Queen takes this opportunity of writing to Sir Robert Peel
_confidentially_ about another person: this is about Lord ----. The
Queen is strongly of opinion that Lord ---- should _not_ be employed
in any post of importance, as his being so would, in her opinion,
be detrimental to the interests of the country. The Queen wishes Sir
Robert to state this to Lord Aberdeen as her opinion. The Queen is
certain that Sir Robert will take care that it should not be known
generally that this is her opinion, for she is always most anxious to
avoid anything that might appear personal towards anybody. The Queen
cannot refrain from saying that she cannot quite approve of Sir
Charles Bagot's appointment,[93] as from what she has heard of his
qualities she does not think that they are of a character quite to
suit in the arduous and difficult position in which he will be placed.
At the same time the Queen does not mean to object to his appointment
(for she has already formally approved of it), but she feels it her
duty to state frankly and at all times her opinion, as she begs Sir
Robert also to do unreservedly to her. For the future, it appears to
the Queen that it would be best in all appointments of such importance
that before a direct communication was entered into with the
individual intended to be proposed, that the Queen should be informed
of it, so that she might talk to her Ministers fully about it; not
because it is likely that she would object to the appointment, but
merely that she might have time to be acquainted with the qualities
and abilities of the person. The Queen has stated this thus freely to
Sir Robert as she feels certain that he will understand and appreciate
the motives which prompt her to do so. The Queen would wish the
Council to be at two on Tuesday, and she begs Sir Robert would inform
her which of the Ministers besides him will attend.
[Footnote 93: As Governor-General of Canada.]
_Sir Robert Peel to Queen Victoria._
_9th September 1841._
... Sir Robert Peel will have the honour of writing to your Majesty
to-morrow on the subjects adverted to in the note which he has just
received from your Majesty.
He begs for the present to assure your Majesty that he shall consider
every communication which your Majesty may be pleased to address
to him in reference to the personal merits or disqualifications of
individuals as of a most confidential character.
[Pageheading: PEEL APOLOGISES]
_Sir Robert Peel to Mr Anson._
WHITEHALL, _10th September 1841._
MY DEAR SIR,--I am sorry if I have failed to make any communication to
Her Majesty respecting public matters, which Her Majesty has been in
the habit of receiving, or which she would have wished to receive.
Having been occupied in the execution of the important trust committed
to me not less than sixteen or eighteen hours of the twenty-four for
several days past, it may be that I have made some omissions in this
respect, which under other circumstances I might have avoided. I did
not think Her Majesty would wish to be informed of the issue of writs,
necessarily following the appointments to certain offices, of all
which Her Majesty had approved. I certainly ought to have written
to Her Majesty previously to the adjournment of the House of Commons
until Thursday the _16th of September_. It was an inadvertent omission
on my part, amid the mass of business which I have had to transact,
and I have little doubt that if I had been in Parliament I should have
avoided it.
The circumstances of my having vacated my seat, and of having
thus been compelled to leave to others the duty of proposing the
adjournment of the House, was one cause of my inadvertence.
Both the Duke of Wellington and I fully intended to make a report to
Her Majesty after the close of the Parliamentary business of each day,
and will do so without fail on the reassembling of Parliament.
I am, my dear Sir, very faithfully yours,
ROBERT PEEL.
[Pageheading: DIPLOMATIC APPOINTMENTS]
_Viscount Melbourne to Queen Victoria._
SOUTH STREET, _10th September 1841._
... Lord Melbourne has no doubt that Sir Robert Peel has the most
anxious wish to do everything that can be agreeable to your Majesty.
Your Majesty should not omit to speak fully and seriously to him upon
the disposal of great appointments. Their Diplomatic Corps, from which
Ambassadors and Governors are generally taken, is the weakest part of
their establishment. They have amongst them men of moderate abilities
and of doubtful integrity, who yet have held high offices and
have strong claims upon them. The public service may suffer most
essentially by the employment of such men. Lord Melbourne would say
to Peel that "affairs depend more upon the hands to which they are
entrusted than upon any other cause, and that you hope he will well
consider those whose appointment to high and important situations
he sanctions, and that he will not suffer claims of connection or of
support to overbalance a due regard for your Majesty's service and the
welfare of the country." Such an expression of your Majesty's opinion
may possibly be a support to Sir Robert Peel against pretensions which
he would be otherwise unable to resist; but this is entirely submitted
to your Majesty's judgment, seeing that your Majesty, from an exact
knowledge of all that is passing, must be able to form a much more
correct opinion of the propriety and discretion of any step than Lord
Melbourne can do....
Lord Melbourne has a letter from Lord John Russell, rather eager for
active opposition; but Lord Melbourne will write to your Majesty more
fully upon these subjects from Woburn.
[Pageheading: CANADA]
_Viscount Melbourne to Queen Victoria._
WOBURN ABBEY, _12th September 1841._
Lord Melbourne has this morning received your Majesty's letter of
yesterday. Lord Melbourne entirely agrees with your Majesty about
appointments. He knows, as your Majesty does from experience,
that with all the claims which there are to satisfy, with all the
prejudices which are to be encountered, and with all the interests
which require to be reconciled, it is impossible to select the best
men, or even always those properly qualified. He is the last man who
would wish that a Minister who has the whole machine of the Government
before him should be necessarily thwarted or interfered with in the
selection of those whom he may be desirous to employ. Lord Melbourne
would therefore by no means advise your Majesty to throw difficulty in
the way of the diplomatic arrangements which may be proposed, unless
there should be in them anything manifestly and glaringly bad. The
nomination of Lord ---- would have been so, but otherwise it cannot
very greatly signify who is the Ambassador at Vienna, or even at
Petersburg or Paris. Stuart de Rothesay[94] and Strangford[95] are not
good men, either of them, but it will be difficult for Lord Aberdeen
to neglect their claims altogether. Heytesbury[96] is an able man, the
best they have. Sir Robert Gordon[97] is an honest man, slow but not
illiberal. It would be well if your Majesty showed Lord Aberdeen that
you know these men, and have an opinion upon the subject of them.
Canada is another matter. It is a most difficult and most hazardous
task. There has been recent rebellion in the country. A new
Constitution has lately been imposed upon it by Parliament. The two
Provinces have been united, and the united Province is bordered by a
most hostile and uncontrollable community, the United States of North
America. To govern such a country at such a moment requires a man of
great abilities, a man experienced and practical in the management
of popular assemblies.... It is possible that matters may go smoothly
there, and that if difficulties do arise Sir C. Bagot may prove more
equal to them than from his general knowledge of his character Lord
Melbourne would judge him to be....
Upon the subject of diplomatic appointments Lord Melbourne has
forgotten to make one general observation which he thinks of
importance. Upon a change of Government a very great and sudden change
of all or many of the Ministers at Foreign Courts is an evil and to be
avoided, inasmuch as it induces an idea of a general change of policy,
and disturbs everything that has been settled. George III. always set
his face against and discouraged such numerous removals as tending to
shake confidence abroad in the Government of England generally and to
give it a character of uncertainty and instability. It would be well
if your Majesty could make this remark to Lord Aberdeen.
[Footnote 94: The new Ambassador to St Petersburg.]
[Footnote 95: Percy, sixth Viscount Strangford (1780-1855),
formerly Ambassador to Constantinople, whom Byron described as
"Hibernian Strangford, with thine eyes of blue,
And boasted locks of red or auburn hue."]
[Footnote 96: See _post_, p. 329. (Ch. X, 19th September, 1841)]
[Footnote 97: The new Ambassador to Vienna.]
[Pageheading: INDIA AND AFGHANISTAN]
[Pageheading: LORD ELLENBOROUGH'S REPORT]
[Pageheading: INDIAN FINANCES]
_Lord Ellenborough[98] to Queen Victoria._
Lord Ellenborough presents his most humble duty to your Majesty, and
humbly acquaints your Majesty that having, on the morning after the
Council held at Claremont on the third of this month, requested the
clerks of the India Board to put him in possession of the latest
information with respect to the Political, Military, and Financial
affairs of India, he ascertained that on the 4th of June instructions
had been addressed to the Governor-General of India in Council in the
following terms:--"We direct that unless circumstances now unknown to
us should induce you to adopt a different course, an adequate force
be advanced upon Herat, and that that city and its dependencies may be
occupied by our troops, and dispositions made for annexing them to the
kingdom of Cabul."[99]
The last letters from Calcutta, dated the 9th of July, did not
intimate any intention on the part of the Governor-General in
Council of directing any hostile movement against Herat, and the
Governor-General himself having always evinced much reluctance to
extend the operations of the army to that city, it seemed almost
probable that the execution of the orders of the 4th of June would
have been suspended until further communication could be had with the
Home Authorities.
Nevertheless, in a matter of so much moment it did not appear to be
prudent to leave anything to probability, and at Lord Ellenborough's
instance your Majesty's confidential servants came to the conclusion
that no time should be lost in addressing to the Governor-General in
Council a letter in the following terms--such letter being sent, as
your Majesty must be aware, not directly by the Commissioners for the
Affairs of India, but, as the Act of Parliament prescribes in affairs
requiring secrecy, by their direction through and in the name of the
Secret Committee of the Court of Directors:--
"From the Secret Committee of the Court of Directors of the East India
Company to the Governor-General of India in Council.
"Her Majesty having been pleased to form a new Administration, we
think it expedient that no step should be taken with respect to
Herat which would have the effect of compelling the prosecution of a
specific line of Policy in the countries beyond the Indus, until
the new Ministers shall have had time to take the subject into their
deliberate consideration, and to communicate to us their opinions
thereupon.
"We therefore direct that, unless you should have already taken
measures in pursuance of our Instructions of the 4th of June
1841--which commit the honour of your Government to the prosecution
of the line of Policy which we thereby ordered you to adopt, or which
could not be arrested without prejudice to the Public interests, or
danger to the troops employed--you will consider those Instructions to
be suspended.
"We shall not fail to communicate to you at an early period our fixed
decision upon this subject."
It was not possible to bring this subject before your Majesty's
confidential servants before the afternoon of Saturday the 4th. The
mail for India, which should have been despatched on the 1st, had been
detained till Monday the 6th by the direction of your Majesty's late
Ministers, in order to enable your Majesty's present servants to
transmit to India and China any orders which it might seem to them
to be expedient to issue forthwith. Further delay would have been
productive of much mercantile inconvenience, and in India probably of
much alarm. In this emergency your Majesty's Ministers thought
that your Majesty would be graciously pleased to approve of their
exercising at once the power of directing the immediate transmission
to India of these Instructions.
Your Majesty must have had frequently before you strong proofs of
the deep interest taken by Russia in the affairs of Herat, and your
Majesty cannot but be sensible of the difficulty of maintaining in
Europe that good understanding with Russia which has such an important
bearing upon the general peace, if serious differences should exist
between your Majesty and that Power with respect to the States of
Central Asia.
But even if the annexation of Herat to the kingdom of Cabul were
not to have the effect of endangering the continuance of the good
understanding between your Majesty and Russia, still your Majesty will
not have failed to observe that the further advance of your Majesty's
forces 360 miles into the interior of Central Asia for the purpose
of effecting that annexation, could not but render more difficult
of accomplishment the original intention of your Majesty, publicly
announced to the world, of withdrawing your Majesty's troops from
Afghanistan as soon as Shah Sooja should be firmly established upon
the throne he owes to your Majesty's aid.
These considerations alone would have led Lord Ellenborough to desire
that the execution of the orders given on the 4th of June should at
least be delayed until your Majesty's confidential servants had had
time to consider maturely the Policy which it might be their duty to
advise your Majesty to sanction with respect to the countries on the
right bank of the Indus; but financial considerations strengthened
this desire, and seemed to render it an imperative duty to endeavour
to obtain time for mature reflection before any step should be taken
which might seriously affect the tranquillity of Europe, and must
necessarily have disastrous effects upon the Administration of India.
It appeared that the political and military charges now incurred
beyond the Indus amounted to £1,250,000 a year--that the estimate of
the expense of the additions made to the Army in India, since April
1838, was £1,138,750 a year, and that the deficit of Indian Revenue
in 1839-40 having been £2,425,625, a further deficit of £1,987,000 was
expected in 1840-41.
Your Majesty must be too well informed of the many evils consequent
upon financial embarrassment, and entertains too deep a natural
affection for all your Majesty's subjects, not to desire that in
whatever advice your Majesty's confidential servants may tender to
your Majesty with respect to the Policy to be observed in Afghanistan,
they should have especial regard to the effect which the protracted
continuance of military operations in that country, still more any
extension of them to a new and distant field, would have upon the
Finances of India, and thereby upon the welfare of eighty millions of
people who there acknowledge your Majesty's rule.
[Footnote 98: President of the Board of Control.]
[Footnote 99: For the progress of affairs in Afghanistan,
_see_ Introductory Notes for 1839-1842.
(to Ch. VIII; Ch. IX; Ch. X; Ch. XI)]
_Queen Victoria to Lord Ellenborough._
WINDSOR CASTLE, _19th September 1841._
The Queen thanks Lord Ellenborough for this clear and interesting
Memorandum he has sent. It seems to the Queen that the course intended
to be pursued--namely to take time to consider the affairs of India
without making any precipitate change in the Policy hitherto pursued,
and without involving the country hastily in expenses, is far the best
and safest.
[Pageheading: DIPLOMATIC APPOINTMENTS]
_Queen Victoria to the Earl of Aberdeen._
WINDSOR CASTLE, _19th September 1841._
In the conversation that the Queen had with Lord Aberdeen last week,
she omitted mentioning two persons to him. The one is Lord Heytesbury;
the Queen believes him to be a very able man, and would it not
therefore be a good thing to employ him in some important mission? The
other person is Mr Aston, who is at Madrid; the Queen hopes it may be
possible to leave him there, for she thinks that he acted with great
discretion, prudence, and moderation since he has been there, and the
post is one of considerable importance. He was, the Queen believes,
long Secretary to the Legation at Paris.
_The Earl of Aberdeen to Queen Victoria._
FOREIGN OFFICE, _21st September 1841._
Lord Aberdeen presents his most humble duty to your Majesty....
Lord Aberdeen has seen the favourable opinion which your Majesty has
been graciously pleased to express of Lord Heytesbury, and he humbly
presumes to think that this honour is not unmerited. The situation
of Governor-General of India has recently been proposed by Sir Robert
Peel for Lord Heytesbury's acceptance, which has been declined by him,
and it is understood that Lord Heytesbury is not at present desirous
of public employment.[100]
Your Majesty's servants have not yet fully considered the propriety
of submitting to your Majesty any proposal of a change in the Spanish
Mission; but the opinion which your Majesty has been pleased to
signify respecting the conduct of Mr Aston at Madrid appears, in
the humble judgment of Lord Aberdeen, to be fully confirmed by the
correspondence in this Office.
Lord Aberdeen would, however, venture humbly to mention that the
person filling this Mission has usually been replaced on a change of
the Administration at home. Should this be the case in the present
instance, Lord Aberdeen begs to assure your Majesty that the greatest
care will be taken to select an individual for your Majesty's
approbation who may be qualified to carry into effect the wise, just,
and moderate policy which your Majesty has been graciously pleased to
recognise in the conduct of Mr Aston.
[Footnote 100: He was made Governor and Captain of the Isle of
Wight, and Governor of Carisbrooke Castle.]
[Pageheading: MELBOURNE AND PEEL]
_Memorandum by Mr Anson._
ROYAL LODGE, _21st September 1841._
Saw Baron Stockmar this morning at the Castle, and had a good deal of
conversation with him on various matters. He is very apprehensive that
evil will spring out of the correspondence now carried on between the
Queen and Lord Melbourne. He thinks it is productive of the greatest
possible danger, and especially to Lord Melbourne; he thought no
Government could stand such undermining influence. I might tell this
to Lord Melbourne, and say that if he was totally disconnected from
his Party, instead of being the acknowledged head, there would not
be the same objection. He said, Remind Lord Melbourne of the time
immediately after the Queen's accession, when he had promised the King
of the Belgians to write to him from time to time an account of all
that was going on in this country; and upon Lord Melbourne telling
him of this promise, he replied, This will not do. It cannot be kept a
secret that you keep up this correspondence, and jealousy and distrust
will be the fruit of a knowledge of it. "Leave it to me," he said, "to
arrange with the King; you cease to write, and I will put it straight
with the King."
The Baron seemed to expect Lord Melbourne to draw the inference from
this that a correspondence between Lord Melbourne and the Queen was
fraught with the same danger, and would, when known, be followed
by distrust and jealousy on the part of Sir Robert Peel. I said I
reconciled it to myself because I felt that it had been productive of
much good and no harm--and that, feeling that it was conducted on
such honourable terms, I should not, if it were necessary, scruple to
acquaint Sir Robert Peel of its existence. The Baron said, "Ask Lord
Melbourne whether he would object to it." He said Peel, when he heard
it, would not, on the first impression, at all approve of it; but
prudence and caution would be immediately summoned to his aid, and he
would see that it was his policy to play the generous part--and would
say he felt all was honourably intended, and he had no objection to
offer--"but," said the Baron, "look to the result. Distrust, being
implanted from the first, whenever the first misunderstanding arose,
or things took a wrong turn, all would, in Peel's mind, be immediately
attributed to this cause."
_Queen Victoria to the King of the Belgians._
WINDSOR CASTLE, _24th September 1841._
MY DEAREST UNCLE,--I have already thanked you for your two kind
letters, but I did not wish to answer them but by a Messenger. I feel
thankful for your praise of my conduct; all is going on well, but it
would be needless to attempt to deny that I _feel_ the _change_, and
I own I am much happier when I need _not_ see the Ministers; luckily
they do not want to see me often. I feel much the King's kindness
about Ste Aulaire;[101] I shall see him here on Tuesday next.
I return you our excellent friend Melbourne's letter, which I had
already seen, as he sent it me to read, and then seal and send. I miss
him much, but I often hear from him, which is a great pleasure to me.
It is a great satisfaction to us to have Stockmar here; he is a great
resource, and is now in excellent spirits.
Mamma is, I suppose, with you now, and we may expect her here either
next Thursday or Friday. How much she will have to tell us! I am very
grateful for what you say of Claremont, which could so easily be
made perfect; and I must say we enjoy ourselves there always
_particulièrement_.... Albert begs me to make you his excuses for not
writing, but I can bear testimony that he really has not time to-day.
And now _addio!_ dearest Uncle, and pray believe me, always, your
devoted Niece,
VICTORIA R.
[Footnote 101: See _post_, p. 334. (Ch. X, 1st October, 1841)]
[Pageheading: FINE ARTS COMMISSION]
_Sir Robert Peel to Queen Victoria._
_26th September 1841._
Sir Robert Peel presents his humble duty to your Majesty, and begs to
be permitted to submit for your Majesty's consideration a suggestion
which has occurred to Sir Robert Peel, and which has reference to
the communication which he recently addressed to your Majesty on
the subject of the promotion of the Fine Arts in connection with the
building of the new Houses of Parliament.
Sir Robert Peel would humbly enquire from your Majesty whether (in
the event of your Majesty's being graciously pleased to approve of the
appointment of a Royal Commission for the further investigation and
consideration of a subject of such deep importance and interest to
the encouragement of art in this country) your Majesty would deem
it desirable that the Prince should be invited in the name of your
Majesty to place himself at the head of this Commission, and to give
to it the authority and influence of his high name, and the advantage
of his taste and knowledge.
Sir Robert Peel will not of course mention this subject to any
one, until he has had the honour of receiving from your Majesty an
intimation of your Majesty's opinions and wishes on this subject.
[Pageheading: DIPLOMATIC APPOINTMENTS]
_Viscount Melbourne to Queen Victoria._
SOUTH STREET, _28th September 1841._
... The diplomatic appointments are as well as they could be made.
At least Lord Melbourne thinks so--at least as much in consequence
of those whom they exclude, as of those whom they admit. The Duke of
Beaufort will do better for Petersburg than for Vienna. He is hardly
equal to the place, which requires a clever man, it being more
difficult to get information there, and to find out what is going on,
than in any other country in Europe.... But Lord Melbourne does not
much regard this, and the Duke of Beaufort possesses one advantage,
which is of the greatest importance in that country. He is a soldier,
was the Duke of Wellington's Aide-de-Camp, and served during much of
the Peninsular War. He will therefore be able to accompany the Emperor
to reviews, and to talk with him about troops and man[oe]uvres. Sir
Robert Gordon and Sir S. Canning will do very well.[102]
Lord Melbourne is very glad to hear that your Majesty was pleased and
impressed with Archdeacon Wilberforce's[103] sermon and his manner of
delivering it. Lord Melbourne has never seen nor heard him. His father
had as beautiful and touching a voice as ever was heard. It was very
fine in itself. He spoiled it a little by giving it a methodistical
and precatory intonation.
Hayter has been to Lord Melbourne to-day to press him to sit to him,
which he will do as soon as he has done with Chantrey. Chantrey says
that all Lord Melbourne's face is very easy except the mouth. The
mouth, he says, is always the most difficult feature, and he can
rarely satisfy himself with the delineation of any mouth, but Lord
Melbourne's is so flexible and changeable that it is almost impossible
to catch it.
[Footnote 102: For Vienna and Constantinople.]
[Footnote 103: Samuel, son of William Wilberforce, at this
date Archdeacon of Surrey, and chaplain to Prince Albert;
afterwards, in 1844, appointed Bishop of Oxford, and
eventually translated to the See of Winchester.]
[Pageheading: MELBOURNE'S ADVICE]
_Viscount Melbourne to Queen Victoria._
SOUTH STREET, _1st October 1841._
Lord Melbourne presents his humble duty to your Majesty. He received
your Majesty's letter yesterday evening, and cannot express to your
Majesty how much obliged he feels by your Majesty's taking the trouble
to give him so much information upon so many points. Ste Aulaire's
hair-powder seems to make a very deep and general impression.[104]
Everybody talks about it. "He appears to be very amiable and
agreeable," everybody says, but then adds, "I never saw a man wear so
much powder." A head so whitened with flour is quite a novelty and a
prodigy in these times. Lord Melbourne has not yet seen him, but means
to call upon him immediately. Lord Melbourne is upon the whole
glad that the Duke of Beaufort has declined St Petersburg. It is an
appointment that might have been acquiesced in, but would not have
been approved. Bulwer[105] will not be a bad choice to accompany Sir
Charles[106] to Canada. Your Majesty knows Bulwer well. He is clever,
keen, active; somewhat bitter and caustic, and rather suspicious. A
man of a more straightforward character would have done better, but
it would be easy to have found many who would have done worse. Lord
Melbourne is very glad that it has been offered to the Prince to be at
the head of this Commission, and that His Royal Highness has accepted
it. It is an easy, unexceptionable manner of seeing and becoming
acquainted with a great many people, and of observing the mode of
transacting business in this country. The Commission itself will be
a scene of very considerable difference of opinion. Lord Melbourne
is for decorating the interior of the Houses of Parliament, if it be
right to do so, but he is not for doing it, whether right or wrong,
for the purpose of spending the public money in the encouragement of
the Fine Arts. Whether it is to be painting or sculpture, or both; if
painting, what sort of painting, what are to be the subjects chosen,
and who are to be the artists employed? All these questions furnish
ample food for discussion, difference, and dispute. Chantrey says
fresco will never do; it stands ill in every climate, will never stand
long in this, even in the interior of a building, and in a public work
such as this is, durability is the first object to be aimed at. He
says that there is in the Vatican a compartment of which the middle
portion has been painted by Giulio Romano[107] in fresco, and at each
of the ends there is a figure painted by Raphael in oil. The fresco
painting has been so often repaired in consequence of decay, that not
a vestige of the original work remains; while the two figures painted
by Raphael in oil still stand out in all their original freshness, and
even improved from what they were when first executed....
Lord Melbourne dined and slept on Wednesday at Wimbledon.[108] He
met there Lord and Lady Cottenham, Lord[109] and Lady Langdale, Lord
Glenelg and his brother, Mr Wm. Grant, who was his private secretary,
and is an amusing man. Lord Melbourne is going there again to-morrow
to stay until Monday. The place is beautiful; it is not like
Claremont, but it is quite of the same character, and always puts Lord
Melbourne in mind of it. The Duchess has many merits, but amongst them
is the not small one of having one of the best cooks in England.
[Footnote 104: Madame de Lieven wrote to Aberdeen, 12th
September 1841: "Ne jugez pas cet Ambassadeur par son
exterieur; il personnifie un peu les Marquis de Molière....
Passez-lui ses cheveux poudrés, son air galant et papillon
auprès des femmes. He cannot help it."]
[Footnote 105: Sir Henry Bulwer, afterwards Lord Dalling.]
[Footnote 106: Sir Charles Bagot.]
[Footnote 107: He was a pupil of Raphael, celebrated for
(among other works) his "Fall of the Titans."]
[Footnote 108: The word is almost illegible. Wimbledon was at
that time in the occupation of the Duke of Somerset.]
[Footnote 109: Master of the Rolls.]
[Pageheading: PEERS AND AUDIENCES]
_Sir James Graham to Queen Victoria._
WHITEHALL, _2nd October 1841._
Sir James Graham with humble duty begs to lay before your Majesty two
letters, which he has received from the Earl of Radnor,[110] together
with the copy of the answer which Sir James Graham returned to the
first of the two letters.
If the presentation of Petitions were the sole subject of the
Audience, it might be needless to impose on your Majesty the
trouble incident to this mode of receiving them, since they might be
transmitted through the accustomed channel of one of the Secretaries
of State; but Sir James Graham infers from a conversation which,
since the receipt of the letters he has had with Lord Radnor, that
the Audience is asked in exercise of a right claimed by Peers of the
Realm.
The existence of this right is not recognised by Statute; but it
rests in ancient usage, and is noticed by Judge Blackstone in his
Commentaries on the Laws of England in the following terms:--
"It is usually looked upon to be the right of each particular Peer of
the Realm to demand an Audience of the King, and to lay before him,
with decency and respect, such matters as he shall judge of importance
to the public weal."
The general practice on the part of the Sovereign has been not to
refuse these Audiences when Peers have asked them....
The above is humbly submitted by your Majesty's dutiful Subject and
Servant,
J. R. G. GRAHAM.
[Footnote 110: William, third Earl, formerly M.P. for
Salisbury.]
_Queen Victoria to Sir James Graham._
WINDSOR CASTLE, _3rd October 1841._
The Queen has received Sir James Graham's communication with the
enclosures. She thinks that it would be extremely inconvenient if
Audiences were to be granted to Peers for the purpose of presenting
Petitions or Addresses. The Queen knows that it has always been
considered a sort of right of theirs to ask for and receive an
Audience of the King or Queen. But the Queen knows that upon several
occasions Lord Melbourne and Lord John Russell wrote to the Peers who
requested Audiences, stating that it would be very inconvenient for
the Queen, particularly in the country, and that they had better
either put off asking for it, till the Queen came to town, or send
what they had to say; communicate in writing--which was complied with.
If, therefore, Sir James Graham would state this to Lord Radnor, he
may probably give up pressing for an Audience. Should he, however,
urge his wish very strongly, the Queen will see him in the manner
proposed by Sir James. The Queen would wish to hear from Sir James
again before she gives a final answer.
[Pageheading: THE CHINESE CAMPAIGN]
_Lord Ellenborough to Queen Victoria._
INDIA BOARD, _2nd October 1841._
Lord Ellenborough, with his most humble duty to your Majesty, humbly
acquaints your Majesty that your Majesty's Ministers, taking into
consideration the smallness of the force with which the campaign in
China was commenced this year, and the advanced period of the season
at which the reinforcements would arrive (which reinforcements would
not so raise the strength of the Army as to afford any reasonable
expectation that its operations will produce during the present year
any decisive results), have deemed it expedient that instructions
would be at once issued to the Indian Government with a view to the
making of timely preparations for the campaign of 1842.[111]
Your Majesty's Ministers are of opinion that the War with China should
be conducted on an enlarged scale, and the Indian Government will
be directed to have all their disposable military and naval force
at Singapore in April, so that the operations may commence at the
earliest period which the season allows.
Lord Ellenborough cannot but entertain a sanguine expectation that
that force so commencing its operations, and directed upon a point
where it will intercept the principal internal communication of the
Chinese Empire, will finally compel the Chinese Government to accede
to terms of Peace honourable to your Majesty, and affording future
security to the trade of your Majesty's subjects.
[Footnote 111: Ningpo was taken by Sir Hugh Gough on 13th
October 1841, and no further operations took place till the
spring of the following year. _See_ Introductory Note, _ante_,
p. 254. (Intro Note to Ch. X)]
_Memorandum by Mr Anson._
WINDSOR CASTLE, _3rd October 1841._
Sat by the Queen last night at dinner. Her Majesty alluded to Sir
Robert Peel's awkward manner, which she felt she could not get over.
I asked if Her Majesty had yet made any effort, which I was
good-humouredly assured Her Majesty "thought she really had done."
Sir Robert's ignorance of character was most striking and
unaccountable; feeling this, made it difficult for Her Majesty to
place reliance upon his judgment in recommendations.
[Pageheading: ENGLISH AND FOREIGN ARTISTS]
[Pageheading: SIR FRANCIS CHANTREY]
_Viscount Melbourne to Queen Victoria._
SOUTH STREET, _4th October 1811._
Lord Melbourne presents his humble duty to your Majesty. He had the
honour of receiving your Majesty's letter of the 2nd inst. yesterday,
at Wimbledon. If Lord Melbourne should hear of anything of what your
Majesty asks respecting the impression made upon Sir Robert and Lady
Peel, he will take care and inform your Majesty, but, of course,
they will speak very favourably, and if they feel otherwise will not
breathe it except in the most secret and confidential manner.
Lord Melbourne is very much rejoiced to hear that the Duchess of Kent
arrived safe and well and in good spirits.
Lord Melbourne sat to Sir F. Chantrey on Saturday last. He will, Lord
Melbourne believes, require only one more sitting, which he wishes to
be at the distance of a week from the last, in order that he may
take a fresh view of the bust, and not become reconciled to its
imperfections by continually looking at it. It may give the Prince
some idea of the national feeling which prevails here, when he is told
that Lord Melbourne upon asking Sir F. Chantrey what ought to be done
if foreign artists were employed to paint the Houses of Parliament,
received from him the following answer: "Why, their heads ought to be
broke and they driven out of the country, and, old as I am, I should
like to lend a hand for that purpose."
_Viscount Melbourne to Queen Victoria._
SOUTH STREET, _5th October 1841._
... Lord Melbourne, by telling your Majesty what Sir Francis Chantrey
said respecting foreign artists, and by requesting your Majesty to
repeat it to the Prince, by no means intended to imply that there was
any disposition on the part of His Royal Highness to recommend the
employment of foreigners. He only meant to convey the idea of the
strength of the prejudice which is felt by enlightened and able men
upon the subject. Lord Melbourne has been sitting this morning to
Hayter for the picture of the marriage, and he (Hayter) held an
entirely contrary language. His tone is: "If foreign artists are more
capable than English, let them be employed. All I require is that the
work should be done as well as it can be." The English are certainly
very jealous of foreigners, and so, Lord Melbourne apprehends, are
the rest of mankind, but not knowing himself any nation except the
English, he cannot venture to make positively that assertion. Lord
Melbourne has been reading the evidence given before the committee of
the House of Commons upon this subject. It is well worth attention,
particularly Mr Eastlake's,[112] which appears to Lord Melbourne to be
very enlightened, dispassionate, and just....
[Footnote 112: Afterwards Sir Charles Eastlake, Keeper of the
National Gallery, 1843-1847, President of the Royal Academy,
1850-1865.]
[Pageheading: THE PRINCE'S GRANT]
_Memorandum by Mr Anson._
WINDSOR CASTLE, _6th October 1841._
Sat by Her Majesty last night at dinner.
The Queen had written to Lord Melbourne about coming to the Castle,
but in his answer he had made no allusion to it; she did not know
whether this was accidental or intentional, for he very often gave no
answer to questions which were put.
I told Her Majesty that I feared he had raised an obstacle to his
visit by making a strong speech against the Government just at the
time he was thinking of coming. That this attack had identified him as
the leader of his Party, at a moment when I had been most anxious
that he should abstain from taking an active part, and by withdrawing
himself from politics he would enable himself to become the more
useful friend to Her Majesty. The Queen had not seen the speech,
was sorry he had felt himself obliged to make it, but it would
be difficult for him to avoid it after having been so long Prime
Minister.
Her Majesty told me that previous to the exit of the late Government,
Lord John had earnestly cautioned Her Majesty not to propose any
new grant of money, as it would in the case of £70,000 for the new
stables, however unfairly, bring great unpopularity upon the Queen. I
said in regard to any increase to the Prince's annuity, I thought
it would be very imprudent in him to think of it, except under very
peculiar circumstances which might arise, but which could not yet be
foreseen. The Queen said that _nothing_ should induce Her Majesty to
accept such a favour from these Ministers. Peel probably now regretted
his opposition to the grant, but it was, and was intended to be, a
personal insult to herself, and it was followed up [by] opposition
to her private wishes in the precedency question, where the Duke of
Wellington took the lead against her wishes, as Peel had done in the
Commons against the Prince's grant. She never could forget it, and no
favour to her should come from such a quarter. I told Her Majesty I
could not rest the Prince's case on Her Majesty's objections if they
were the only ones which could be brought forward. If the case again
rose I feared Her Majesty would find many who before, from Party
views, voted according to Her Majesty's wishes, would now rank on the
opposite side.
Her Majesty asked Dr Hawtrey the evening before who was the cleverest
boy at Eton.
Dr Hawtrey made a profound bow to the Queen and said, "I trust your
Majesty will excuse my answering, for if I did I make 600 enemies at
once."
_Memorandum by Baron Stockmar._
_6th October 1841._
The Queen had asked Lord Melbourne whether he would soon visit her at
Windsor. He had not replied on that point, but had written to Prince
Albert in order to learn first the Prince's opinion on the feasibility
of the matter.
The Prince sent for me and consulted with me. I was of opinion that
the Prince had better refrain from giving an answer, and that I should
give my opinion in the written form of a Memorandum, with which Anson
should betake himself to town. He was to read it aloud to Melbourne,
and orally to add what amplifications might be necessary.
And so it was done.
[Pageheading: RELATIONS WITH PEEL]
My Memorandum was as follows:--
Sir Robert Peel has yet to make his position opposite[113] the
Queen, which for him to obtain is important and desirable for
obvious reasons. I have good cause to doubt that Sir Robert
is sure within himself of the good-will and confidence of the
Queen. As long as the secret communication exists between Her
Majesty and Lord Melbourne, this ground, upon which alone Sir
Robert could obtain the position necessary to him as Premier,
must remain cut away from under his feet. I hold, therefore,
this secret interchange an _essential injustice_ to Sir
Robert's present situation. I think it equally wrong to call
upon the Prince to give an opinion on the subject, as he has
not the means to cause his opinion to be either regarded or
complied with. In this particular matter nobody has paramount
power to do right or wrong but the Queen, and more especially
Lord Melbourne himself. To any danger which may come out of
this to Her Majesty's character, the caution and objection
must come from him, and from him alone; and if I was standing
in his shoes I would show the Queen, of my own accord,
and upon constitutional grounds _too_, that a continued
correspondence of that sort must be fraught with imminent
danger to the Queen, especially to Lord Melbourne, and to the
State.
[Footnote 113: _I.e._ with.]
I then gave Anson the further arguments with which he was to accompany
the reading out of this Memo.
[Pageheading: DISCRETION URGED ON MELBOURNE]
[Pageheading: MELBOURNE'S INFLUENCE]
On the next day Anson went to Melbourne and told him that his note to
him had raised a great consultation, that the Prince felt much averse
to giving any opinion in a case upon which he could exercise no
control, and in which, if it was known that he had given his sanction,
he would be held responsible for any mischief which might arise. He
had consulted Baron Stockmar, who had written the enclosed opinion,
which the Prince had desired Anson to read to Lord Melbourne.
Melbourne read it attentively twice through, with an occasional change
of countenance and compression of lips. He said on concluding
it: "This is a most decided opinion indeed, quite an '_apple[114]
opinion_.'" Anson told him that the Prince felt that if the Queen's
confidence in Peel was in a way to be established, it would be
extremely shaken by his (Lord Melbourne's) visit at such a moment. He
felt that it would be better that Lord Melbourne's appearance should
be in London, where he would meet the Queen only on the terms of
general society, but at the same time he (the Prince) was extremely
reluctant to give an opinion upon a case which Lord Melbourne's own
sense of right ought to decide. Anson added how he feared his speech
of yesterday in the House of Lords[115] had added another impediment
to his coming at this moment, as it had identified him with and
established as the head of the Opposition party, which he (Anson) had
hoped Melbourne would have been able to avoid. Melbourne, who was then
sitting on the sofa, rushed up upon this, and went up and down the
room in a violent frenzy, exclaiming--"God eternally d--n it!"
etc., etc. "Flesh and blood cannot stand this. I only spoke upon
the defensive, which Ripon's speech at the beginning of the session
rendered quite necessary. I cannot be expected to give up my position
in the country, neither do I think that it is to the Queen's interest
that I should."
Anson continued that the Baron thought that no Ministry could stand
the force of such an undercurrent influence, that all the good that
was to be derived from pacifying the Queen's mind at the change had
been gained, and that the danger which we were liable to, and which
threatened him in particular, could only be averted by his own
straightforward decision with the Queen. Anson asked him if _he_ saw
any danger likely to arise from this correspondence. After a long
pause he said, "_I certainly cannot think it right_," though he
felt sure that some medium of communication of this sort was no new
precedent. He took care never to say anything which could bring his
opinion in opposition _to Sir Robert's, and he should distinctly
advise the Queen to adhere to her Ministers in everything,[116]
unless he saw the time had arrived at which it might be
resisted_.[117] The principal evil, replied Anson, to be dreaded from
the continuance of Lord Melbourne's influence was, according to the
Baron's opinion, that so long as the Queen felt she could resort to
Lord Melbourne for his advice, she never would be disposed (from not
feeling the necessity) to place any real confidence in the advice she
received from Peel.
[Footnote 114: No doubt Lord Melbourne said an "apple-pie"
opinion.]
[Footnote 115: At the opening of the Session Lord Ripon had
reprobated the late Government for resorting to temporary
expedients, and Lord Melbourne, on the second reading of the
Exchequer-bills Funding Bill, caustically but good-humouredly
replied to the attack.]
[Footnote 116: _Note by Baron Stockmar._--If he wishes to
carry this out consistently and quite honestly, what then is
the value of his advice, if it be only the copy of that of Sir
R. Peel?]
[Footnote 117: _Note by Baron Stockmar._--This means, in my
way of reading it: "The Queen, by her correspondence with
me, puts Peel into my hands, and there I mean to let him stay
unhurt, until time and extraneous circumstances--but more
especially the advantage that will accrue to me by my secret
correspondence with the Queen--shall enable me to plunge, in
all security, the dagger into his back."]
_The Earl of Liverpool to Baron Stockmar._[118]
FIFE HOUSE, _7th October 1841._
MY DEAR BARON,--Peel sent for me this morning to speak to me about
the contents of his letter to me. After some general conversation on
matters respecting the Royal Household, he said that he had had
much satisfaction in his intercourse lately with Her Majesty, and
specifically yesterday, and he asked me whether I had seen Her Majesty
or the Prince yesterday, and whether they were satisfied with him. I
told him that except in public I had not seen Her Majesty, and except
for a moment in your room I had not seen the Prince; but that as he
spoke to me on this matter, I must take the opportunity of saying a
word to him about _you_, from whom I had learnt yesterday that both
the Queen and Prince are extremely well pleased with him. That I
had known you very long, but that our great intimacy began when King
Leopold sent you over just previous to the Queen's accession; that we
had acted together on that occasion, and that our mutual esteem and
intimacy had increased; that your position was a very peculiar one,
and that you might be truly said to be a species of second parent to
the Queen and the Prince; that your only object was their welfare, and
your only ambition to be of service to them; that in this sense you
had communicated with Melbourne, and that I wished that in this sense
you should communicate with him (Peel). He said that he saw the matter
exactly as I did, that he wished to communicate with you, and felt the
greatest anxiety to do everything to meet the wishes of the Queen and
Prince in all matters within his power, and as far as consistent
with his known and avowed political principles; that in all matters
respecting the Household and their private feelings that the smallest
hint sufficed to guide him, as he would not give way to any party
feeling or job which should in any way militate against Her Majesty
or His Royal Highness's comfort; that he wished particularly that it
should be known that he never had a thought of riding _roughshod_ over
Her Majesty's wishes; that if you would come to him at any time, and
be candid and explicit with him, you might depend upon his frankness
and discretion; that above all, if you had said anything to him, and
expressed a wish that it might not be communicated even to the Duke of
Wellington, (that was his expression), that he wished me to assure you
that your wishes should be strictly attended to. Pray give me a line
to say that you do not disapprove of what I have done. We had a great
deal more conversation, but with this I will not now load my letter,
being ever sincerely yours,
LIVERPOOL.
Direct your answer to this house.
[Footnote 118: This letter was submitted to the Queen.]
[Pageheading: AUDIENCES OF PEERS]
_Viscount Melbourne to Queen Victoria._
SOUTH STREET, _8th October 1841._
Lord Melbourne presents his humble duty to your Majesty. He has this
morning received your Majesty's letter of yesterday. There can be no
doubt that your Majesty is right about the Audiences which have been
requested....
Sir Robert Peel is probably right in supposing that the claim of a
Peer to an Audience of the Sovereign originated in early times, and
before the present course of government by responsible advisers was
fully and decidedly established, which it hardly can be said to have
been until after the accession of the House of Hanover, but the custom
of asking for such Audiences, and of their being in general granted,
was well known, and has for the most part been observed and adhered
to. Lord Melbourne remembers that during the part of the French War,
when considerable alarm began to prevail respecting its duration, and
the serious aspect which it was assuming, George III. gave Audiences
to the Duke of Norfolk and others which he certainly would not have
been inclined to do if he had not thought himself bound by his duty
and by Constitutional precedent. At the time of the passing of the
Roman Catholic Relief Act, George IV. received very many Peers, much
no doubt against his will, who came to remonstrate with him upon the
course which his Ministers were pursuing. William IV. did the same at
the time of the Reform Bill, and certainly spoke upon the subject in
a manner which Lord Melbourne always thought indiscreet and imprudent.
Upon the whole, the practice has been so much acted upon and
established, that Lord Melbourne will certainly not think it wise to
make any alteration now, especially as it has in itself beneficial
effects, especially as in a time of strong political feeling it is a
satisfaction to the people to think that their wishes and opinions are
laid before the Sovereign fairly and impartially. It is not likely to
be a very heavy burthen, inasmuch as such Audiences are only asked at
particular moments, and they are not in themselves very burthensome
nor difficult to deal with. It is only for the Sovereign to say that
he is convinced of the good motives which have actuated the step, and
that consideration will be given to the matter and arguments which
have been stated.
Lord Melbourne has one vague recollection of a correspondence upon
this subject between Lord Holland and some King, but does not remember
the circumstances with any accuracy.
Duncannon[119] persuaded Brougham to give up asking an Audience upon
condition of Lord Melbourne's promising to place his letters in your
Majesty's hands, which he did.[120] Lord Charlemont[121] also was
prevented in some manner or another, which Lord Melbourne forgets.
Upon the whole, Lord Melbourne thinks that it is best to concede this
privilege of the Peerage, whether it actually exists or not, but to
restrain it within due and reasonable bounds, which in ordinary times
it is not difficult to do. Extraordinary times must be dealt with as
they can be....
Lady A---- is, as your Majesty says, good-natured. She talks three or
four times as much as she ought, and like many such women often says
exactly the things she ought not to say. Lady B---- has ten times the
sense of her mother, and a little residue of her folly.
[Footnote 119: Ex-First Commissioner of Land Revenue.]
[Footnote 120: See _ante_, pp. 293 and 335-6.
(Ch. X, 'Lord Brougham'; 'Peers and Audiences')]
[Footnote 121: Francis William, fifth Viscount Charlemont
(1775-1863), created a Peer of the United Kingdom in 1837.]
[Pageheading: GOVERNOR-GENERALSHIP OF INDIA]
[Pageheading: LORD ELLENBOROUGH]
_Sir Robert Peel to Queen Victoria._
_9th October 1841._
Sir Robert Peel, with his humble duty to your Majesty, begs leave
to inform your Majesty that in consequence of the opinion which your
Majesty was graciously pleased to express when Sir Robert Peel last
had the honour of waiting upon your Majesty, with respect to the
superior qualifications of Lord Ellenborough for the important
trust of Governor-General of India, Sir Robert Peel saw his Lordship
yesterday, and enquired whether he would permit Sir Robert Peel to
propose his appointment to your Majesty.
Lord Ellenborough was very much gratified by the proposal, admitted at
once that it was very difficult to find an unexceptionable candidate
for an office of such pre-eminent importance, but made some difficulty
on two points.
First--Considerations of health, which though disregarded personally,
might, he feared, interfere with the execution of such unremitting and
laborious duties as would devolve upon the Governor-General of India.
Secondly--The consideration that on his acceptance of the office he
would be required by law to give up during his tenure of it no less
than £7,500 per annum, the amount of compensation now paid to him in
consequence of the abolition of a very valuable office[122] which he
held in the Courts of Law.
During Lord Ellenborough's conversation with Sir Robert Peel, and
while the mind of Lord Ellenborough was very much in doubt as to the
policy of his acceptance of the office, the box which contained your
Majesty's note of yesterday was brought to Sir Robert Peel.
Sir Robert Peel humbly acquaints your Majesty that he ventured to read
to Lord Ellenborough on the instant the concluding paragraph of your
Majesty's note, namely--
"The more the Queen thinks of it, the more she thinks that Lord
Ellenborough would be far the most fit person to send to India."
Sir Robert Peel is perfectly convinced that this opinion of your
Majesty, so graciously expressed, removed every doubt and difficulty
from Lord Ellenborough's mind, and decided him to forgo every personal
consideration rather than appear unmindful of such a favourable
impression of his qualifications for public service on the part of his
Sovereign.
Sir Robert Peel humbly hopes that your Majesty will not disapprove of
the use which he made of a confidential note from your Majesty.
As your Majesty kindly permitted Sir Robert Peel to send occasionally
letters to your Majesty of a private rather than a public character,
he ventures to enclose one from the Duke of Wellington on the subject
of the appointment of Governor-General.
Sir Robert Peel had observed to the Duke of Wellington that he
had great confidence in Lord Ellenborough's integrity, unremitting
industry, and intimate knowledge of Indian affairs; that his only
fear was that Lord Ellenborough might err from _over-activity_ and
eagerness--but that he hoped his tendency to hasty decisions would be
checked by the experience and mature judgment of Indian advisers on
the spot.
The Duke of Wellington's comments have reference to these observations
of Sir Robert Peel. Your Majesty will nevertheless perceive that the
Duke considers, upon the whole, "that Lord Ellenborough is better
qualified than any man in England for the office of Governor-General."
[Footnote 122: He was Joint Chief Clerk of the Pleas in the
Queen's Bench, a sinecure conferred on him by his father, who
was Lord Chief Justice of the King's Bench, 1802-1818.]
[Pageheading: AFFAIRS IN SPAIN]
_Queen Victoria to the King of the Belgians._
WINDSOR CASTLE, _12th October 1841._
MY DEAREST UNCLE,--- ... Respecting the Spanish affairs,[123] I can
give you perfectly satisfactory intelligence concerning the Infants'
return. Espartero sees them return with the greatest regret, but said
he felt he could not prevent them from doing so. If, however, they
should be found to intrigue at all, they will not be allowed to
remain. Respecting a marriage with the eldest son of Dona Carlotta, I
know _positively_ that Espartero _never_ would _hear_ of it; but, on
the other hand, he is equally strongly opposed to poor little Isabel
marrying any French Prince, and I must add that _we_ could _never
allow that_. You will see that I have given you a frank and fair
account....
[Footnote 123: The Queen-mother, who was living in Paris, had
been deprived by a vote of the Cortes of the guardianship of
the young Queen, Isabella II., and risings in her interest now
took place at Pampeluna and Vittoria. On the 7th October, a
bold attempt was made at Madrid to storm the Palace and get
possession of the person of the young Queen. Queen Christina
denied complicity, but the Regent, Espartero, suspended
her pension on the ground that she had encouraged the
conspirators.]
_Viscount Melbourne to Queen Victoria._
SOUTH STREET, _12th October 1841._
Lord Melbourne presents his humble duty to your Majesty, and returns
many thanks for the letter received yesterday informing Lord Melbourne
of the time of your Majesty's coming to London. Lord Melbourne
earnestly hopes that your Majesty continues well.
Lord Melbourne is very glad to hear of the appointment of Lord
Ellenborough. The reasons which your Majesty gives are sound and just,
and it is of great importance that a man not only of great ability but
of high station, and perfectly in the confidence of the Government at
home, should be named to this important post. Lord Ellenborough is a
man of great abilities, of much knowledge of India, of great industry
and of very accurate habits of business, and Lord Melbourne knows of
no objection to his appointment, except the loss of him here, where,
whether in or out of office, he has always been of great service.
He has hitherto been an unpopular man and his manners have been
considered contemptuous and overbearing, but he is evidently much
softened and amended in this respect, as most men are by time,
experience, and observation. Lord Fitzgerald[124] is a very able
public man, Lord Melbourne would say one of the most able, if not the
most able they have; but Lord Melbourne is told by others, who know
Lord Fitzgerald better, that Lord Melbourne overrates him. He is a
very good speaker, he has not naturally much industry, and his
health is bad, which will probably disable him from a very close and
assiduous attention to business. It is, however, upon the whole an
adequate appointment, and he is perhaps more likely to go on smoothly
with the Court of Directors, which is a great matter, than Lord
Ellenborough.
[Footnote 124: On Lord Ellenborough becoming Governor-General,
Lord Fitzgerald and Vesci, an ex-M.P., and former Chancellor
of the Irish Exchequer, succeeded him at the Board of
Control.]
[Pageheading: FRANCE AND SPAIN]
_The Earl of Aberdeen to Queen Victoria._
FOREIGN OFFICE, _16th October 1841._
Lord Aberdeen, with his most humble duty, begs to lay before
your Majesty a private letter from M. Guizot, which has just been
communicated to him by M. de Ste-Aulaire, on the recent attempt
in favour of Queen Christina in Spain. Your Majesty will see that
although M. Guizot denies, with every appearance of sincerity, all
participation of the French Government in this attempt, he does not
conceal that it has their cordial good wishes for its success. These
feelings, on the part of such a Government as that of France, will
probably be connected with practical assistance of some kind, although
M. Guizot's declarations may perhaps be literally true.
_Queen Victoria to the Earl of Aberdeen._
The Queen must say that she fears the French are at the bottom of it,
for their jealousy of our influence in Spain is such, that the Queen
fears they would not be indisposed to see civil war to a certain
degree restored rather than that Spain should go on quietly supported
by us.[125] The Queen, however, hopes that, as far as it is possible,
the English Government will support the present Regent, who is
thoroughly attached to England, and who, from all that the Queen
hears of him, is the fittest man they have in Spain for the post he
occupies; and indeed matters till now had gone on much more quietly
than they had for some time previous, since Espartero is at the head
of the Government. The French intrigues should really be frustrated.
The Queen certainly thinks that M. Guizot's veracity is generally not
to be doubted, but the conduct of France regarding Spain has always
been very equivocal.
[Footnote 125: See _post_, p. 349. (Ch. X, 17th October, 1841)]
[Pageheading: MASTERSHIP OF TRINITY]
_Sir Robert Peel to Queen Victoria._
_16th October 1841._
Sir Robert Peel, with his humble duty to your Majesty, begs leave to
acquaint your Majesty that the Master of Trinity College, Cambridge,
has formally signified his wish to retire from the duties of that
important trust.
Sir Robert Peel has reason to believe that it would be advantageous
that the selection of a successor to Dr. Wordsworth should be made
from members of Trinity College who are or have been fellows of the
College. Of these, the most eminent in respect to the qualifications
required in the office of Master, and to academical distinction,
are:--
Professor Whewell.[126]
The Rev. Mr Martin,[127] Bursar of the College.
The Rev. Dr Wordsworth,[128] Head Master of Harrow School,
and son of the present Master of Trinity.
The latter is a highly distinguished scholar, but his success as Head
Master of Harrow has not been such as to overcome the objection which
applies on general grounds to the succession of a father by a son in
an office of this description.
Professor Whewell is a member of Trinity College of the highest
scientific attainments. His name is probably familiar to your Majesty
as the author of one of the Bridgewater Treatises,[129] and of other
works which have attracted considerable notice.
He is a general favourite among all who have had intercourse with him
from his good temper and easy and conciliatory manners. Though not
_peculiarly_ eminent as a divine (less so at least than a writer on
scientific and philosophical subjects), his works manifest a deep
sense of the importance of religion and sound religious views. The
Archbishop of Canterbury[130] and the Bishop of London[131] (himself
of Trinity College) incline to think that the most satisfactory
appointment upon the whole would be that of Professor Whewell.
Sir Robert Peel, after making every enquiry into the subject, and with
a deep conviction of the importance of the appointment, has arrived at
the same conclusion, and humbly therefore recommends to your Majesty
that Professor Whewell should succeed Dr Wordsworth as Master of
Trinity College, Cambridge.
[Footnote 126: Then Knightsbridge Professor of Moral
Philosophy.]
[Footnote 127: Francis Martin, afterwards Vice-Master, died
1868.]
[Footnote 128: Christopher Wordsworth, afterwards Bishop of
Lincoln.]
[Footnote 129: By the will (dated 1825) of the eighth Earl
of Bridgewater--who must not be confounded with the third and
last Duke, projector of inland navigation--£8,000 was left
for the best work on the "Goodness of God as manifested in
the Creation." The money was divided amongst eight persons,
including Whewell, who wrote on Astronomy considered in
reference to Natural Theology.]
[Footnote 130: William Howley.]
[Footnote 131: O. J. Blomfield.]
[Pageheading: QUEEN ISABELLA]
[Pageheading: THE SPANISH MARRIAGE]
_Queen Victoria to the Earl of Aberdeen._
_17th October 1841._
The Queen received Lord Aberdeen's letter yesterday evening, and quite
approves of the draft to Mr Aston, and of Lord Aberdeen's having sent
it off at once. Her earnest wish is that the English Government should
be firm, and uphold the Regent as far as it is in our power. The Queen
has perused M. Guizot's letter with great attention, but she cannot
help fearing that assistance and encouragement has been given in
some shape or other to the revolts which have taken place. The Queen
Christina's residence at Paris is very suspicious, and much to be
regretted; every one who saw the Queen and knew her when Regent, knew
her to be clever and _capable_ of governing, had she but attended
to her duties. This she did not, but wasted her time in frivolous
amusements and neglected her children sadly, and finally left them.
It was her _own_ doing, and therefore it is not the kindest conduct
towards her children, but the very _worst_, to try and disturb the
tranquillity of a country which was just beginning to recover from the
baneful effects of one of the most bloody civil wars imaginable.
The Queen is certain that Lord Aberdeen will feel with her of what
importance it is to England that Spain should not become subject to
French interests, as it is evident _France wishes_ to make it. The
marriage of Queen Isabel is a most important question, and the Queen
is likewise certain that Lord Aberdeen sees at once that we could
never let her marry a French Prince. Ere long the Queen must speak to
Lord Aberdeen on this subject. In the meantime the Queen thought
it might be of use to Lord Aberdeen to put him in possession of her
feelings on the state of Spain, in which the Queen has always taken a
very warm interest.
_Viscount Melbourne to Queen Victoria._
PANSHANGER, _21st October 1841._
Lord Melbourne presents his humble duty to your Majesty. He received
here yesterday your Majesty's letter of the 19th inst., and he
earnestly hopes that your Majesty has arrived quite safe and well in
London. Besides the family, we have had hardly anybody here except
Lady Clanricarde.[132] Yesterday Sir Edward L. Bulwer[133] came,
beating his brother hollow in ridiculousness of attire, ridiculous as
the other is. He has, however, much in him, and is agreeable when you
come to converse with him....
Lord Melbourne is rather in doubt about his own movements. Lord
Leicester[134] presses him much to go to Holkham, where Lord
Fortescue,[135] Mr Ellice[136] and others are to be, and considering
Lord Leicester's age, Lord Melbourne thinks that it will gratify him
to see Lord Melbourne again there. But at Holkham they shoot from
morning until night, and if you do not shoot you are like a fish
upon dry land. Lord Melbourne hardly feels equal to the exertion, and
therefore thinks that he shall establish himself for the present
at Melbourne, where he will be within reach of Trentham, Beau
Desert,[137] Wentworth,[138] and Castle Howard,[139] if he likes to
go to them. The only annoyance is that it is close to Lord and Lady
G----, whom he will be perpetually meeting.
[Footnote 132: A daughter of George Canning, the Prime
Minister.]
[Footnote 133: Afterwards Lord Lytton, the novelist.]
[Footnote 134: The famous country gentleman, "Mr Coke of
Norfolk."]
[Footnote 135: Hugh, second Earl, K.G.]
[Footnote 136: The Right Hon. Edward Ellice, M.P. ("Bear"
Ellice).]
[Footnote 137: Near Lichfield, a seat of Lord Anglesey.]
[Footnote 138: Lord Fitzwilliam's house, near Rotherham.]
[Footnote 139: Lord Carlisle's house, near York, built by
Vanbrugh.]
[Pageheading: HOLLAND AND BELGIUM]
_The King of the Belgians to Queen Victoria._
LAEKEN, _22 October 1841._
... In France there is a great outcry that a Bourbon must be the
future husband of the Queen of Spain, etc. I must say that as the
Spaniards and the late King changed themselves the Salic custom which
Philip V. had brought from France,[140] it is natural for the rest of
Europe to wish that no Bourbon should go there. Besides, it must be
confessed that the thing is not even easy, as there is great hatred
amongst the various branches of that family. The King of the French
himself has always been _opposed_ to the idea of one of his sons going
there; in France, however, that opinion still exists, and Thiers had
it, strongly.
I confess that I regret that Queen Christina was encouraged to
settle at Paris, as it gave the thing the appearance of something
preconcerted. I believe that a wish existed that Christina would
retire peaceably and _par la force des circonstances_, but now this
took a turn which I am sure the King does not like; it places him,
besides, into _une position ingrate_; the Radicals hate him, the
Moderates will cry out that he has left them in the lurch, and the
Carlists are kept under key, and of course also not much pleased. I
meant to have remained in my wilds till yesterday, but my Ministers
were so anxious for my return, there being a good many things on the
_tapis_, that I came back on Tuesday, the 19th....
Here one is exactly shut up as if one was in a menagerie, walking
round and round like a tame bear. One breathes here also a mixture
of all sorts of moist compounds, which one is told is fresh air, but
which is not the least like it. I suppose, however, that my neighbour
in Holland, where they have not even got a hill as high as yours in
Buckingham Gardens, would consider Laeken as an Alpine country. The
tender meeting of the old King and the new King,[141] as one can
hardly call him a young King, must be most amusing. I am told that if
the old King had not made that love-match, he would be perfectly
able to dethrone his son; I heard that yesterday from a person rather
attached to the son and hating the father. In the meantime, though
one can hardly say that he is well at home, some strange mixture of
cut-throats and ruined soldiers of fortune had a mind to play us some
tricks here; we have got more and more insight into this. Is it by
instigation from him personally, or does he only know of it without
being a party to it? That _is_ difficult to tell, the more so as he
makes immense demonstration of friendly dispositions towards us,
and me in particular. I would I could make a _chassez croisez_ with
Otho;[142] he would be the gainer in solids, and I should have sun and
an interesting country; I will try to make him understand this, the
more so as you do not any longer want me in the West.
[Footnote 140: The Pragmatic Sanction of Philip V. was
repealed in 1792 by the Cortes, but the repeal was not
promulgated by the King. Under the Salic Law, Don Carlos would
have been on the throne. See _ante_, p. 44. (Ch. V, Footnote 9)]
[Footnote 141: William I., who had abdicated in order to marry
again, and William II., his son, who was nearly fifty.]
[Footnote 142: The King of Greece, elected in 1833.]
[Pageheading: AMBASSADORS' AUDIENCES]
_Queen Victoria to Sir Robert Peel._
_25th October 1841._
With respect to the appointment of Chief Justice of the Queen's Bench,
the Queen approves of Mr Pennefather[143] for that office. The Queen
may be mistaken, for she is not very well acquainted with the judicial
officers in Ireland, but it strikes her that Serjeant Jackson belonged
to the very violent Orange party in Ireland, and if this should be the
case she suggests to Sir Robert Peel whether it would not be better
_not_ to appoint him. If, on the other hand, the Queen should be
mistaken as to his political opinions, she would not disapprove of his
succeeding Mr Pennefather.
The Queen saw in the papers that Lord Stuart de Rothesay is already
gone. The Queen can hardly believe this, as no Ambassador or Minister
_ever_ left England without previously asking for an Audience and
receiving one, as the Queen wishes always to see them before they
repair to their posts. Would Sir Robert be so very good as to ask Lord
Aberdeen whether Lord Stuart de Rothesay is gone or not, and if he
should be, to tell Lord Aberdeen that in future she would wish
him always to inform her when they intend to go, and to ask for an
Audience, which, if the Queen is well, she would always grant. It is
possible that as the Queen said the other day that she did not wish
to give many Audiences after the Council, that Lord Aberdeen may have
misunderstood this and thought the Queen would give none, which was
_not_ her intention. The Queen would be thankful to Sir Robert if he
would undertake to clear up this mistake, which she is certain (should
Lord Stuart be gone) arose entirely from misapprehension.
The Queen also wishes Sir Robert to desire Lord Haddington to send her
some details of the intended reductions in the Fleet which she sees by
a draft of Lord Aberdeen's to Mr Bulwer have taken place.[144]
[Footnote 143: Recently appointed Solicitor-General; Sergeant
J. D. Jackson now succeeded him.]
[Footnote 144: The statement of the Royal Navy in Commission
at the beginning of 1841 sets out 160 vessels carrying 4,277
guns.]
[Pageheading: STOCKMAR AND MELBOURNE]
[Pageheading: STOCKMAR'S ADVICE]
_Memorandum by Baron Stockmar._
_25th October 1841._
... I told [Lord Melbourne] that, as I read the English Constitution,
it meant to assign to _the Sovereign in his functions a deliberative
part_--that I was not sure the Queen had the means within herself to
execute this deliberative part properly, but I was sure that the only
way for her to execute her functions at all was to be strictly honest
to those men who at the time being were her Ministers. That it was
chiefly on this account that I had been so very sorry to have found
now, on my return from the Continent, that on the change of the
Ministry a capital opportunity to read a great Constitutional maxim
to the Queen had not only been lost by Lord Melbourne, but that he had
himself turned an instrument for working great good into an instrument
which must produce mischief and danger. That I was afraid that, from
what Lord Melbourne had been so weak as to have allowed himself to be
driven into, _against his own and better conviction_, the Queen must
have received a most pernicious bias, which on any future occasion
would make her inclined to act in a similar position similarly to that
what she does now, being convinced that what she does _now_ must be
right on all future occasions, or else Lord Melbourne would not have
sanctioned it. Upon this, Lord Melbourne endeavoured to palliate, to
represent the danger, which would arise from his secret correspondence
with the Queen as very little, to adduce precedents from history,
and to screen his present conduct behind what he imagined Lord Bute's
conduct had been under George III.[145] I listened patiently, and
replied in the end: All this might be mighty fine and quite calculated
to lay a flattering unction on his own soul, or it might suffice to
tranquillize the minds of the Prince and Anson, but that I was too old
to find the slightest argument in what I had just now heard, nor could
it in any way allay my apprehension. I began then to dissect all
that he had produced for his excusation, and showed him--as I thought
clearly, and as he admitted convincingly--that it would be impossible
to carry on this secret commerce with the Sovereign for any length
of time without exposing the Queen's character and creating mighty
embarrassments in the quiet and regular working of a Constitutional
machine.
My representations seemed to make a very deep impression, and Lord
Melbourne became visibly nervous, perplexed, and distressed. After
he had recovered a little I said, "I never was inclined to obtrude
advice; but if you don't dislike to hear my opinion, I am prepared to
give it to you." He said, "What is it?" I said, "You allow the Queen's
confinement to pass over quietly, and you wait till her perfect
recovery of it. As soon as this period has arrived, you state of
your own accord to Her Majesty that this secret and confidential
correspondence with her must cease; that you gave in to it, much
against your feelings, and with a decided notion of its impropriety
and danger, and merely out of a sincere solicitude to calm Her
Majesty's mind in a critical time, and to prevent the ill effects
which great and mental agitation might have produced on her health.
That this part of your purpose now being most happily achieved, you
thought yourself in duty bound to advise Her Majesty to _cease all
her communications_ to you on political subjects, as you felt it wrong
within yourself to receive them, and to return your political advice
and opinions on such matters; that painful as such a step must be to
your feelings, which to the last moment of your life will remain those
of the most loyal attachment and devotion to the Queen's person, it
is dictated to you by a deep sense of what you owe to the country, to
your Sovereign, and to yourself."
[Footnote 145: For some time after the accession of George
III., Bute, though neither in the Cabinet nor in Parliament,
was virtually Prime Minister, but he became Secretary of State
on 25th March 1761. George II. had disliked him, but he was
generally believed to have exercised an undue influence over
the consort of Prince Frederic of Wales, mother of George
III.]
_Queen Victoria to Sir Robert Peel._
_26th October 1841._
With respect to Serjeant Jackson, the Queen will not oppose his
appointment, in consequence of the high character Sir Robert Peel
gives him; but she cannot refrain from saying that she very much fears
that the favourable effect which has hitherto been produced by the
formation of so mild and conciliatory a Government in Ireland, may
be endangered by this appointment, which the Queen would sincerely
regret.
_Viscount Melbourne to Queen Victoria._
SOUTH STREET, _26th October 1841._
Lord Melbourne presents his humble duty to your Majesty, and returns
your Majesty the letters of the King of the Belgians, with many
thanks. It certainly is a very unfortunate thing that the Queen
Christina was encouraged to fix her residence at Paris, and the
suspicion arising, therefore, cannot but be very injurious both to the
King of the French and to the French nation.
Lord Melbourne returns his warmest thanks for your Majesty's kind
expressions. He felt the greatest pleasure at seeing your Majesty
again and looking so well, and he hopes that his high spirits did
not betray him into talking too much or too heedlessly, which he is
conscious that they sometimes do.
The King Leopold, Lord Melbourne perceives, still hankers after
Greece; but Crowns will not bear to be chopped and changed about in
this manner. These new Kingdoms are not too firmly fixed as it is, and
it will not do to add to the uncertainty by alteration....
[Pageheading: DISPUTE WITH UNITED STATES]
_Sir Robert Peel to Queen Victoria._
WHITEHALL, _28th October 1841._
... Sir Robert Peel humbly assures your Majesty that he fully
participates in the surprise which your Majesty so naturally expresses
at the extraordinary intimation conveyed to Mr Fox[146] by the
President of the United States.[147]
Immediately after reading Mr Fox's despatch upon that subject, Sir
Robert Peel sought an interview with Lord Aberdeen. The measure
contemplated by the President is a perfectly novel one, a measure of a
hostile and unjustifiable character adopted with pacific intentions.
Sir Robert Peel does not comprehend the object of the President,
and giving him credit for the desire to prevent the interruption of
amicable relations with this country, Sir Robert Peel fears that
the forcible detention of the British Minister, after the demand of
passports, will produce a different impression on the public mind,
both here and in the United States, from that which the President must
(if he be sincere) have anticipated. It appears to Sir Robert Peel
that the object which the President professes to have in view would be
better answered by the immediate compliance with Mr Fox's demand for
passports, and the simultaneous despatch of a special mission to this
country conveying whatever explanations or offers of reparation the
President may have in contemplation.
Sir Robert Peel humbly assures your Majesty that he has advised
such measures of preparation to be taken in respect to the amount of
disposable naval force, and the position of it, as without bearing
the character of menace or causing needless disquietude and alarm, may
provide for an unfavourable issue of our present differences with the
United States.
Sir Robert Peel fears that when the President ventured to make to Mr
Fox the communication which he did make, he must have laboured under
apprehension that M'Leod might be executed in spite of the efforts of
the general Government of the United States to save his life.
[Footnote 146: British Minister at Washington.]
[Footnote 147: One Alexander M'Leod was tried at Utica on
the charge of being implicated in the destruction of the
_Caroline_ (an American vessel engaged in carrying arms to the
Canadian rebels), in 1837, and in the death of Mr Durfee, an
American. The vessel had been boarded by Canadian loyalists
when lying in American waters, set on fire and sent over
Niagara Falls, and in the affray Durfee was killed. M'Leod
was apprehended on American territory, and hence arose the
friction between the two countries. M'Leod was acquitted 12th
October 1841.]
[Pageheading: PORTUGAL]
_Queen Victoria to the Earl of Aberdeen._
BUCKINGHAM PALACE, _31st October 1841._
The Queen received yesterday evening Lord Aberdeen's letter with the
accompanying despatches and draft. She certainly _is_ surprised at the
strange and improper tone in which Lord Howard's[148] despatches are
written, and can only attribute them to an over-eager and, she fully
believes, mistaken feeling of the danger to which he believes the
throne of the Queen to be exposed.
The Queen has carefully perused Lord Aberdeen's draft, which she
highly approves, but wishes to suggest to Lord Aberdeen whether upon
further consideration it might not perhaps be as well to _soften_ the
words under which she has drawn a pencil line, as she fears they might
irritate Lord Howard very much.
The Queen is induced to copy the following sentences from a letter she
received from her cousin, the King of Portugal, a few days ago, and
which it may be satisfactory to Lord Aberdeen to see:--
"_Je dois encore vous dire que nous avons toutes les raisons de nous
louer de la manière dont le Portugal est traité par votre Ministre des
Affaires Étrangères, et nous ferons de notre côté notre possible pour
prouver notre bonne volonté."_
[Footnote 148: Lord Howard de Walden, Minister Plenipotentiary
at Lisbon.]
[Pageheading: SECRETARIES OF STATE]
_Viscount Melbourne to Queen Victoria._
SOUTH STREET, _1st November 1841._
... Now for His Royal Highness's questions....
How the power of Prime Ministry grew up into its present form it is
|
Wikiomics:Percentage identity
How to compute the percentage identity between a pair of sequences?
The percentage identity for two sequences may take many different values. It is dependent on:
* 4) length of shortest sequence.
* 5) length of alignment.
* 6) mean length of sequence.
* 7) number of non-gap positions.
* 8) number of equivalenced positions excluding overhangs.
Credits
* Geoff Barton wrote most of the text as a message to the PDB mailing-list
* the original formatting for the wiki was done by Martin Jambon
|
import {shallowMount} from '@vue/test-utils'
import AccordionItem from '@/components/Accordion/Item'
describe('AccordionItem', () => {
const title = 'title'
const content = 'content'
const index = 0
const wrapperFactory = ({propsData, scopedSlots} = {}) => {
return shallowMount(AccordionItem, {
propsData: {
content,
index,
title,
...propsData
},
scopedSlots: {
...scopedSlots
}
})
}
it('renders title and content', async () => {
const wrapper = wrapperFactory()
expect(await wrapper.find('[data-el="title"]').text()).toEqual(title)
expect(await wrapper.find('[data-el="content"]').text()).toEqual(content)
wrapper.destroy()
})
it('does not render toggle button', async () => {
const wrapper = wrapperFactory({
propsData: {
showToggle: false
}
})
const toggle = await wrapper.find('[data-el="toggle"]')
expect(toggle.exists()).toBe(false)
wrapper.destroy()
})
it('emits accordion:select event on click accordion item', async () => {
const wrapper = wrapperFactory()
await wrapper.find('[data-el="title"]').trigger('click')
const event = wrapper.emitted('item:select')
expect(event).toBeTruthy()
expect(event[0]).toEqual([index])
wrapper.destroy()
})
it('renders passed value in title after slot passed', async () => {
const wrapper = wrapperFactory({
scopedSlots: {
title: `<template><h3>${title}</h3></template>`
}
})
const itemTitle = await wrapper.find('[data-el="title"]')
expect(itemTitle.html()).toContain(`<h3>${title}</h3>`)
wrapper.destroy()
})
it('renders passed value in content after slot passed', async () => {
const wrapper = wrapperFactory({
scopedSlots: {
content: `<template><pre>${content}</pre></template>`
}
})
const itemContent = await wrapper.find('[data-el="content"]')
expect(itemContent.html()).toContain(`<pre>${content}</pre>`)
wrapper.destroy()
})
})
|
User blog comment:Zaffie/Really quite urgent - Please help-!!!/@comment-2073496-20101006000518
Zaf, for me t get an idea of want u want, list some other charrie's names and nams u like plz.
|
Technology | Media | Telecommunications
Wednesday, October 14, 2009
Pay-TV Set Top Boxes Transition to MPEG-4
The global pay-TV market has been somewhat unpredictable for vendors that supply the key elements of the service delivery infrastructure. After a record-setting year in 2008, worldwide demand for digital cable set top boxes (STB) is falling in 2009, according to the latest market study by In-Stat.
The slowdown in unit shipments and revenue has generally been concentrated in the comparatively advanced cable markets in North America and Western Europe. The market slow-down has been due to reductions in cable operator capital expenditure (CAPEX) budgets brought on by the global economic recession.
Meanwhile, unit shipments to China are projected to set another record in 2009, approaching 20 million units, contributing to a rise in the overall Asia-Pacific market. In addition, increasing demand for digital cable TV services is pushing digital cable set top boxes into new markets in Asia, Latin America, and in Eastern Europe.
"Even with a slight decrease in unit shipments in 2009, the cable set top box market remains both dynamic and robust," says Mike Paxton, In-Stat analyst. "There are some significant technology transitions, including the transition to MPEG-4 and the move toward a hybrid QAM + IP cable set top box that are creating new opportunities for cable set top box vendors."
In-Stat's market study found the following:
- Global unit shipments of digital cable set top boxes are projected to reach 47 million in 2009, a decrease of 6 percent over 2008.
- Low-cost, digital terminal adapter (DTA) product unit shipments are beginning to have an impact on the cable set top box market in North America, especially in terms of product ASPs.
- While Motorola and Cisco Systems remain the top two cable set top box manufacturers, out of the remaining eight cable set top box manufacturers in the top ten, six of them are from China.
|
Game Controls
Game Controls
Keyboard
* W,S,A,D - move
* Z,E - buy/move a building
* X,R - build rail (also build Rail-Droids when standing on the railway beginning in your base)
Mouse
* Moving - aim with your gun, or to put building
* Mouse1 - shoot
* Mouse2 - same as Z, buy/pick up/put building in specified location
|
const errors = require('restify-errors')
const log = require('../../lib/log')
const User = require('../../models/User')
module.exports = async (req, res, next) => {
try {
await User.findOneAndUpdate({ email: req.user.email }, { profile: req.body })
res.send({ success: true, message: res.__('Profile updated successfully') })
log.info(`Profile Updated: ${req.user.email}`)
next()
} catch (err) {
log.error(err)
return next(new errors.InternalError(err.message))
}
}
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.