The following instructions describe how to install the Hue tarball on a multi-node cluster. You need to also install Hadoop and its satellite components (Oozie, Hive...) and update some Hadoop configuration files before running Hue.
Hue consists of a web service that runs on a special node in your cluster. Choose one node where you want to run Hue. This guide refers to that node as the Hue Server. For optimal performance, this should be one of the nodes within your cluster, though it can be a remote node as long as there are no overly restrictive firewalls. For small clusters of less than 10 nodes, you can use your existing master node as the Hue Server.
You can download the Hue tarball here: https://github.com/cloudera/hue/releases
Hue employs some Python modules which use native code and requires certain development libraries be installed on your system. To install from the tarball, you'll need these library development packages and tools installed on your system:
sudo apt-get install git ant gcc g++ libffi-dev libkrb5-dev libmysqlclient-dev libsasl2-dev libsasl2-modules-gssapi-mit libsqlite3-dev libssl-dev libxml2-dev libxslt-dev make maven libldap2-dev python-dev python-setuptools libgmp3-dev
sudo add-apt-repository ppa:webupd8team/java
sudo apt-get update
sudo apt-get install oracle-java8-installer
sudo apt-get install libtidy-0.99-0
sudo yum install ant asciidoc cyrus-sasl-devel cyrus-sasl-gssapi cyrus-sasl-plain gcc gcc-c++ krb5-devel libffi-devel libxml2-devel libxslt-devel make mysql mysql-devel openldap-devel python-devel sqlite-devel gmp-devel
apache-maven
package or maven3 tarball)Required for MacOS 10.11+
export LDFLAGS=-L/usr/local/opt/openssl/lib && export CPPFLAGS=-I/usr/local/opt/openssl/include
Installing Python 2.7:
Check your OS Version:
cat /etc/redhat-release
Make sure "/etc/redhat-release" contains "CentOS 6.8 or 6.9" version. These instructions are tested on CentOS 6.8 and 6.9 versions only. It may or may not work on previous CentOS 6 series OS.
yum install -y centos-release-SCL
yum install -y scl-utils
yum install -y python27
Check your OS Version
cat /etc/redhat-release
Make sure /etc/redhat-release
contains "RedHat 6.8 or 6.9" version. These instructions are tested on RedHat 6.8 and 6.9 versions only. It may or may not work on previous RedHat 6 series OS.
wget http://mirror.infra.cloudera.com/centos/6/extras/x86_64/Packages/centos-release-scl-rh-2-3.el6.centos.noarch.rpm
rpm -ivh centos-release-scl-rh-2-3.el6.centos.noarch.rpm
yum install -y scl-utils
yum install -y python27
Check your OS Version
cat /etc/redhat-release
Make sure /etc/redhat-release
contains "Oracle 6.8 or 6.9" version. These instructions are tested on Oracle 6.8 and 6.9 versions only. It may or may not work on previous Oracle 6 series OS.
wget -O /etc/yum.repos.d/public-yum-ol6.repo http://yum.oracle.com/public-yum-ol6.repo
Set the value of the enabled parameter for the software_collections repository to 1: for file /etc/yum.repos.d/public-yum-ol6.repo
[ol6_software_collections]
name=Software Collection Library release 3.0 packages for Oracle Linux 6 (x86_64)
baseurl=http://yum.oracle.com/repo/OracleLinux/OL6/SoftwareCollections/x86_64/
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-oracle
gpgcheck=1
enabled=1
for more details, refer to this link: https://docs.oracle.com/cd/E37670_01/E59096/html/section_e3v_nbl_cr.html
yum install -y scl-utils
yum install -y python27
Download both instantclient-basic and instantclient-sdk of the same version (<IP_ADDRESS>.0 for this example) and on your ~/.bash_profile, add
export ORACLE_HOME=/usr/local/share/oracle
export VERSION=<IP_ADDRESS>.0
export ARCH=x86_64
export DYLD_LIBRARY_PATH=$ORACLE_HOME
export LD_LIBRARY_PATH=$ORACLE_HOME
and then
source ~/.bash_profile
sudo mkdir -p $ORACLE_HOME
sudo chmod 775 $ORACLE_HOME
then unzip the content of both downloaded zip files into the newly created $ORACLE_HOME in a way that the 'sdk' folder is at the same level with the other files and then
ln -s libclntsh.dylib.11.1 libclntsh.dylib
ln -s libocci.dylib.11.1 libocci.dylib
and finally
cd sdk
unzip ottclasses.zip
Configure $PREFIX
with the path where you want to install Hue by running:
PREFIX=/usr/share make install
cd /usr/share/hue
You can install Hue anywhere on your system, and run Hue as a non-root user.
It is a good practice to create a new user for Hue and either install Hue in
that user's home directory, or in a directory within /usr/share
.
Alternatively to building Hue, a http://gethue.com/getting-started-with-hue-in-2-minutes-with-docker/ is available.
.Q: I moved my Hue installation from one directory to another and now Hue no longer functions correctly.
A: Due to the use of absolute paths by some Python packages, you must run a series of commands if you move your Hue installation. In the new location, run:
rm app.reg
rm -r build
make apps
.Q: Why does "make install" compile other pieces of software?
A: In order to ensure that Hue is stable on a variety of distributions and architectures, it installs a Python virtual environment which includes its dependencies. This ensures that the software can depend on specific versions of various Python libraries and you don't have to be concerned about missing software components.
After your cluster is running with the plugins enabled, you can start Hue on your Hue Server by running:
build/env/bin/supervisor
This will start several subprocesses, corresponding to the different Hue components. Your Hue installation is now running.
Hue is often run with:
A Web proxy lets you centralize all the access to a certain URL and prettify the address (e.g. ec2-54-247-321-151.compute-1.amazonaws.com --> demo.gethue.com).
The Quick Start wizard allows you to perform the following Hue setup operations by clicking the tab of each step or sequentially by clicking Next in each screen:
Displays a list of the installed Hue applications and their configuration. The location of the folder containing the Hue configuration files is shown at the top of the page. Hue configuration settings are in the hue.ini configuration file.
Click the tabs under Configuration Sections and Variables to see the settings configured for each application. For information on configuring these settings, see Hue Configuration in the Hue installation manual.
Hue ships with a default configuration that will work for
pseudo-distributed clusters. If you are running on a real cluster, you must
make a few changes to the hue.ini
configuration file (/etc/hue/hue.ini
when installed from the
package version) or pseudo-distributed.ini
in desktop/conf
when in development mode).
The following sections describe the key configuration options you must make to configure Hue.
This commands outlines the various sections and options in the configuration, and provides help and information on the default values.
These configuration variables are under the [desktop]
section in
the hue.ini
configuration file.
Hue uses CherryPy web server. You can use the following options to change the IP address and port that the web server listens on. The default setting is port 8888 on all configured IP addresses.
# Webserver listens on this address and port
http_host=<IP_ADDRESS>
http_port=8888
For security, you should also specify the secret key that is used for secure hashing in the session store. Enter a long series of random characters (30 to 60 characters is recommended).
secret_key=jFE93j;2[290-eiw.KEiwN2s3['d;/.q[eIW^y#e=+Iei*@Mn<qW5o
NOTE: If you don't specify a secret key, your session cookies will not be secure. Hue will run but it will also display error messages telling you to set the secret key.
In the Hue ini configuration file, in the [desktop] section, you can enter the names of the app to hide:
[desktop] # Comma separated list of apps to not load at server startup. app_blacklist=beeswax,impala,security,filebrowser,jobbrowser,rdbms,jobsub,pig,hbase,sqoop,zookeeper,metastore,spark,oozie,indexer
By default, the first user who logs in to Hue can choose any username and password and becomes an administrator automatically. This user can create other user and administrator accounts. User information is stored in the Django database in the Django backend.
The authentication system is pluggable. For more information, see the Hue SDK Documentation.
List of some of the possible authentications:
For example, to enable Hue to first attempt LDAP directory lookup before falling back to the database-backed user model, we can update the hue.ini configuration file or Hue safety valve in Cloudera Manager with a list containing first the LdapBackend followed by either the ModelBackend or custom AllowFirstUserDjangoBackend (permits first login and relies on user model for all subsequent authentication):
[desktop] [[auth]] backend=desktop.auth.backend.LdapBackend,desktop.auth.backend.AllowFirstUserDjangoBackend
This tells Hue to first check against the configured LDAP directory service, and if the username is not found in the directory, then attempt to authenticate the user with the Django user manager.
Programmatically
When a Hue administrator loses their password, a more programmatic approach is required to secure the administrator again. Hue comes with a wrapper around the python interpreter called the “shell” command. It loads all the libraries required to work with Hue at a programmatic level. To start the Hue shell, type the following command from the Hue installation root.
Then:
cd /usr/lib/hue (or /opt/cloudera/parcels/CDH-XXXXX/share/hue if using parcels and CM)
build/env/bin/hue shell
The following is a small script, that can be executed within the Hue shell, to change the password for a user named “example”:
from django.contrib.auth.models import User
user = User.objects.get(username='example')
user.set_password('some password')
user.save()
The script can also be invoked in the shell by using input redirection (assuming the script is in a file named script.py):
build/env/bin/hue shell < script.py
How to make a certain user a Hue admin
build/env/bin/hue shell
Then set these properties to true:
from django.contrib.auth.models import User
a = User.objects.get(username='hdfs')
a.is_staff = True
a.is_superuser = True
a.set_password('my_secret')
a.save()
Via a command
Go on the Hue machine, then in the Hue home directory and either type:
To change the password of the currently logged in Unix user:
build/env/bin/hue changepassword
If you don't remember the admin username, create a new Hue admin (you will then also be able to login and could change the password of another user in Hue):
build/env/bin/hue createsuperuser
The properties we need to tweak are leaflet_tile_layer and leaflet_tile_layer_attribution, that can be configured in the hue.ini file:
[desktop] leaflet_tile_layer=https://server.arcgisonline.com/ArcGIS/rest/services/World_Imagery/MapServer/tile/{z}/{y}/{x} leaflet_tile_layer_attribution='Tiles © Esri — Source: Esri, i-cubed, USDA, USGS, AEX, GeoEye, Getmapping, Aerogrid, IGN, IGP, UPR-EGP, and the GIS User Community'
We explained how to run Hue with NGINX serving the static files or under Apache. If you use another proxy, you might need to set these options:
[desktop] # Enable X-Forwarded-Host header if the load balancer requires it. use_x_forwarded_host=false # Support for HTTPS termination at the load-balancer level with SECURE_PROXY_SSL_HEADER. secure_proxy_ssl_header=false
You can configure Hue to serve over HTTPS.
Configure Hue to use your private key by adding the following
options to the hue.ini
configuration file:
ssl_certificate=/path/to/certificate ssl_private_key=/path/to/key
Ideally, you would have an appropriate key signed by a Certificate Authority.
If you're just testing, you can create a self-signed key using the openssl
command that may be installed on your system:
Create a key:
openssl genrsa 1024 > host.key
Create a self-signed certificate:
openssl req -new -x509 -nodes -sha1 -key host.key > host.cert
Note: The security vulnerability SWEET32 is also called Birthday attacks against TLS ciphers with 64bit block size and it is assigned CVE-2016-2183. This is due to legacy block ciphers having block size of 64 bits are vulnerable to a practical collision attack when used in CBC mode.
DES/3DES are the only ciphers has block size of 64-bit. One way to config Hue not to use them:
[desktop] ssl_cipher_list=DEFAULT:!DES:!3DES
When getting a bigger result set from Hive/Impala or bigger files like images from HBase, the response requires to increase the buffer size of SASL lib for thrift sasl communication.
[desktop] # This property specifies the maximum size of the receive buffer in bytes in thrift sasl communication, # default value is 2097152 (2 MB), which equals to (2 * 1024 * 1024) sasl_max_buffer=2097152
In the [useradmin]
section of the configuration file, you can
optionally specify the following:
default_user_group:: The name of a default group that is suggested when creating a user manually. If the LdapBackend or PamBackend are configured for doing user authentication, new users will automatically be members of the default group.
You can add a custom banner to the Hue Web UI by applying HTML directly to the property, banner_top_html. For example:
banner_top_html=
My company's custom Hue Web UI banner

You can customize a splash screen on the login page by applying HTML directly to the property, login_splash_html. For example:
[desktop]
[[custom]]
login_splash_html=WARNING: You are required to have authorization before you proceed.
There is also the possibility to change the logo for further personalization.
[desktop]
[[custom]]
# SVG code to replace the default Hue logo in the top bar and sign in screen
# e.g. <image xlink:href="/static/desktop/art/hue-logo-mini-white.png" x="0" y="0" height="40" width="160" />
logo_svg=
You can go crazy and write there any SVG code you want. Please keep in mind your SVG should be designed to fit in a 160×40 pixels space. To have the same ‘hearts logo’ you can see above, you can type this code
[desktop]
[[custom]]
logo_svg='<g><path stroke="null" id="svg_1" d="m44.41215,11.43463c-4.05017,-10.71473 -17.19753,-5.90773 -18.41353,-0.5567c-1.672,-5.70253 -14.497,-9.95663 -18.411,0.5643c-4.35797,11.71793 16.891,22.23443 18.41163,23.95773c1.5181,-1.36927 22.7696,-12.43803 18.4129,-23.96533z" fill="#ffffff"/> <path stroke="null" id="svg_2" d="m98.41246,10.43463c-4.05016,-10.71473 -17.19753,-5.90773 -18.41353,-0.5567c-1.672,-5.70253 -14.497,-9.95663 -18.411,0.5643c-4.35796,11.71793 16.891,22.23443 18.41164,23.95773c1.5181,-1.36927 22.76959,-12.43803 18.41289,-23.96533z" fill="#FF5A79"/> <path stroke="null" id="svg_3" d="m154.41215,11.43463c-4.05016,-10.71473 -17.19753,-5.90773 -18.41353,-0.5567c-1.672,-5.70253 -14.497,-9.95663 -18.411,0.5643c-4.35796,11.71793 16.891,22.23443 18.41164,23.95773c1.5181,-1.36927 22.76959,-12.43803 18.41289,-23.96533z" fill="#ffffff"/> </g>'
Read more about it in Hue with a custom logo post.
This article details how to store passwords in a script launched from the OS rather than have clear text passwords in the hue*.ini files.
Some passwords go in Hue ini configuration file making them easily visible to Hue admin user or by users of cluster management software. You can use the password_script feature to prevent passwords from being visible.
Hue now offers a new property, idle_session_timeout, that can be configured in the hue.ini file:
[desktop] [[auth]] idle_session_timeout=600
When idle_session_timeout is set, users will automatically be logged out after N (e.g. – 600) seconds of inactivity and be prompted to login again:
Read more about Auditing User Administration Operations with Hue and Cloudera Navigator.
These configuration variables are under the [hadoop]
section in
the hue.ini
configuration file.
Depending on which apps you need, you need to make sure that some Hadoop services are already setup (that way Hue can talk to them).
|-------------|--------------------------------------------------------| | Component | Applications | |-------------|--------------------------------------------------------| | Editor | SQL (Hive, Impala, any database...), Pig, Spark... | | Browsers | YARN, Oozie, Impala, HBase, Livy | | Scheduler | Oozie | | Dashboard | Solr, SQL (Impala, Hive...) | |-------------|--------------------------------------------------------|
You need to enable WebHdfs or run an HttpFS server. To turn on WebHDFS,
add this to your hdfs-site.xml
and restart your HDFS cluster.
Depending on your setup, your hdfs-site.xml
might be in /etc/hadoop/conf
.
<property>
<name>dfs.webhdfs.enabled</name>
<value>true</value>
</property>
You also need to add this to core-site.xml
.
<property>
<name>hadoop.proxyuser.hue.hosts</name>
<value>*</value>
</property>
<property>
<name>hadoop.proxyuser.hue.groups</name>
<value>*</value>
</property>
If you place your Hue Server outside the Hadoop cluster, you can run an HttpFS server to provide Hue access to HDFS. The HttpFS service requires only one port to be opened to the cluster.
Also add this in httpfs-site.xml
which might be in /etc/hadoop-httpfs/conf
.
<property>
<name>httpfs.proxyuser.hue.hosts</name>
<value>*</value>
</property>
<property>
<name>httpfs.proxyuser.hue.groups</name>
<value>*</value>
</property>
Hue submits MapReduce jobs to Oozie as the logged in user. You need to
configure Oozie to accept the hue
user to be a proxyuser. Specify this in
your oozie-site.xml
(even in a non-secure cluster), and restart Oozie:
<property>
<name>oozie.service.ProxyUserService.proxyuser.hue.hosts</name>
<value>*</value>
</property>
<property>
<name>oozie.service.ProxyUserService.proxyuser.hue.groups</name>
<value>*</value>
</property>
Hue's Hive SQL Editor application helps you use Hive to query your data. It depends on a Hive Server 2 running in the cluster. Please read this section to ensure a proper integration.
Your Hive data is stored in HDFS, normally under /user/hive/warehouse
(or any path you specify as hive.metastore.warehouse.dir
in your
hive-site.xml
). Make sure this location exists and is writable by
the users whom you expect to be creating tables. /tmp
(on the local file
system) must be world-writable (1777), as Hive makes extensive use of it.
HiveServer2 and Impala support High Availability through a “load balancer”. One caveat is that Hue’s underlying Thrift libraries reuse TCP connections in a pool, a single user session may not have the same Impala or Hive TCP connection. If a TCP connection is balanced away from the previously selected HiveServer2 or Impalad instance, the user session and its queries can be lost and trigger the “Results have expired” or “Invalid session Id” errors.
To prevent sessions from being lost, you need configure the load balancer with “source” algorithm to ensure each Hue instance sends all traffic to a single HiveServer2/Impalad instance. Yes, this is not true load balancing, but a configuration for failover High Availability. HiveSever2 or Impala coordinators already distribute the work across the cluster so this is not an issue.
To enable an optimal load distribution that works for everybody, you can create multiple profiles in our load balancer, per port for Hue clients and non-Hue clients like Hive or Impala. You can configure non-Hue clients to distribute loads with “roundrobin” or “leastconn” and configure Hue clients with “source” (source IP Persistence) on dedicated ports, for example, 10015 for Hive beeline commands, 10016 for Hue, 21051 for Hue-Impala interactions while 25003 for Impala shell.
You can configure the HaProxy to have two different ports associated with different load balancing algorithms. Here is a sample configuration (haproxy.cfg) for Hive and Impala HA on a secure cluster.
frontend hiveserver2_front bind *:10015 ssl crt /path/to/cert_key.pem mode tcp option tcplog default_backend hiveserver2 backend hiveserver2 balance roundrobin mode tcp server hs2_1 host-2.com:10000 ssl ca-file /path/to/truststore.pem check server hs2_2 host-3.com:10000 ssl ca-file /path/to/truststore.pem check server hs2_3 host-1.com:10000 ssl ca-file /path/to/truststore.pem check frontend hivejdbc_front bind *:10016 ssl crt /path/to/cert_key.pem mode tcp option tcplog stick match src stick-table type ip size 200k expire 30m default_backend hivejdbc backend hivejdbc balance source mode tcp server hs2_1 host-2.com:10000 ssl ca-file /path/to/truststore.pem check server hs2_2 host-3.com:10000 ssl ca-file /path/to/truststore.pem check server hs2_3 host-1.com:10000 ssl ca-file /path/to/truststore.pem checkAnd here is an example for impala HA configuration on a secure cluster.
frontend impala_front bind *:25003 ssl crt /path/to/cert_key.pem mode tcp option tcplog default_backend impala backend impala balance leastconn mode tcp server impalad1 host-3.com:21000 ssl ca-file /path/to/truststore.pem check server impalad2 host-2.com:21000 ssl ca-file /path/to/truststore.pem check server impalad3 host-4.com:21000 ssl ca-file /path/to/truststore.pem checkfrontend impalajdbc_front bind *:21051 ssl crt /path/to/cert_key.pem mode tcp option tcplog stick match src stick-table type ip size 200k expire 30m default_backend impalajdbc backend impalajdbc balance source mode tcp server impalad1 host-3.com:21050 ssl ca-file /path/to/truststore.pem check server impalad2 host-2.com:21050 ssl ca-file /path/to/truststore.pem check server impalad3 host-4.com:21050 ssl ca-file /path/to/truststore.pem check
Note: “check” is required at end of each line to ensure HaProxy can detect any unreachable Impalad/HiveServer2 server, so HA failover can be successful. Without TCP check, you may hit the “TSocket reads 0 byte” error when the Impalad/HiveServer2 server Hue tries to connect is down.
After editing the /etc/haproxy/haproxy.cfg file, run following commands to restart HaProxy service and check the service restarts successfully.
service haproxy restart service haproxy status
Also we need add following blocks into hue.ini.
[impala] server_port=21051Read more about it in the How to optimally configure your Analytic Database for High Availability with Hue and other SQL clients post.[beeswax] hive_server_port=10016
Hue currently requires that the machines within your cluster can connect to each other freely over TCP. The machines outside your cluster must be able to open TCP port 8888 on the Hue Server (or the configured Hue web HTTP port) to interact with the system.
Hue supports one HDFS cluster. That cluster should be defined
under the [[[default]]]
sub-section.
fs_defaultfs::
This is the equivalence of fs.defaultFS
(aka fs.default.name
) in
Hadoop configuration.
webhdfs_url:: You can also set this to be the HttpFS url. The default value is the HTTP port on the NameNode.
hadoop_conf_dir::
This is the configuration directory of the HDFS, typically
/etc/hadoop/conf
.
Hue’s filebrowser can now allow users to explore, manage, and upload data in an S3 account, in addition to HDFS.
Read more about it in the S3 User Documentation.
In order to add an S3 account to Hue, you’ll need to configure Hue with valid S3 credentials, including the access key ID and secret access key: AWSCredentials
These keys can securely stored in a script that outputs the actual access key and secret key to stdout to be read by Hue (this is similar to how Hue reads password scripts). In order to use script files, add the following section to your hue.ini configuration file:
[aws] [[aws_accounts]] [[[default]]] access_key_id_script=/path/to/access_key_script secret_access_key_script= /path/to/secret_key_script allow_environment_credentials=false region=us-east-1
Alternatively (but not recommended for production or secure environments), you can set the access_key_id and secret_access_key values to the plain-text values of your keys:
[aws] [[aws_accounts]] [[[default]]] access_key_id=s3accesskeyid secret_access_key=s3secretaccesskey allow_environment_credentials=false region=us-east-1
The region should be set to the AWS region corresponding to the S3 account. By default, this region will be set to ‘us-east-1’.
Hue’s file browser can now allow users to explore, manage, and upload data in an ADLS, in addition to HDFS and S3.
Read more about it in the ADLS User Documentation.
In order to add an ADLS account to Hue, you’ll need to configure Hue with valid ADLS credentials, including the client ID, client secret and tenant ID. These keys can securely stored in a script that outputs the actual access key and secret key to stdout to be read by Hue (this is similar to how Hue reads password scripts). In order to use script files, add the following section to your hue.ini configuration file:
[adls] [[azure_accounts]] [[[default]]] client_id_script=/path/to/client_id_script.sh client_secret_script=/path/to/client_secret_script.sh tenant_id_script=/path/to/tenant_id_script.sh [[adls_clusters]] [[[default]]] fs_defaultfs=adl://.azuredatalakestore.net webhdfs_url=https:// .azuredatalakestore.net
Alternatively (but not recommended for production or secure environments), you can set the client_secret value in plain-text:
[adls] [[azure_account]] [[[default]]] client_id=adlsclientid client_secret=adlsclientsecret tenant_id=adlstenantid [[adls_clusters]] [[[default]]] fs_defaultfs=adl://.azuredatalakestore.net webhdfs_url=https:// .azuredatalakestore.net
Hue supports one or two Yarn clusters (two for HA). These clusters should be defined
under the [[[default]]]
and [[[ha]]]
sub-sections.
resourcemanager_host:: The host running the ResourceManager.
resourcemanager_port:: The port for the ResourceManager REST service.
logical_name:: NameNode logical name.
submit_to:: To enable the section, set to True.
In the [impala]
section of the configuration file, you can
optionally specify the following:
server_host::
The hostname or IP that the Impala Server should bind to. By
default it binds to localhost
, and therefore only serves local
IPC clients.
LDAP or PAM pass-through authentication with Hive or Impala and Impersonation .
In the [beeswax]
section of the configuration file, you can
optionally specify the following:
beeswax_server_host::
The hostname or IP that the Hive Server should bind to. By
default it binds to localhost
, and therefore only serves local
IPC clients.
hive_conf_dir::
The directory containing your hive-site.xml
Hive
configuration file.
Use the query editor with any JDBC or Django-compatible database.
In the [liboozie]
section of the configuration file, you should
specify:
oozie_url::
The URL of the Oozie service. It is the same as the OOZIE_URL
environment variable for Oozie.
In the [search]
section of the configuration file, you should
specify:
solr_url:: The URL of the Solr service.
In the [hbase]
section of the configuration file, you should
specify:
hbase_clusters:: Comma-separated list of HBase Thrift servers for clusters in the format of "(name|host:port)".
Now that you've installed and started Hue, you can feel free to skip ahead
to the <
Hue can detect certain invalid configuration.
To view the configuration of a running Hue instance, navigate to
http://myserver:8888/hue/dump_config
, also accessible through the About
application.
Displays the Hue Server log and allows you to download the log to your local system in a zip file.
Read more on the Threads and Metrics pages blog post
Threads page can be very helpful in debugging purposes. It includes a daemonic thread and the thread objects serving concurrent requests. The host name, thread name identifier and current stack frame of each are displayed. Those are useful when Hue “hangs”, sometimes in case of a request too CPU intensive. There is also a REST API to get the dump of Threads using 'desktop/debug/threads'
Read more on the Threads and Metrics pages blog post
Hue uses the PyFormance Python library to collect the metrics. These metrics are represented as gauge, counters, meter, rate of events over time, histogram, statistical distribution of values. A REST API endpoint '/desktop/metrics/' to get all the metrics dump as json is also exposed
The below metrics of most concern to us are displayed on the page:
One of the most useful ones are the percentiles of response time of requests and the count of active users. Admins can either filter a particular property in all the metrics or select a particular metric for all properties
The User Admin application lets a superuser add, delete, and manage Hue users and groups, and configure group permissions. Superusers can add users and groups individually, or import them from an LDAP directory. Group permissions define the Hue applications visible to group members when they log into Hue and the application features available to them.
Click the User Admin icon in the top right navigation bar under your username.
LDAP or PAM pass-through authentication with Hive or Impala and Impersonation .
The User Admin application provides two levels of user privileges: superusers and users.
Users — can change their name, e-mail address, and password and log in to Hue and run Hue applications, subject to the permissions provided by the Hue groups to which they belong.
| Username | A user name that contains only letters, numbers, and underscores; blank spaces are not allowed and the name cannot begin with a number. The user name is used to log into Hue and in file permissions and job submissions. This is a required field. |
| Password and Password confirmation | A password for the user. This is a required field. |
| Create home directory | Indicate whether to create a directory named /user/username in HDFS. For non-superusers, the user and group of the directory are username. For superusers, the user and group are username and supergroup. |
| First name and Last name | The user's first and last name. |
| E-mail address | The user's e-mail address. The e-mail address is used by the Job Designer and Beeswax applications to send users an e-mail message after certain actions have occurred. The Job Designer sends an e-mail message after a job has completed. Beeswax sends a message after a query has completed. If an e-mail address is not specified, the application will not attempt to email the user. |
| Groups | The groups to which the user belongs. By default, a user is assigned to the **default** group, which allows access to all applications. See [Permissions](#permissions). |
| Active | Indicate that the user is enabled and allowed to log in. Default: checked. |
| Superuser status | Assign superuser privileges to the user. |
Note:
Importing users from an LDAP directory does not import any password information. You must add passwords manually in order for a user to log in.
To add a user from an external LDAP directory:
| Username | The user name. |
| Distinguished name | Indicate that Hue should use a full distinguished name for the user. This imports the user's first and last name, username, and email, but does not store the user password. |
| Create home directory | Indicate that Hue should create a home directory for the user in HDFS. |
Click Add/sync user.
If the user already exists in the User Admin, the user information in User Admin is synced with what is currently in the LDAP directory.
You can sync the Hue user database with the current state of the LDAP directory using the Sync LDAP users/groups function. This updates the user and group information for the already imported users and groups. It does not import any new users or groups.
Superusers can add and delete groups, configure group permissions, and assign users to group memberships.
You can add groups, and delete the groups you've added. You can also import groups from an LDAP directory.
| Name | The name of the group. Group names can only be letters, numbers, and underscores; blank spaces are not allowed. |
| Members | The users in the group. Check user names or check Select all. |
| Permissions | The applications the users in the group can access. Check application names or check Select all. |
[desktop] [[ldap]] login_groups=ldap_grp1,ldap_grp2,ldap_grp3
| Name | The name of the group. |
| Distinguished name | Indicate that Hue should use a full distinguished name for the group. |
| Import new members | Indicate that Hue should import the members of the group. |
| Import new members from all subgroups | Indicate that Hue should import the members of the subgroups. |
| Create home directories | Indicate that Hue should create home directories in HDFS for the imported members. |
Permissions for Hue applications are granted to groups, with users gaining permissions based on their group membership. Group permissions define the Hue applications visible to group members when they log into Hue and the application features available to them.
A script called supervisor
manages all Hue processes. The supervisor is a
watchdog process -- its only purpose is to spawn and monitor other processes.
A standard Hue installation starts and monitors the following processes:
runcpserver
- a web server based on CherryPy that provides the core web
functionality of HueIf you have installed other applications into your Hue instance, you may see other daemons running under the supervisor as well.
You can see the supervised processes running in the output of ps -f -u hue
:
UID PID PPID C STIME TTY TIME CMD
hue 8685 8679 0 Aug05 ? 00:01:39 /usr/share/hue/build/env/bin/python /usr/share/hue/build/env/bin/desktop runcpserver
Note that the supervisor automatically restarts these processes if they fail for any reason. If the processes fail repeatedly within a short time, the supervisor itself shuts down.
The Hue logs are found in /var/log/hue
, or in a logs
directory under your
Hue installation root. Inside the log directory you can find:
access.log
file, which contains a log for all requests against the Hue
web server.supervisor.log
file, which contains log information for the supervisor
process.supervisor.out
file, which contains the stdout and stderr for the
supervisor process..log
file for each supervised process described above, which contains
the logs for that process..out
file for each supervised process described above, which contains
the stdout and stderr for that process.If users on your cluster have problems running Hue, you can often find error
messages in these log files. If you are unable to start Hue from the init
script, the supervisor.log
log file can often contain clues.
In addition to logging INFO
level messages to the logs
directory, the Hue
web server keeps a small buffer of log messages at all levels in memory. You can
view these logs by visiting http://myserver:8888/hue/logs
. The DEBUG
level
messages shown can sometimes be helpful in troubleshooting issues.
To troubleshoot why Hue is slow or consuming high memory, admin can enable instrumentation by setting the instrumentation
flag to True.
[desktop] instrumentation=trueIf
django_debug_mode
is enabled, instrumentation is automatically enabled. This flag appends the response time and the total peak memory used since Hue started for every logged request.
[17/Apr/2018 15:18:43 -0700] access INFO <IP_ADDRESS> admin - "POST /jobbrowser/jobs/ HTTP/1.1" `returned in 97ms (mem: 135mb)`
[23/Apr/2018 10:59:01 -0700] INFO <IP_ADDRESS> admin - "POST /jobbrowser/jobs/ HTTP/1.1" returned in 88ms
Hue requires a SQL database to store small amounts of data, including user account information as well as history of job submissions and Hive queries. By default, Hue is configured to use the embedded database SQLite for this purpose, and should require no configuration or management by the administrator. However, MySQL is the recommended database to use. This section contains instructions for configuring Hue to access MySQL and other databases.
The default SQLite database used by Hue is located in: /usr/share/hue/desktop/desktop.db
.
You can inspect this database from the command line using the sqlite3
program or typing `/usr/share/hue/build/env/bin/hue dbshell'. For example:
sqlite3 /usr/share/hue/desktop/desktop.db
SQLite version 3.6.22
Enter ".help" for instructions
Enter SQL statements terminated with a ";"
sqlite> select username from auth_user;
admin
test
sample
sqlite>
It is strongly recommended that you avoid making any modifications to the database directly using SQLite, though this trick can be useful for management or troubleshooting.
If you use the default SQLite database, then copy the desktop.db
file to
another node for backup. It is recommended that you back it up on a regular
schedule, and also that you back it up before any upgrade to a new version of
Hue.
Although SQLite is the default database type, some advanced users may prefer to have Hue access an alternate database type. Note that if you elect to configure Hue to use an external database, upgrades may require more manual steps in the future.
The following instructions are for MySQL, though you can also configure Hue to work with other common databases such as PostgreSQL and Oracle.
To configure Hue to store data in MySQL:
Create a new database in MySQL and grant privileges to a Hue user to manage this database.
mysql> create database hue; Query OK, 1 row affected (0.01 sec) mysql> grant all on hue.* to 'hue'@'localhost' identified by 'secretpassword'; Query OK, 0 rows affected (0.00 sec)
Shut down Hue if it is running.
To migrate your existing data to MySQL, use the following command to dump the existing database data to a text file. Note that using the ".json" extension is required.
/usr/share/hue/build/env/bin/hue dumpdata > $some-temporary-file.json
Open the hue.ini
file in a text editor. Directly below the
[[database]]
line, add the following options (and modify accordingly for
your MySQL setup):
host=localhost port=3306 engine=mysql user=hue password=secretpassword name=hue
As the Hue user, configure Hue to load the existing data and create the necessary database tables:
/usr/share/hue/build/env/bin/hue syncdb --noinput mysql -uhue -psecretpassword -e "DELETE FROM hue.django_content_type;" /usr/share/hue/build/env/bin/hue loaddata $temporary-file-containing-dumped-data.json
Your system is now configured and you can start the Hue server as normal.
After installation, you can use Hue by navigating to http://myserver:8888/
.
The link:user-guide/index.html[user guide] will help users go through the various installed applications.
The two latest LTS versions of each browsers:
Your feedback is welcome. The best way to send feedback is to join the https://groups.google.com/a/cloudera.org/group/hue-user[mailing list], and send e-mail, to mailto:hue-user<EMAIL_ADDRESS>If you find that something doesn't work, it'll often be helpful to include logs from your server. Please include the logs as a zip (or cut and paste the ones that look relevant) and send those with your bug reports.


We respect the privacy of all visitors who coming in on this website. We're using Google analytics (is a freemium web analytics service offered by Google that tracks and reports website traffic). It also collects anonymous data about the visitor of the website that integrates Google Analytics.
The tracking information allows us to better understand the kind of visitors who come to our site and what content they are reading. Occasionally, we compile aggregate statistics about the number of visitors this site receives and browsers being used. No personally identifying data is included in this type of reporting.
Since this site integrates Google Analytics, all of our activity falls within the boundaries of the Google Analytics Terms of Service
If you have any questions with regard to this privacy statement, please send us a Message.


Page made by Michał Studnicki
The man who established capoeira regional
Mestre Bimba during playing on berimbau - the main instrument used in capoeira.
"Do not show off your progresses to your friends outside the roda. Hold them back and surprise people with them in a fight."
One of the rules in Mestre Bimba's Academy.


I graduated from the Bachelor’s degree course in Computer Science at UNIFEI (Federal University of Itajubá) - Itajubá campus and now I am a student in the MBA of Artificial Intelligence and Big Data at University of São Paulo (USP) - São Carlos campus - currently working as a full-time Jr Machine Learning Researcher at CPQD.
Download ResumeMBA in Artificial Intelligence and Big Data, 2022-Present
University of São Paulo (USP), São Carlos, Brazil
BSc in Computer Science, 2018-2022
Federal University of Itajubá (UNIFEI), Itajubá, Brazil
An example of linking directly to an external project website using “external_link”.
An example of using the in-built project page.


|
Bolt Preview
0.4.4
C++ template library with support for OpenCL
|
#include <iterator>
#include <type_traits>
#include <numeric>
#include <bolt/cl/bolt.h>
#include <boost/iterator/iterator_facade.hpp>
#include <boost/iterator/reverse_iterator.hpp>
#include <boost/shared_array.hpp>
Go to the source code of this file.
Classes | |
| class | bolt::cl::device_vector< T > |
| This defines the OpenCL version of a device_vector. More... | |
| class | bolt::cl::device_vector< T >::UnMapBufferFunctor< Container > |
| Class used with shared_ptr<> as a custom deleter, to unmap a buffer that has been mapped with device_vector data() method. | |
| class | bolt::cl::device_vector< T >::reference_base< Container > |
| A writeable element of the container The location of an element of the container may not actually reside in system memory, but rather in device memory, which may be in a partitioned memory space. Access to a reference of the container results in a mapping and unmapping operation of device memory. More... | |
| class | bolt::cl::device_vector< T >::iterator_base< Container > |
| Base class provided to encapsulate all the common functionality for constant and non-constant iterators. More... | |
| class | bolt::cl::device_vector< T >::reverse_iterator |
| A reverse random access iterator in the classic sense. More... | |
| class | bolt::cl::device_vector< T >::const_reverse_iterator |
| A constant random access iterator in the classic sense. More... |
Namespaces | |
| namespace | bolt |
| Defining namespace for the Bolt project. | |
| namespace | bolt::cl |
| Namespace that captures OpenCL related data types and functions. |
Public header file for the device_container class


How North East leads the way when it comes to producing England talent
When it comes to population, the region is punching well above its weight for England stars
by Jerry ChenNorth East has been a bedrock for producing a steady line of talented footballers for the national team for almost half a century.
With England playing their 1000th game tonight at Wembley against Montenegro, the newly released statistics for the games serves as a good reminder of North East contributions more so than ever.
Out of 1,244 players that have turned out for the Three Lions,145 of them hails from the North East which is the fourth highest total of any region in England behind the North West (280), Greater London (195) and the West Midlands (164).
It may not sound all that impressive but when you take into account of the North East’s population the region is indeed punching well above its weight.
Each of the 145 North East born England players plays for 17,947 individual currently living in the region.
The North West has the next best record with one player for every 25,302 residents followed by the West Midlands (one for every 34,618 people), the East Midlands (one for every 41,151 people) and Yorkshire and Humber (one for every 42,535 people).
On a county level, county Durham has the best record for each of it’s 46 England internationals work out for every 11,180 people of the county.
Lancashire comes next with one for every 15,069 residents, followed by Shropshire (17,134), Tyne and Wear (17,308) and South Yorkshire (18,032).
In terms of the town level, Mexborough comes out on top for anywhere to have produced at least five internationals.
The town has produced six England players over the years at a rate of one for every 2,541 people who currently live there.
Blackburn has the next best record with its 26 internationals working out at one for every 5,687 residents followed by Middlesbrough (one per 7,707 residents), Bolton (10,734) and Nottingham (11,425).
Sunderland on the other hand have each player plays for 11,490 locals while every one of internationals for South Shields works out for 15,067 of the population.
Region // Players
North West // 280
Greater London // 195
West Midlands // 164
North East // 145
Yorkshire and Humber // 121
East Midlands // 111
South East // 97
East of England // 51
South West // 41
Outside UK // 34
Wales // 2
Scotland // 2
Population per number of players from each region
Region // Players
North East // 17,947
North West // 25,302
West Midlands // 34,407
East Midlands // 41,151
Greater London // 42,392
Yorkshire and Humber // 43,941
South East // 89,948
East of England // 115,802
South West // 130,238
Population per number of players from each town/city
Town/City // Players
Mexborough // 2,541
Blackburn // 5,687
Middlesbrough // 7,707
Bolton // 10,734
Nottingham // 11,425
Sunderland // 11,490
Shrewsbury // 11,953
Burton-on-Trent // 12,050
Liverpool // 12,056
Stoke-on-Trent // 12,490
Preston // 12,769
Kensington and Chelsea // 13,076
Chester // 13,274
Barrow in Furness // 13,694
Manchester // 14,181
Burnley // 14,515
Sheffield // 14,665
Chesterfield // 14,827
Southport // 15,056
South Shields // 15,067


Imelda Staunton 'to take over from Olivia Coleman in The Crown'
Imelda Staunton has reportedly been cast as Queen Elizabeth in The Crown, taking over the role from Olivia Coleman.
Olivia is currently starring in the third series of the Netflix hit opposite Tobias Menzies as her husband Prince Philip.
She originally replaced Claire Foy who played the Queen in series one and two with Matt Smith as Prince Philip.
According to Mail Online Imelda, 63, will star in seasons five and six after being ‘approached by senior producers and casting directors to play the Queen from her mid-60s on’.
The series are likely to span the queen’s reign throughout the 90s, including 1992 which she famously called her ‘annus horribilis’.
It was the year Prince Andrew and Sarah Ferguson separated and Princess Anne divorced Captain Mark Phillips.
The period of time covered is also likely to include the deaths of Princess Diana in 1997, and Princess Margaret and the Queen Mother in 2002.
In season four Princess Diana will be played by Emma Corrin opposite Josh O’Connor as Prince Charles. Gillian Anderson will also appear as Margaret Thatcher.
Advertisement Advertisement
Season three, currently on Netflix, is Olivia’s debut as Her Majesty and covers the Aberfan disaster and the arrival of Prince Philip’s mother Princess Alice of Battenberg.
Harold Wilson’s time as Prime Minister, the moon landing, the decolonisation of Africa and the Caribbean and Princess Margaret’s affair with Roddy Llewellyn are also covered in the time period of 1964 until 1977.
Previously Dame Helen Mirren, who won an Oscar for her portrayal of Elizabeth II in the 2006 film The Queen, ruled out stepping into Olivia’s shoes.
‘I think it’s more interesting when you see other portraits and it builds into a more interesting picture than just someone coming back’ she said on Lorraine.
Metro.co.uk has contacted Netflix for comment.
The Crown season three is available on Netflix now.
Got a showbiz story?
If you've got a story, video or pictures get in touch with the Metro.co.uk Entertainment team by emailing us<EMAIL_ADDRESS>calling 020 3615 2145 or by visiting our Submit Stuff page - we'd love to hear from you.


Regasm located in
C:\Windows\Microsoft.NET\Framework\v4.0.30319
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\
(may be in other Framework folders as well)
.\regasm.exe /U "C:\Users\user\folder\exe"
It needs to be valid .NET assembly


0
0
Join the Custom Blocks
New GameWhat is Custom 2048: Create / Find a 2048 custom pack, and paste it in the box above.
You can also find pre-made packs, and a How-To Create at custom2048.github.io/packs.
Tile Legend:


{%extends "registration/base.html"%} {% load bootstrap4 %} {% block content %}
Check your information and before submiting
Open an account now sign-in
Get the app.


public enum StretchTypeEnum extends java.lang.Enum<StretchTypeEnum> implements JREnum
First, there is the natural stretch of the element, which is caused by the element growing naturally in order to display its entire content. This is the case with text fields that have isStretchWithOverflow set to true and thus growing in height in order to display all the rows of text that the value of their text field expression provides at runtime.
Secondly, there is the forced stretch of an element, which in addition to its natural growth required by its own content, needs to further grow to match the growing height of some other element that it is put in relation with at report design time.
A forced stretch can be imposed to elements that are part of element groups (JRElementGroup) or element containers (bands, frames, table cells, list cells, etc.).
The forced stretch also comes in two flavors.
There is element group stretch and container stretch.
Element group stretch is forced upon an element by the natural growth of the other elements in the same group.
The container stretch is forced upon an element by all types of growth that the container itself suffers,
including forced container stretch imposed onto the container by its own parent container.
| Enum Constant and Description |
|---|
CONTAINER_BOTTOM
Constant used for specifying that the element will adapt its height to match the new
height of the container it is placed on, which has been affected by stretch, but also taking
into account the fact that the Y position of the element has probably changed and should be compensated for,
resulting in the element's distance to container bottom being preserved.
|
CONTAINER_HEIGHT
Constant used for specifying that the element will adapt its height to match the new
height of the container it is placed on, which has been affected by stretch, but without taking
into account the fact that the Y position of the element within the container has probably changed due to floating and/or
collapsing white space above it.
|
ELEMENT_GROUP_BOTTOM
Constant used for specifying that the element will adapt its height to match the changing
height of the overall element group it is part of, but also taking into account the fact that the Y position of the
element within the group has probably changed due to floating and/or
collapsing white space above it and should be compensated for, resulting in the element's distance to the group's initial
bottom edge being preserved.
|
ELEMENT_GROUP_HEIGHT
Constant used for specifying that the element will adapt its height to match the changing
height of the overall element group it is part of, but without taking into account the fact that the Y position of the
element within the group has probably changed due to floating and/or
collapsing white space above it.
|
NO_STRETCH
A constant indicating that the element preserves its original specified height.
|
RELATIVE_TO_BAND_HEIGHT
Deprecated.
Replaced by
CONTAINER_HEIGHT . |
RELATIVE_TO_TALLEST_OBJECT
Deprecated.
Replaced by
ELEMENT_GROUP_HEIGHT . |
| Modifier and Type | Field and Description |
|---|---|
static java.lang.String |
PROPERTY_LEGACY_ELEMENT_STRETCH_ENABLED |
| Modifier and Type | Method and Description |
|---|---|
static StretchTypeEnum |
getByName(java.lang.String name) |
static StretchTypeEnum |
getByValue(byte value)
Deprecated.
Used only by deprecated serialized fields.
|
static StretchTypeEnum |
getByValue(java.lang.Byte value)
Deprecated.
Used only by deprecated serialized fields.
|
java.lang.String |
getName() |
byte |
getValue()
Deprecated.
Used only by deprecated serialized fields.
|
java.lang.Byte |
getValueByte()
Deprecated.
Used only by deprecated serialized fields.
|
static StretchTypeEnum |
valueOf(java.lang.String name)
Returns the enum constant of this type with the specified name.
|
static StretchTypeEnum[] |
values()
Returns an array containing the constants of this enum type, in
the order they are declared.
|
public static final StretchTypeEnum NO_STRETCH
public static final StretchTypeEnum RELATIVE_TO_TALLEST_OBJECT
ELEMENT_GROUP_HEIGHT
.public static final StretchTypeEnum RELATIVE_TO_BAND_HEIGHT
CONTAINER_HEIGHT
.public static final StretchTypeEnum ELEMENT_GROUP_HEIGHT
public static final StretchTypeEnum ELEMENT_GROUP_BOTTOM
public static final StretchTypeEnum CONTAINER_HEIGHT
public static final StretchTypeEnum CONTAINER_BOTTOM
public static final java.lang.String PROPERTY_LEGACY_ELEMENT_STRETCH_ENABLED
public static StretchTypeEnum[] values()
for (StretchTypeEnum c : StretchTypeEnum.values()) System.out.println(c);
public static StretchTypeEnum valueOf(java.lang.String name)
name
- the name of the enum constant to be returned.java.lang.IllegalArgumentException
- if this enum type has no constant with the specified namejava.lang.NullPointerException
- if the argument is nullpublic java.lang.Byte getValueByte()
getValueByte
in interface JREnum
public final byte getValue()
public static StretchTypeEnum getByName(java.lang.String name)
public static StretchTypeEnum getByValue(java.lang.Byte value)
public static StretchTypeEnum getByValue(byte value)
© 2001 - 2016 TIBCO Software Inc. www.jaspersoft.com


pip_services3_container.refer package¶
Submodules¶
- pip_services3_container.refer.BuildReferencesDecorator module
- pip_services3_container.refer.ContainerReferences module
- pip_services3_container.refer.LinkReferencesDecorator module
- pip_services3_container.refer.ManagedReferences module
- pip_services3_container.refer.ReferencesDecorator module
- pip_services3_container.refer.RunReferencesDecorator module
Module contents¶
pip_services3_container.refer.__init__¶
Provides the inversion of control design pattern but does not contain the fully functional container (we can just only create a class that will set various references).
Once the objects of a container are configured, if they implement the IReferenceable interface, they are passed a set of references for recreating links between objects in the container. If objects implement the IOpenable interface, the open() method is called and they start to work. Connections to various services are made, after which the objects start, the container starts running, and the objects carry out their tasks. When the container starts to close, the objects that implement the ICloseable interface are closed via their close() method (which should make them stop working and disconnect from other services), after which objects that implement the IUnreferenceable interface delete various links between objects, and, finally, the contains destroys all objects and turns off.
BuildReferencesDecorator Build, LinkReferencesDecorator Link, and RunReferencesDecorator Run - ReferenceDecorators are used during the corresponding building, linking, and running stages and are united in ManagedReferences, which are extended by ContainerReferences.
| copyright: | Conceptual Vision Consulting LLC 2018-2019, see AUTHORS for more details. |
|---|---|
| license: | MIT, see LICENSE for more details. |
-
class
pip_services3_container.refer.
ReferencesDecorator
(base_references, parent_references)¶ Bases:
pip_services3_commons.refer.IReferences.IReferences
Chainable decorator for IReferences that allows to inject additional capabilities such as automatic component creation, automatic registration and opening.
-
base_references
= None¶
-
find
(locator, required)¶ Gets all component references that match specified locator.
Parameters: - locator – the locator to find a reference by.
- required – forces to raise an exception if no reference is found.
Returns: a list with matching component references.
Raises: a ReferenceException when required is set to true but no references found.
-
get_all
()¶ Gets all component references registered in this reference map.
Returns: a list with component references.
-
get_all_locators
()¶ Gets locators for all registered component references in this reference map.
Returns: a list with component locators.
-
get_one_optional
(locator)¶ Gets an optional component reference that matches specified locator.
Parameters: locator – the locator to find references by. Returns: a matching component reference or null if nothing was found.
-
get_one_required
(locator)¶ Gets a required component reference that matches specified locator.
Parameters: locator – the locator to find a reference by. Returns: a matching component reference. Raises: a ReferenceException when no references found.
-
get_optional
(locator)¶ Gets all component references that match specified locator.
Parameters: locator – the locator to find references by. Returns: a list with matching component references or empty list if nothing was found.
-
get_required
(locator)¶ Gets all component references that match specified locator. At least one component reference must be present. If it doesn’t the method throws an error.
Parameters: locator – the locator to find references by. Returns: a list with matching component references. Raises: a ReferenceException when no references found.
-
parent_references
= None¶
-
put
(locator=None, reference=None)¶ Puts a new reference into this reference map.
Parameters: - locator – a locator to find the reference by.
- component – a component reference to be added.
-
remove
(locator)¶ Removes a previously added reference that matches specified locator. If many references match the locator, it removes only the first one. When all references shall be removed, use removeAll method instead.
Parameters: locator – a locator to remove reference Returns: the removed component reference.
-
remove_all
(locator)¶ Removes all component references that match the specified locator.
Parameters: locator – the locator to remove references by. Returns: a list, containing all removed references.
-
-
class
pip_services3_container.refer.
RunReferencesDecorator
(base_references, parent_references)¶ Bases:
pip_services3_container.refer.ReferencesDecorator.ReferencesDecorator
References decorator that automatically opens to newly added components that implement IOpenable interface and closes removed components that implement ICloseable interface.
-
close
(correlation_id)¶ Closes component and frees used resources.
Parameters: correlation_id – (optional) transaction id to trace execution through call chain.
-
is_opened
()¶ Checks if the component is opened.
Returns: true if the component has been opened and false otherwise.
-
open
(correlation_id)¶ Opens the component.
Parameters: correlation_id – (optional) transaction id to trace execution through call chain.
-
put
(locator=None, component=None)¶ Puts a new reference into this reference map.
Parameters: - locator – a locator to find the reference by.
- component – a component reference to be added.
-
remove
(locator)¶ Removes a previously added reference that matches specified locator. If many references match the locator, it removes only the first one. When all references shall be removed, use removeAll method instead.
Parameters: locator – a locator to remove reference Returns: the removed component reference.
-
remove_all
(locator)¶ Removes all component references that match the specified locator.
Parameters: locator – the locator to remove references by. Returns: a list, containing all removed references.
-
-
class
pip_services3_container.refer.
LinkReferencesDecorator
(base_references, parent_references)¶ Bases:
pip_services3_container.refer.ReferencesDecorator.ReferencesDecorator
,pip_services3_commons.run.IOpenable.IOpenable
References decorator that automatically sets references to newly added components that implement IReferenceable interface and unsets references from removed components that implement IUnreferenceable interface.
-
close
(correlation_id)¶ Closes component and frees used resources.
Parameters: correlation_id – (optional) transaction id to trace execution through call chain.
-
is_opened
()¶ Checks if the component is opened.
Returns: true if the component has been opened and false otherwise.
-
open
(correlation_id)¶ Opens the component.
Parameters: correlation_id – (optional) transaction id to trace execution through call chain.
-
put
(locator=None, component=None)¶ Puts a new reference into this reference map.
Parameters: - locator – a locator to find the reference by.
- component – a component reference to be added.
-
remove
(locator)¶ Removes a previously added reference that matches specified locator. If many references match the locator, it removes only the first one. When all references shall be removed, use removeAll method instead.
Parameters: locator – a locator to remove reference Returns: the removed component reference.
-
remove_all
(locator)¶ Removes all component references that match the specified locator.
Parameters: locator – the locator to remove references by. Returns: a list, containing all removed references.
-
-
class
pip_services3_container.refer.
BuildReferencesDecorator
(base_references, parent_references)¶ Bases:
pip_services3_container.refer.ReferencesDecorator.ReferencesDecorator
References decorator that automatically creates missing components using available component factories upon component retrival.
-
clarify_locator
(locator, factory)¶ Clarifies a component locator by merging two descriptors into one to replace missing fields. That allows to get a more complete descriptor that includes all possible fields.
Parameters: - locator – a component locator to clarify.
- factory – a factory that shall create the component.
Returns: clarified component descriptor (locator)
-
create
(locator, factory)¶ Creates a component identified by given locator.
Parameters: - locator – a locator to identify component to be created.
- factory – a factory that shall create the component.
Returns: the created component.
-
find
(locator, required)¶ Gets all component references that match specified locator.
Parameters: - locator – the locator to find a reference by.
- required – forces to raise an exception if no reference is found.
Returns: a list with matching component references.
-
find_factory
(locator)¶ Finds a factory capable creating component by given descriptor from the components registered in the references.
Parameters: locator – a locator of component to be created. Returns: found factory or null if factory was not found.
-
-
class
pip_services3_container.refer.
ManagedReferences
(tuples=None)¶ Bases:
pip_services3_container.refer.ReferencesDecorator.ReferencesDecorator
,pip_services3_commons.run.IOpenable.IOpenable
- Managed references that in addition to keeping and locating references can also manage their lifecycle:
- Auto-creation of missing component using available factories
- Auto-linking newly added components
- Auto-opening newly added components
- Auto-closing removed components
-
close
(correlation_id)¶ Closes component and frees used resources.
Parameters: correlation_id – (optional) transaction id to trace execution through call chain.
-
static
from_tuples
(*tuples)¶ Creates a new ManagedReferences object filled with provided key-value pairs called tuples. Tuples parameters contain a sequence of locator1, component1, locator2, component2, … pairs.
Parameters: tuples – the tuples to fill a new ManagedReferences object. Returns: a new ManagedReferences object.
-
is_opened
()¶ Checks if the component is opened.
Returns: true if the component has been opened and false otherwise.
-
open
(correlation_id)¶ Opens the component.
Parameters: correlation_id – (optional) transaction id to trace execution through call chain.
-
class
pip_services3_container.refer.
ContainerReferences
¶ Bases:
pip_services3_container.refer.ManagedReferences.ManagedReferences
Container managed references that can be created from container configuration.
-
put_from_config
(config)¶ Puts components into the references from container configuration.
Parameters: config – a container configuration with information of components to be added.
-


Page maintained by Ke-Sen Huang.
If you have additions or changes, send an e-mail.
Note that when possible I link to the page containing the link to the actual PDF or PS of the preprint.
I prefer this as it gives some context to the paper and avoids possible copyright problems with direct linking.
Thus you may need to search on the page to find the actual document.
Changelog
Acquisition
- Reconstruction of Volumetric Surface Textures for Real-Time Rendering
-
Sebastian Magda,
David Kriegman
- Statistical Acquisition of Texture Appearance
-
Addy Ngan,
Frédo Durand
- Sparse Lumigraph Relighting by Illumination and Reflectance Estimation from Multi-View Images
-
Tianli Yu,
Hongcheng Wang,
Narendra Ahuja,
Wei-Chao Chen
- Tomographic Reconstruction of Transparent Objects
-
Borislav Trifonov,
Derek Bradley,
Wolfgang Heidrich
Multi-View and Multi-Perspective
- An Efficient Multi-View Rasterization Architecture
-
Jon Hasselgren,
Tomas Akenine-Moller
- Antialiasing for Automultiscopic 3D Displays
-
Matthias Zwicker,
Wojciech Matusik,
Frédo Durand,
Hanspeter Pfister
- Automatic Multiperspective Images
-
Augusto Román,
Hendrik P. A. Lensch
- Real-time Multi-perspective Rendering on Graphics Hardware
-
Xianyou Hou,
Li-Yi Wei,
Heung-Yeung Shum,
Baining Guo
Sampling & Ray-Tracing
- Two Stage Importance Sampling for Direct Lighting
-
David Cline,
Parris Egbert,
Justin Talbot,
David Cardon
- Sequential Sampling of Environment Maps
-
Abhijeet Ghosh,
Arnaud Doucet,
Wolfgang Heidrich
- Making Radiance and Irradiance Caching Practical: Adaptive Caching and Neighbor Clamping
-
Jaroslav Køivánek,
Kadi Bouatouch,
Sumanta Pattanaik,
Jiri Zara
- Instant Ray Tracing: The Bounding Interval Hierarchy (PDF link provided by authors)
-
Carsten Wachter,
Alexander Keller
Radiance Transfer & Relighting
- Exploiting Temporal Coherence for Incremental All-Frequency Relighting
-
Ryan Overbeck,
Aner Ben-Artzi,
Ravi Ramamoorthi,
Eitan Grinspun
- Wavelet Radiance Transport for Real-time Indirect Lighting
-
Janne Kontkanen,
Emmanuel Turquin,
Nicolas Holzschuch,
François Sillion
- Efficient Wavelet Rotation for Environment Map Rendering
-
Rui Wang,
Ren Ng,
David Luebke,
Greg Humphreys
- Relighting Human Locomotion with Flowed Reflectance Fields
-
Per Einarsson, Charles-Felix Chabert, Andrew Jones, Bruce Lamond,
Alex Ma,
Tim Hawkins, Sebastian Sylwan,
Paul Debevec
Visibility & Shadows
- Adaptive Visibility Driven View Cell Construction
-
Oliver Mattausch,
Jiri Bittner,
Michael Wimmer
- Near Optimal Hierarchical Culling: Performance Driven Use of Hardware Occlusion Queries
-
Michael Guthe,
Akos Balazs,
Reinhard Klein
- Shadow Map Warping and Partitioning
-
Brandon Lloyd,
David Tuft,
Sung-Eui Yoon,
Dinesh Manocha
- Real-time Soft Shadow Mapping by Backprojection
-
Gaël Guennebaud,
Loïc Barthe,
Mathias Paulin
Photography & Matting
- Practical, Real-time Studio Matting using Dual Imagers
-
Morgan McGuire,
Wojciech Matusik,
William Yerazunis
- Surface Enhancement Using Real-time Photometric Stereo and Reflectance Transformation (PDF link provided by authors)
-
Tom Malzbender,
Bennett Wilburn,
Dan Gelb,
Bill Ambrisco
- Symmetric Photography : Exploiting Data-sparseness in Reflectance Fields
-
Gaurav Garg,
Eino-Ville Talvala,
Marc Levoy,
Hendrik P. A. Lensch
- Spatio-angular Resolution Trade-Offs in Integral Photography
-
Todor Georgiev,
Colin Zheng,
Shree K. Nayar,
David Salesin,
Brian Curless,
Chintan Intwala
Texture
- Texture Transfer Using Geometry Correlation
-
Tom Mertens,
Jan Kautz,
Jiawen Chen,
Philippe Bekaert,
Frédo Durand
- Silhouette Texture
-
Hongzhi Wu,
Li-Yi Wei,
Xi Wang,
Baining Guo
- Feature-Aware Texturing (Draft version)
-
Ran Gal,
Olga Sorkine,
Daniel Cohen-Or
- Texture Replacement of Garments in Monocular Video Sequences
-
Volker Scholz,
Marcus Magnor
GPU Rendering
- A GPU-driven Algorithm for Accurate Interactive Reflections on Curved Objects
-
Pau Estalella,
Ignacio Martin,
George Drettakis,
Dani Tost
- Interactive Screen-Space Accurate Photon Tracing on GPUs
-
Jens Kruger,
Kai Burger,
Rudiger Westermann
- A Novel Method for Fast and High-Quality Rendering of Hair
-
Songhua Xu,
,
Hao Jiang,
Yunhe Pan
- Ambient Occlusion for Animated Characters
-
Janne Kontkanen,
Timo Aila
NPR
- ARDECO: Automatic Region DEtection and Conversion
-
Gregory Lecot,
Bruno Lévy
- Segmentation-Based 3D Artistic Rendering
-
Alexander Kolliopoulos,
Jack M. Wang,
Aaron Hertzmann
- Painting With Texture
-
Lincoln Ritter,
Wilmot Li,
Maneesh Agrawala
Brian Curless,
David Salesin
- Directing Gaze in 3D Models with Stylized Focus
-
Forrester Cole,
Doug DeCarlo,
Adam Finkelstein,
Kenrick Kin,
Keith Morley,
Anthony Santella
Reflectance and Illumination
- Bidirectional Instant Radiosity
-
Benjamin Segovia,
Jean-Claude Iehl,
Richard Mitanchey,
Bernard Peroche
- Image-driven Navigation of Analytical BRDF Models
-
Addy Ngan,
Frédo Durand,
Wojciech Matusik
- A Spectral BSSRDF for Shading Human Skin (Project)
-
Craig Donner,
Henrik Wann Jensen
kesen.huang@gmail.com


{% assign lang = site.translations[site.lang] %} {%- comment -%} {%- endcomment -%} {%- assign format = '2' -%} {%- if include.icon and include.icon != '' and include.feature and include.feature != '' and include.description and include.description != '' -%} {%- if format == '1' -%}
{{ include.description | liquify | markdownify }}


Get Started
The open platform is a public service for accessing all the content the theguardian creates, categorised by tag and section. There are over one and a half million items available published as far back as 1999.
To get up and running, follow these simple steps:
- Read through our documentation
- Familiarise yourself with the API using our explorer
- Get access by registering for a key and reviewing our terms and conditions
- Ask for advice and send us your feedback using through our support forum
- Follow us on twitter and tweet us when your app has gone live - @openplatform
Get Access
Choose the level of access required for your application:
Developer
- Free
- Up to 12 calls per second
- Up to 5,000 calls per day
- Access to article text
- Access to over 1,740,000 pieces of content
Commercial
- On request
- Custom throttle limit
- Custom quota limit
- Access to article text, images, audio and videos
- Access to entire Guardian content store


☰ Menu
{% if classes|length > 0 %}
Class
Group Member Emails
Contact Group
Want to Leave?
{% for item in classes %}
{{ item[0] }}
{{ ", ".join(item[1]) }}
Send an email!
Yeah, I'm out!
{% endfor %}
{{ form.toDelete(class_="input", placeholder="classes", id="deletedClass")}} {{ form.hidden_tag() }}
{% else %}
You don't have any classes yet!
Click here to add you first!
{% endif %}


Hi there!
My name is
Chris Etienne. I am a Researcher in the
Discovery Research Group at
Agenus, a clinical-stage immuno-oncology company in Lexington, MA.
My main research focuses are in Functional Genomics and Novel Target Discovery -- I use a combination of novel Immunology techniques and Molecular Biology tools to conduct loss of function genomics screens in order to identify novel immune regulators relevant to cancer immune evasion. I also develop robust bioinformatics pipelines to analyze Next-Generation Sequencing data and clinical data to identify resistance mechanisms to immune checkpoint modulating (CPM) therapeutics, especially, PD1 and CTLA4.
I take a broad view of Immuno-Modulatory Drug Discovery and Targeted Therapy: I believe that combination treatments involving conventional small molecules and biologics (e.g. antibodies and recombinant proteins), as well as more novel therapies such as Adoptive Cell Therapy (CAR T, TCR, TIL, NK cells) together will provide curative treatments to patients.
Most of my work these days involves rethinking how to better understand the Tumor Immune Micro-Environment and its effects on the immune system, how to identify genetic markers underlying diseases across different cancer indications, applying and creating better computational tools for data analysis.
I am lover of open-source software/code and always looking for something new and fun to learn.


| Top |
An IPv4 or IPv6 socket address; that is, the combination of a GInetAddress and a port number.
GSocketAddress * g_inet_socket_address_new (GInetAddress *address
,guint16 port
);
Creates a new GInetSocketAddress for address
and port
.
Since 2.22
GSocketAddress * g_inet_socket_address_new_from_string (const char *address
,guint port
);
Creates a new GInetSocketAddress for address
and port
.
If address
is an IPv6 address, it can also contain a scope ID
(separated from the address by a "<literal>%</literal>").
Since 2.40
GInetAddress *
g_inet_socket_address_get_address (GInetSocketAddress *address
);
Gets address
's GInetAddress.
the GInetAddress for address
, which must be
g_object_ref()
'd if it will be stored.
[transfer none]
Since 2.22
guint16
g_inet_socket_address_get_port (GInetSocketAddress *address
);
Gets address
's port.
Since 2.22
guint32
g_inet_socket_address_get_flowinfo (GInetSocketAddress *address
);
Gets the sin6_flowinfo
field from address
,
which must be an IPv6 address.
Since 2.32
guint32
g_inet_socket_address_get_scope_id (GInetSocketAddress *address
);
Gets the sin6_scope_id
field from address
,
which must be an IPv6 address.
Since 2.32
“flowinfo”
property“flowinfo” guint
The sin6_flowinfo
field, for IPv6 addresses.
Flags: Read / Write / Construct Only
Default value: 0
Since 2.32
“port”
property“port” guint
The port.
Flags: Read / Write / Construct Only
Allowed values: <= 65535
Default value: 0
“scope-id”
property“scope-id” guint
IPv6 scope ID.
Flags: Read / Write / Construct Only
Default value: 0


Lightning Datatable for SObject (Account)
Edit
Delete
Edit Account
{{accountToEdit | json}}
{{accountEditForm?.value | json}} Valid: {{accountEditForm?.valid}}
Save
Cancel


GymJunkie
Hate going to the gym when it's full? We know that feel bro. That's why we built GymJunkie, to show you how many people are at the gym right now and when today will probably be a good time to come by.
There are
54


Defines position, rotation and speed related data for moving an entity.
More...
|
| | Movement (float speed=0.0f, float rotationSpeed=0.0f) |
| | Initializes a new instance of the T:MB2D.EntityComponent.Movement class. More...
|
| |
Defines position, rotation and speed related data for moving an entity.
§ Movement()
| MB2D.EntityComponent.Movement.Movement |
( |
float |
speed = 0.0f , |
|
|
float |
rotationSpeed = 0.0f |
|
) |
| |
|
inline |
Initializes a new instance of the T:MB2D.EntityComponent.Movement class.
- Parameters
-
| speed | Initial speed value. |
| rotationSpeed | Initial rotation speed value. |
§ Angle
| float MB2D.EntityComponent.Movement.Angle |
|
getset |
Gets or sets the angle.
The angle in radians.
§ Heading
| Vector2 MB2D.EntityComponent.Movement.Heading |
|
getset |
Gets or sets the current heading.
The heading.
§ LastPosition
| Vector2 MB2D.EntityComponent.Movement.LastPosition |
|
getset |
Gets or sets the last known position.
The last position.
§ Position
| Vector2 MB2D.EntityComponent.Movement.Position |
|
getset |
Gets or sets the world position.
The position.
§ RotationSpeed
| float MB2D.EntityComponent.Movement.RotationSpeed |
|
getset |
Gets or sets the rotation speed.
The rotation speed.
§ Speed
| float MB2D.EntityComponent.Movement.Speed |
|
getset |
Gets or sets the movement speed.
The speed.
The documentation for this class was generated from the following file:
- MB2D/src/EntityComponent/Components/Movement.cs


quintilesims
Businessmodel of QuintilesIMS
Customer Segments
QuintilesIMS provides a broad range of services to commercial and institutional customers operating in the healthcare and pharmaceuticals sectors. The Company’s customers principally fall into the following categories:
- Pharmaceutical, including small, mid-size domestic and regional pharmaceutical companies, and multinational pharmaceutical and biopharmaceutical enterprises; and
- Other Healthcare, including medical device manufacturers, diagnostic companies, and healthcare providers, including clinics, large hospitals, and health systems. No single customer accounted for 10% or more of QuintilesIMS’s consolidated service revenues in 2015. The Company has historically derived a significant portion of its service revenues from a relatively limited number of major projects or customers, and, as biopharmaceutical companies continue to outsource large projects to a limited number of providers, this concentration of business could increase.
QuintilesIMS serves an international customer base, spanning its domestic market of the US, as well as markets across Europe, Asia, Japan, Canada, Africa, and Latin America.
Value Propositions
QuintilesIMS provides value to its customers in the following ways:
- Its reputation and track record, with the Company established as a reliable provider of biopharmaceutical development services and commercial outsourcing services, serving a large client base, including high-profile, multinational pharmaceutical businesses;
- Its broad selection of services and solutions, with the Company offering a wide range of services to its customers, supporting various aspects of the pharmaceutical commercialisation process, including channel management, patient engagement services, market access consulting, brand communication solutions;
- Its technologies, with the Company utilising proprietary IT platforms and technologies that support the Company’s commercial engagements, clinical trials and real-world studies, as well as its online safety platform;
- Its international reach, with the Company serving customers across Asia Pacific, Europe, Africa, Latin America, as well as its native North America;
- Its industry expertise and experience, with the Company employing specialist personnel across its various operating divisions, as well as an experienced team of industry executives. ### Channels
QuintilesIMS operates a website at www.quintilesims.com, through which its provides information on its various services, solutions, and operating locations. The Company also operates separate websites for its Quintiles and IMS Health units at www.quintiles.com and www.imshealth.com respectively. The IMS Health website also hosts an online customer portal, which allows customers to manage their IMS Health applications, and access tools and resources.
QuintilesIMS operates its own extensive in-house sales and service force. These personnel operate out of the Company’s international network of offices, spanning the Americas, Asia Pacific, Europe, the Middle East, and Africa, including locations in the US, China, the UK, Brazil, and South Africa. The Company’s sales and service force notably includes its dedicated contract sales team, which comprises more than 6,700 contract medical sales representatives around the world.
QuintilesIMS additionally provides services through its international workforce of specialist employees, including medical doctors and academics, as well as its team of health management services professionals who offer customised clinical and educational solutions to bridge the gap between the clinical and commercial phases of product development.
Customer Relationships
QuintilesIMS provides a selection of services and tools to its customers on a self-service basis, through its IMS Health customer portal. This principally comprises applications related to the Company’s product development services, through which customers can access a range of functions, resources, and tools without interacting directly with members of the Company’s sales and service personnel.
QuintilesIMS provides customised services to its customers through its contract sales force, which offers flexible solutions – including direct hire, flexible work arrangements, leave of absence and “strike force” arrangements – that are tailored to the individual needs of each client. The Company also works closely with clients through its specialist personnel and health management professionals, who consult directly with clients, working toward the goals of the customer.
QuintilesIMS offers ongoing support to its customers, who are able to contact the company’s various offices and departments directly, receiving personalised assistance over the phone or online. The Company also provides a range of online support resources, including FAQs, and technical information.
QuintilesIMS additionally maintains contact with its customers through its social media accounts – including with Facebook, Google+, Twitter, and LinkedIn – which serve as an extra point of contact and enable the Company to keep customers updated with company developments.
Key Activities
QuintilesIMS operates as a provider of biopharmaceutical development services and commercial outsourcing services, principally in relation to the development and commercialisation of pharmaceutical therapies.
The Company aligns its operations into two reportable business segments: Product Development, which operates as contract research organisation, focused on Phase II-IV clinical trials and associated laboratory and analytical activities; and Integrated Healthcare Services, which comprises commercial pharmaceutical sales and service organisations, providing a range of services, including contract pharmaceutical sales, phase research, market access and consulting, health information analytics and technology consulting, and other healthcare solutions.
QuintilesIMS serves a range of companies operating across the pharmaceutical and healthcare sectors in a number of geographic regions, including the Americas, Asia Pacific, Europe, and Africa.
Key Partners
QuintilesIMS works closely with a broad range of partner organisations and companies across its two operating segments. These partners can be categorised broadly as:
- Supplier and Vendor Partners, including suppliers of various tools, equipment, and services that support the Company’s core operations, as well as various companies to which certain non-technical functions can be outsourced;
- Research and Investigator Partners, including medical research, pharmaceutical, and diagnostic companies that assists the Company in its research activities, as well as physicians, referred to as investigators, at hospitals, clinics or other sites that work on the Company’s clinical trials;
- Joint Venture Partners, comprising various pharmaceutical and diagnostic companies with which the Company works on joint projects through mutually owned entities; and
- Strategic and Alliance Partners, comprising market-leading companies from a range of industries, with which the Company collaborates on various projects and promotions. QuintilesIMS has agreed a range of partnerships in recent years. This includes a strategic tie-up with Biogen Idec, a partnership with Cardiovascular Research Foundation to join forces on trial services, and a strategic alliance with DaVita Clinical Research.
Key Resources
QuintilesIMS’s key resources are its technologies and intellectual properties, its online platform and applications, its IT and communications infrastructure, its sales and distribution channels, its partnerships, and its personnel.
QuintilesIMS develops and uses a number of proprietary methodologies, analytics, systems, technologies and other intellectual property in the conduct of its business. Searches of records published by the US Patent and Trademark Office identified a number of patent applications in which QuintilesIMS is named as assignee, including applications entitled ‘Methods and systems for predictive clinical planning and design and integrated execution services’, ‘Methods for predicting cardiac toxicity’ and ‘Methods for providing an easily comprehendible risk rating for pharmaceutical products’.
QuintilesIMS also owns and or leases a network of around 120 offices located in approximately 60 countries worldwide.
Cost Structure
QuintilesIMS incurs costs in relation to the development of solutions and technologies, development of its online portal, the maintenance of its IT and communications infrastructure, the operation so fits sales and distribution channels, the procurement of professionals services, the management of its partnerships, and the retention of its personnel.
In 2015 QuintilesIMS recorded total cost of revenue and service costs in the amount of $2.73 billion, and selling, general, and administrative costs totalling $920.99 for the year.
Revenue Streams
QuintilesIMS generates revenue primarily through the provision of various biopharmaceutical development services and commercial outsourcing services to pharmaceutical and medical customers. The Company divides its revenue streams into two categories:
- Service Revenues, primarily including revenue derived from the provision of product development and commercialisation services to our customers; and
- Reimbursed Expenses, comprising payments to physicians (investigators) who oversee clinical trials and travel expenses for the Company’s clinical monitors and sales representatives. In 2015 QuintilesIMS generated annual revenue of $5.74 billion, up marginally on the $5.46 billion recorded by the Company in 2014. This comprised $4.33 billion in service revenue, and $1.41 billion in reimbursed expenses. The Company’s Product Development segment accounted for around 73.8% of its 2015 service revenues, while its Integrated Healthcare Services segment accounted for approximately 26.2%.