HEAL Platform Documentation
1. The HEAL Platform
The HEAL Platform is a cloud-based and multifunctional web interface that provides a secure environment for discovery and analysis of NIH HEAL results and data. It is designed to serve users with a variety of objectives, backgrounds, and specialties.
The HEAL Platform represents a dynamic Data Ecosystem that aggregates and hosts data from multiple resources to make data discovery and access easy for users.
The platform provides a way to search and query over study metadata and diverse data types, generated by different projects and organizations and stored across multiple secure repositories.
The HEAL platform also offers a secure and cost-effective cloud-computing environment for data analysis, empowering collaborative research and development of new analytical tools. New workflows and results of analyses can be shared with the HEAL community to enable collaborative, high-impact publications that address the opioid crisis.
The HEAL Platform is powered by the open-source software “Gen3” . Gen3 was created by and is actively developed at the University of Chicago’s Center for Translational Data Science (CTDS) with the aim of creating interoperable cloud-based data resources for the scientific research community.
Watch the introduction video to the HEAL Platform below
2. Types of hosted Data
The HEAL Platform provides secure access to data that is the product of opioid research and will be the driving engine for new discovery.
On the highest level, the data hosted on the HEAL Platform range from study metadata that describe available datasets at a high-level to subject-level data. The types of data represented are diverse and include scientific research across multiple disciplines, as well as studies related to policy making and community service leadership. For example, researchers can use this single platform to find data ranging from clinical patient care data and public records to “omics” data files and associated sample collection and processing data.
The HEAL platform aims to make data more accessible by following the "FAIR" principles:
Findable
- Researchers are provided an intuitive interface to search over metadata for HEAL studies and related datasets.
- Each study and dataset will be assigned a unique, persistent identifier.
Accessible
- Authenticated users can request and receive access to controlled-access data by data providers.
- Metadata can be accessed via an open API.
Interoperable
- Standard metadata vocabularies facilitate discovery and joint analysis of HEAL and related datasets. Data can
- Data can be easily exported to various workspaces for analysis using a variety of software tools.
Reusable
- Data can be easily reused to facilitate reproducibility of results, development and sharing of new tools, and collaboration between investigators.
3. Data Management and Repositories
The HEAL-funded RENCI/RTI (Renaissance Computing Institute) at the University of North Carolina at Chapel Hill team will provide data management, stewardship, and support to help investigators make their data FAIR and connect to the Platform. The HEAL Platform securely exposes data stored on multiple HEAL-approved repositories. For more information, see https://heal.nih.gov/about/public-access-data.
Currently, the platform has the following Data Resources:
4. How to get started
a) HEAL Platform Overview
Click on an icon to jump to the section
b) Login Page
Browsing the study metadata on the Discovery Page, following along the pre-made notebooks in the
“Static Notebooks” tab, and downloading the file manifest with publicly accessible data files does not require
authorization and is open-access.
Click here to see all open-access studies.
You will need to log in and obtain authorization (access) in order to run analyses in workspaces.
Browsing the study metadata on the Discovery Page, following along the pre-made notebooks in the “Static Notebooks” tab, and downloading the file manifest with publicly accessible data files does not require authorization and is open-access.
Click here to see all open-access studies.
You will need to log in and obtain authorization (access) in order to run analyses in workspaces.
Clicking on a study containing controlled data will prompt users to log in. In order to access controlled data available on the HEAL Platform – for which you will be prompted once clicking on the study – or perform analyses in the workspace, start by visiting the login page (https://healdata.org/login).
Login from Google: You may login using any Google account credentials, or a G-suite enabled institutional email. This option may or may not be available depending on the institution or organization the user is associated with. Users should contact the IT support to verify if this option is available. For staff, students, and faculty of the University of Chicago, more information can be found here.
ORCID Login: Users with an ORCID account can log in using their ORCID credentials.
InCommon Login: Users can login with a participating institution that is federated by InCommon. Click on “Select...” to browse and choose the institution.
After successfully logging in, your username will appear in the upper right-hand corner of the page.
c) How to check and request access
Users can find out to which projects they have access to by navigating to the Discovery Page and by selecting “Data Availability" - "Available" - ”OK” as shown below.
Access to individual Studies
You can check access by clicking on a study in the Discovery Page, as shown below:
If you have access, a green box will show “You have access to this study”.
Current (open-access) studies
Current open-access studies will be shown when navigating to the Discovery Page.
Users can download and/or export open-access study files after logging in.
Currently, the HEAL Platform hosts the following studies. All are open-access except when noted.
Note, that different studies relate to different Data Resources.
| Project number | Study Name | Data Resource |
|---|---|---|
| 57b45d83d6c9e7e8693ccdfd | Naloxone Overdose Prevention Laws | PDAPS |
| 10.3886/ICPSR34945.v3 | National Mental Health Services Survey (N-MHSS) | ICPSR |
| 1U24AR076730-01 | A synthetic dataset from the Back Pain Consortium (BACPAC) Research Program Data Integration, Algorithm Development and Operations Management Center | HEAL |
| 10.3886/ICPSR04256.v5 | National Survey of Substance Abuse Treatment Services (N-SSATS) | ICPSR |
| cdcwonder | CDC Wide-ranging Online Data for Epidemiologic Research (CDC WONDER) Mortality Multiple Cause-of-Death Public Use Record | HEAL |
| 10.3886/ICPSR30122.v5 | Treatment Episode Data Set: Discharges (TEDS-D) | ICPSR |
| deaarcos1 | Drug Enforcement Administration Controlled Substances Tracking (DEA ARCOS) | HEAL |
|
a) 1U2CDA050098-01_a b) 1U2CDA050098-01_b |
JCOIN - Methodology and Advanced Analytics Resource Center: a) JCOIN 026: Amerispeak Brief Stigma Survey b) The Opioid Environment Policy Scan |
JCOIN |
Overview of access to Datasets and Studies
Users can visit the "Profile” page to view a list of studies they have access to under the “You have access to the following project(s)” section, as shown in the figure below.
From here users can also view current API keys or create and download new keys. API keys are required for downloads which require use of the Gen3-client. More information in the chapter “Downloading Data Files”.
From here users can also view if they have access to projects or workspaces
- /dictionary_page: You have access to the data dictionary.
- /workspace: You have access to the workspace.
- /programs/open: You have access to open-access projects.
Linking access to FAIR enabled repositories
Users need to login to access data stored on FAIR enabled repositories in order to run selected Jupyter Notebooks (see section Static Notebooks) that are based on data stored on the FAIR repositories.
Users can link their access to another repository when navigating to the healdata.org/workspace and clicking on one of the current login options as shown below.
The login button will turn grey upon once access is activated. Access needs to be renewed after 30 days.
d) Discovery Page
The Discovery Page provides users a venue to search and find studies and datasets displayed in the HEAL Platform. Users can browse through the publicly accessible study-level metadata without requiring authorization.
Use text-based search, faceted search, and tags to rapidly and efficiently find relevant studies, discover new datasets across multiple resources, and easily export selected data files to the analysis workspace.
Search Features
Finding studies is made easy using keywords (ex. study name, titles, investigator names, etc.) in the free text-based search bar or using tags, see image below.
Find available Study-level Metadata
Finding available study-level metadata on the HEAL Platform is made easy by clicking on a study.
Find accessible Datasets
Users can select and filter studies from multiple resources and conduct analyses on the selected datasets in a workspace. Users can find search only available data they have access to by selecting the data access button in the top right corner of the study page and selecting “Data Availability" - "Available" as shown below. The Discovery Page will automatically update the list of studies that have available datasets.
Data Availability Options
Different options for Data Availability exist and will be explained below.
-
Available: This option will display only studies with datasets users have access to and entails
all open-access studies. Studies can be selected and exported to a workspace or downloaded by clicking on the
associated checkbox on the left-hand side of the study entry and selecting one of the options in the top right.
Once available, each study can be selected and exported to workspace or downloaded.
-
Not available: This option will filter out all studies that will only have
metadata but no datasets available. The checkbox next to the study will be greyed out and non-clickable.
Studies will grey out if they're not available, have no data attached, users have no access to, or are in pending mode.
-
Pending: This option will display studies located on any
data resource or repository, for which attached datasets will be added in the near future.
The checkbox next to the study will be greyed out and non-clickable as shown above.
Select Files on the Discovery Page and bring them to the Workspace
The above gif shows the workflow used to select data files from the
Discovery Page and bring them into the workspace using Jupyter Notebooks.
Please scroll to the end of this section to find instructions on how to find exported data files in the RStudio environment.
-
Log in on healdata.org/login.
-
Find and select study on the Discovery Page using the checkbox on the left side and clicking on "Open in Workspace".
See current open-access studies here.
-
Choose a workspace flavor. This step may take several minutes.
-
Navigate to the
/pd/data/healdata.org/
folder and find the manifests there.
- "pd" means persistent directory. Saved files outside this directory will be lost.
- The manifests will capture the file information sorted by name, guid (i.e. digital ID), or filepath.
- The manifest folders are named according to the timestamp of creation, such asmanifest-YYYY-MM-XXXX-XX-XX.XXXXXX
.
- Note, that all exported data files will be saved in the/pd/data/healdata.org/
folder.
- Please also note, that the workspace mounts up to a maximum of 5 different manifests while the workspace is running but shows only the latest exported manifest in a newly launched workspace.
- Terminating the workspace will result in the loss of all but the latests manifest.
-
From the directory
/pd
, users can now start a new notebook. Click “New” (upper right corner) or open a previously saved notebook on the landing drive to load the files into one of the cells, for example by running
import os
import pandas as pd
os.chdir('/pd')
demo_df = pd.read_csv('pd/this_is_a_demo.txt', sep='\t')
demo_df.head()
More information for instructions on importing data can be found in the section "Workspaces".
- Make sure to terminate the workspace when the work is finished to reduce computational costs.
If users work in the RStudio environment, click
"Terminal" on the left hand side. The home
directory is
/home/rstudio
.
In order to find the files, type in
cd ../../data/healdata.org
and
ls
to list all manifests.
Read more here.
e) Workspaces
HEAL Platform workspaces are secure data analysis environments in the cloud that can access data from one or more data resources. By default, Workspaces include Jupyter notebooks, Python and RStudio, but can be configured to host virtually any application, including analysis workflows, data processing pipelines, or data visualization apps.
New to Jupyter? Learn more about the popular tool for data scientists on Jupyter.org (disclaimer: CTDS is not responsible for the content).
Guideline to get started
- Users need to log in via healdata.org/login to access workspaces.
-
After navigating to healdata.org/workspace, users will discover a list of pre-configured virtual machine (VM) images, as shown below.
Available workspaces on the HEAL Platform (top). Users can link accounts from other repositories (bottom; click here to see how).
- (Generic) Jupyter Notebook: Choose this VM if you are familiar with setting up Python-based Notebooks, or if you just exported one or multiple studies from the Discovery Page and want to start your custom analysis.
- (Generic) R Studio: Choose this VM if you are familiar with R Studio-based data analysis tools. This workspace will offer a RStudio environment.
- (Generic, User-licensed) Stata Notebook: Choose this VM if you are familiar with STATA-based data analysis. This notebook requires a STATA license.
-
Tutorial Notebooks:
Explore our Jupyter Notebook tutorials written in Python or RStudio,
which pull data from various sources of the
HEAL Data Ecosystem to leverage statistical programs
and data analysis tools.
All interactive tutorial notebooks can be also found as static version on the Notebook Browser tab; read more in the section "Static Notebooks".
Feel free to edit and experiment with this collection of notebooks. They are your personal copies!
- Notebooks in Python: (1) Bacpac Synthetic Data Analysis, (2) JCOIN Tracking Opioid Stigma, (3) Opioid Overdose Trajectories, (4) Opioid Prevalence And Overdoses
- Notebooks in RStudio: (1) OEPS and Opioid Toolkit
-
Click “Launch” on any of the above workspace flavors to spin up a copy of that VM. Note: Launching the VM may take several minutes.
The status of launching the workspace is displayed after clicking on “Launch”.
-
After launching, the home folders are displayed, one of which is the user's persistent drive ("pd").
The /pd directory is a user’s persistent drive.
-
Select the /pd folder. Only files saved in the /pd directory will remain available after termination of a workspace session.
New files or licenses should be saved in the the /pd directory if users need to access them after restarting the workspaces.
- Do not save files in the "data" and “data/healdata.org” folders.
- The folder “healdata.org” in the “data” folder will host the data files you have exported from the Discovery Page.
- Attention: Any personal files in the folder “data” will be lost. Personal files in the directory /pd will persist. -
Start a new workspace by clicking “New” in the top right corner and choose between Python 3 or R Studio as the base programmatic language.
Start a new notebook under “New”.
-
Experiment away!
Code blocks are entered in cells, which can be executed individually or all at once. Code documentation and comments
can also be entered in cells, and the cell type can be set to support Markdown.
Results, including plots, tables, and graphics, can be generated in the workspace and downloaded as files.
Users can import data files directly into the Notebook code after selecting files from the "Discovery Page". An example is shown below.
-
Do not forget to terminate your workspace once your work is finished to be mindful of
the cost-intensive computational effort. Note, that Workspaces automatically
shut down after 90 minutes of idle time.
Do not forget to terminate your workspace once your work is finished. Unterminated workspaces continue to accrue computational costs.
Upload, save, and download Files/Notebooks
Users can upload data files or Notebooks from the local machine to the home directory by clicking on “Upload” and access them in the Notebook (see below).
Then run in the cells, for example:
import os
import pandas as pd
os.chdir('/data')
demo_df = pd.read_csv('/this_is_a_demo.txt', sep='\t')
demo_df.head()
Users can save the notebook by clicking "File" - "Save as", as shown below.
Users can download notebooks by clicking "File" - "Download as", as shown below.
Environments, Languages, and Tools
The following environments are available in the workspaces:
-
Jupyter
-
RStudio
(read more)
The following programmatic languages are available in Jupyter Notebooks:
The following tools are available in Jupyter Notebooks:
- GitHub (read GitHub documentation)
Python 3 and RStudio in Jupyter
Both Python 3 and RStudio are available in Jupyter Notebooks.
Users can expect to be able to use typical Python or RStudio packages, such as PyPI or CRAN.
For Python and RStudio, users can start a new notebook under "New", as shown below.
STATA in Jupyter
STATA is available as language in Jupyter notebooks (either in Python or R kernels), but requires a license and a specific workspace.
Users need to first choose the following workspace "(Generic, User-licensed) Stata Notebook" in order to be able to use STATA:
Users need to upload a license stata.lic
to the /pd folder by selecting "Upload" (top right).
Note, that uploading the license can also be achieved programmatically by
opening a new terminal window under "New" - "Terminal", finding the directory
/pd by typing:
cd pd
. Then, create a file using vim:
vim stata.lic
.
This will open the file in the terminal.
Users can copy the license, then hit :
+ wq
.
Then, users need to start a new notebook under "New" (choose either R or Python).
Run the following code in the first cell:
import stata_setup
stata_setup.config("/usr/local/stata17", "mp")
This will return the following:
Users can then begin using the notebook by typing in known STATA commands, for example
%% stata . describe
.
RStudio environment
Users can make use of the preinstalled RStudio environment by launching the following workspace:
Find exported data files in manifests by selecting "Terminal" on the left side, and typing
cd ../../data/healdata.org
Troubleshooting
- If the kernel died, make sure to be logged in on 1) the Login Page 2) have enabled access to the FAIR enabled repository
f) Static Notebooks
The Static Notebooks page contains a collection of view-only tutorial Jupyter Notebooks that provide demo analyses of datasets published on the HEAL platform.
This tab acts as a visual ‘table of contents’ of available HEAL datasets.
Why static Notebooks?
These notebooks will allow users to learn how to analyze and visualize data available on the HEAL platform - without having to take the additional steps of finding and exporting the data used by the tutorial first.
All tutorial notebooks are static, view-only, and can be downloaded as.html
files.
Find the notebooks in interactive mode in the Workspace tab.
Find below a description of how to work with the tutorials in the workspaces.
These tutorial notebooks are meant to:
- Give users a sense for how the platform can be used to analyze data.
- Bring complementary datasets together.
- Be used as a launching point for the users’ own custom analysis.
- Spark imagination about how users can incorporate the platform data access, analysis, and collaboration tools into their own research and data analysis process and pipelines.
The “Static Notebooks” tab will be regularly updated with new and exciting tutorial data analysis notebooks, as more datasets are published and brought together in novel ways on the Platform.
Currently available Notebooks
Find below a list of notebooks that are currently available and which datasets they’re based on.
Click here to watch demo videos about how to use the tutorial Jupyter Notebooks as a launching point for your own custom analysis.
|
Notebook Name |
Project Title |
Project Number |
Datasets used | Language | Needs linking access to FAIR (which one)? |
|---|---|---|---|---|---|
| BACPAC synthetic data analysis |
Back Pain Consortium (BACPAC) Research Program Data Integration, Algorithm Development and Operations Management Center |
1U24AR076730-01 |
1) participant_ SMART.tsv 2) substance_use_ SMART.tsv 3) physical_function_ SMART.tsv |
Python | |
| Tracking Stigma related to Opioid Use Disorder |
Methodology and Advanced Analytics Resource Center |
1U2CDA050098-01_a |
1) JCOIN_NORC_ Omnibus_SURVEY1_ Feb2020.sav 2) JCOIN_NORC_ Omnibus_SURVEY2_ April2020.sav 3) JCOIN_NORC_ Omnibus_SURVEY3_ June2020.sav 4) JCOIN_NORC_ Omnibus_SURVEY4_ Oct2020.sav |
Python | JCOIN |
| Opioid Prevalence And Overdoses |
1) Drug Enforcement Administration Controlled Substances Tracking (DEA ARCOS) 2) Prescription Drug Abuse Policy System 2b) 3) CDC Wide-ranging Online Data for Epidemiologic Research (CDC WONDER) Mortality Multiple Cause-of-Death Public Use Record |
1) deaarcos1 2) 57b45d83d6 c9e7e8693ccdfd 3) cdcwonder |
1a) dea_arcos_drug_list.tsv 1b) dea_arcos_county_ population.tsv 1c) dea_arcos_combined_ county_annual.tsv 1d) dea_arcos_state_population.tsv 2a) 20170216-RM-Stat-Data.xlsx 2b) Naloxone_Data_09112020.xlsx 2c) 20180810_Good_Samaritan_ Law_Stat_Data.xlsx 3a) CDC_WONDER_unintentional_ overdoses.tsv 3b) CDC_WONDER_suicide_ overdoses.tsv 3c) monthly_unintentional_ overdoses.tsv |
Python | FAIR |
| OEPS And Opioid Toolkit (Watch tutorial) |
Methodology and Advanced Analytics Resource Center |
1U2CDA050098-01_b |
1) ZIP_COUNTY.xlsx 2) us-wide-moudsCleaned.csv 3) zctas2018.shp |
RStudio | JCOIN |
| Opioid Overdose Trajectories (Watch tutorial) |
CDC Wide-ranging Online Data for Epidemiologic Research (CDC WONDER) Mortality Multiple Cause-of-Death Public Use Record |
cdcwonder |
1) deaths_gender.xlsx 2) deaths_age_cat.xlsx 3) deaths_type_opioid.xlsx 4) cdc_wonder_year_cause_ hedegaard_et_al_2020.txt 5) cdc_wonder_year_cause_ state_hedegaard_et_al_2020.txt |
Python |
Working with the Tutorial Notebooks in interactive mode
-
The data used by the tutorial
notebook must be exported
from the Discovery page to the workspace
to work with the tutorial Jupyter Notebooks in interactive mode.
The previous section lists which data is required to import from the Discovery Page.
All exported data will be stored in the pd/data/healdata.org/manifest-YYYY-MM-XXXX-XX-XX.XXXXXX
folder.
-
Some notebooks require linked access to FAIR enabled repositories,
as described here.
The previous section lists if the notebook needs linking access to FAIR enabled repositories.
- Code in the notebooks is editable, and users can import additional datasets and extend their analysis.
Demo - How to find data and work on the Tutorial Notebooks
Below we describe the steps to export data from the Discovery Page tutorial Jupyter notebooks for one example tutorial notebook HEAL_Workspace_Demo_BACPAC.ipynb (“BACPAC synthetic data analysis”)
This example notebook does not require linking access to a FAIR repository. Please see the table in the previous section if the notebook of interest requires linking access.
Users must be logged in to follow the steps below.
-
Find and select the study by the project number (in this example: 1U24AR076730-01)
on the Discovery Page.
Project numbers and datasets are given in the previous section.
-
Click the “Open in Workspace” button in the upper right corner. This step will create a manifest folder which you can find later in the Workspace’s folder "data/healdata.org".
Select the study and click on “Open in Workspace”.
-
Go to the Workspace tab and click “Launch” on the “Bacpac Synthetic Data Analysis Notebook”. This may take a few minutes to load.
Note, that depending on the chosen notebook, this step varies to align with the name of the notebook/workspace.
-
Find and open the notebook in the landing directory.
Open the notebook by clicking on “HEAL_Workspace_Demo_BACPAC".
-
Click the first two cells and run them by clicking into the cell and either using shift+enter on the keyboard or selecting “Run”:
-
Run the next cell, making sure you copy the name of the exported manifest folder, as shown below:
-
Explore the rest of the notebook. If you want to make changes, make sure to save the notebook as a new file in the directory "pd".
- Make sure to terminate the workspace when the work is finished to reduce computational costs.
Note: Work must be saved in the directory "/pd" in order to remain accessible after workspace termination. Note, that Workspaces automatically shut down after 90 minutes of idle time.
g) Profile Page
On the profile page users will find information regarding their access to projects, access to Gen3-specific tools (e.g. access to the /workspace), and the function to create API keys for credential downloads. API keys are necessary for the downloadof files using the Gen3-client; for more information see chapter 4.
5. Downloading Data Files
Users can download data files associated with a study by downloading the files directly from the Discovery page, or leveraging the CTDS-owned python software development kit (SDK) and the tool “Gen3-client” if the file size exceeds 250 MB.
Note that current studies that have datasets of more than 250 MB are those with the following project numbers: a) cdcwonder and b) deaarcos1.
Note, that accessing some data files require linked access to FAIR enabled repositories, as described here.
a) Download Data Files from the Discovery Page
Users can download data files up to sizes of 250 MB directly from the Discovery Page.
Below you find the simple steps to do so.
-
Navigate to the Discovery Page.
-
Find the study of interest by using the search features
or the list of accessible studies.
-
Select the clickable box next to the study.
Click on "Download ZIP", which will initiate the data download.
Select the study and click "Download ZIP".
-
Users will be prompted with a window that shows the download is being prepared.
Please do not navigate away from this page until the download is complete.
After clicking "Download ZIP", your download is being prepared. Please do not navigate away from this page until the download is complete.
-
Users will be notified once the download is ready. If the download doesn't start automatically,
please follow the link prompted.
Users will be notified once the download is ready. Save the file(s) by selecting the directory using the prompted window.
-
If the file size exceeds 250 MB, users will be notified to deselect studies to reduce the size
or use other tools:
Users are advised to use other tools to download the files if the total file size exceeds 250 MB. Please see the next section for a step-by-step guide using these tools.
b) Download Data Files using the Gen3-client
In order to download data files above 250 MB, users will need to utilize the Gen3-client command line tool developed by the University of Chicago’s Center for Translational Data Science.
The current studies that have datasets of more than 250 MB are those with the following project numbers: a) cdcwonder and b) deaarcos1.
Find below a guide to download data files using the Gen3-client:
-
Log in to the Data Commons on healdata.org/login
- Find and select one or multiple studies of interest on the Discovery Page. For multiple studies, select "Data Availability" in the top right corner, click “Available”, and choose multiple studies.
-
Click on the button “Download".
Select a study of interest, then click on the button “Download".
-
Create and download an API key from your Profile Page. Note where you save the API key on your local machine.
Create an API key on the profile page.
Download the API key as json file and note the directory where the API key was saved for step 6.
-
Download and configure the Gen3-client
a. Follow the download instructions of the Gen3-client here. The client can be downloaded here.
b. In your terminal, configure your profile using the following command:
gen3-client configure --profile=<profile_name> --cred=<credentials.json> --apiendpoint=<api_endpoint_url>
#Mac/Linux:
gen3-client configure --profile=demo
--cred=~/Downloads/demo-credentials.json --apiendpoint=https://healdata.org/
#Windows:
gen3-client configure --profile=demo
--cred=C:\Users\demo\Downloads\demo-credentials.json --apiendpoint=https://healdata.org/
#Output:
10:08:20 Profile 'demo' has been configured successfully.
If successfully executed, a configuration file will be stored under the directory the user specified under “cred”. For troubleshooting, refer to the instructions found here.
c. Download files by using the following command, which references the manifest file name and its location:
gen3-client download-multiple --profile=<profile_name> --manifest=<manifest_file> --download-path=<path_for_files>
gen3-client download-multiple --profile=demo --manifest=manifest.json --download-path=downloads
#Output:
2021/06/03 16:48:46 Reading manifest...
200 B / 200 B [===================] 100.00% 0s
WARNING: flag "rename" was set to false in "original" mode, duplicated files under "downloads/" will be overwritten
Proceed? [y/n]: y
2021/06/03 16:48:47 Total number of GUIDs: 1
2021/06/03 16:48:47 Preparing file info for each file, please wait...
1 / 1 [============================================] 100.00% 0s
2021/06/03 16:48:47 File info prepared successfully
arcos_all_washpost.tsv.gz 6.41 GiB / 6.41 GiB [=======================================================] 100.00% 0s
6. FAQ
-
What can I do on the HEAL Platform?
The HEAL Platform is a cloud-based and multifunctional web interface that provides a secure environment for discovery and analysis of HEAL results and data. Explore all functionalities here.
-
Which datasets are currently open-access?
Find all open-access datasets here.
-
Where can I see individual study metadata?
Individual study metadata is shown upon clicking on a study entry on the Discovery Page. Click to read the full description here.
-
How and where can I see if I have access to a study?
Clicking on an individual study on the Discovery Page will show in the top right corner if they are accessible to the user. To see all studies users have access to, users should navigate to the Discovery Page and select “Data Availability” - Available”. More information here.
-
I do not have access to a specific study, how can I get access?
RENCI/RTI (Renaissance Computing Institute) at the University of North Carolina at Chapel Hill establishes and manages data access contacts over all data contributors/sources. To request access to controlled data, users should contact RENCI/RTI at<EMAIL_ADDRESS>-
The profile page says I have access but I don’t see it on the Discovery Page.
Please contact our help desk.
-
Do I need to store my data in a particular location, repository, or
database in to participate in the HEAL platform?
You must store your data in a HEAL-approved repository. A HEAL-approved repository is a data repository that is NIH-approved AND positively has an API for metadata, data, and data permissions calls.
-
How do I find a HEAL-approved repository in which to store my data?
Please reach out to RENCI for further questions on this topic.
-
Are there costs that will be the responsibility of individual investigators associated with data storage in a HEAL-approved repository now and in the future?
Please reach out to RENCI for further questions on this topic.
-
I would like to download data files from a specific study, what do I need to do?
Users can download the studies directly from the Discovery Page as described here, or, if the file size exceeds 250 MB, users need to use the Gen3-client command line tool to download data files, as described here. Additional information on the Gen3-client may be found here.
-
How can I get data files into the Workspace from the Discovery Page?
Click here to follow the steps on how to get files from the Discovery Page to the Workspace.
-
How do I find a study?
Click here to see possible ways to search for a study on the Discovery Page.
-
Can I download files directly from the portal?
Yes, you can. Click here to follow the steps to download data files from the Discovery Page. Caution: the download is limited to file sizes of 250 MB.
-
My download is not working.
Please check if your file size exceeds 250 MB. If yes, please other tools as described here to download the files. Note that the current studies that have datasets of more than 250 MB are those with the following project numbers: a) cdcwonder and b) deaarcos1. If errors persist, please contact the help desk.
-
My data file download using the Gen3-client gets stuck, where can I get help?
For troubleshooting, please see the Gen3-client documentation here. If errors persist, contact our help desk.
-
The Gen3-client shows errors, where can I get help?
To check that the client is working and to confirm the client version, type ‘gen3-client’ in the terminal. Typing ‘gen3-client help’ will display the help menu. Users must provide the full path of the tool in order for the commands to run, for example, ‘./gen3-client’ while working from the directory containing the client.
For more troubleshooting, please see the Gen3-client documentation here. If errors persist, contact our help desk.
-
I want to work interactively on the Tutorial Notebooks. Show me how.
Click here to follow the steps of a demo.
-
What are the current Tutorial Notebooks?
Click here to see a list of currently available Notebooks in Python and R.
-
How do I work with these Tutorial Notebooks?
Click here to see a guide of how to work with the Tutorial Notebooks.
-
How do I link my account to a FAIR enabled repository?
Click here to see how to link your account to a FAIR enabled repository.
-
What do the Workspaces have to offer?
Click here to see how to get started and here to see what languages, tools, and environments the workspaces have enabled.
-
I want to report a bug!
Please report any errors or bugs to our help desk.
7. Tutorial Videos
Watch our tutorial videos to learn how to interact with the HEAL Platform, export data files from the Discovery Page, and use the tutorial Jupyter Notebooks as a launching point for your own custom analysis.
-
“HEAL Platform Tutorial”
Watch this video to start learning about all features on the HEAL Platform.
If your Browser does not support watching this video, here's a link to the video instead.
-
“The Opioid Environment Toolkit and OEPS”
This tutorial video demonstrates the use of the HEAL Platform Workspace through the analysis for the Opioid Environment Policy Scan Dataset using statistical tools written in the R programming language.
If your Browser does not support watching this video, here's a link to the video instead.
-
“Opioid Overdose Trajectories”
This tutorial video demonstrates the use of the HEAL Platform to reproduce findings of a CDC study of Opioid Overdose Death rates in the United States.
If your Browser does not support watching this video, here's a link to the video instead.
Contact
Need help? Please contact our help desk.


Here you can decrypt a message (e.g. a password).
Send this to your friend who wants to encrypt the message (its your 2048 bit public key, it is safe to share):
DO NOT RELOAD THE PAGE until your friend has sent you the encrypted message. The public key on this page is a one-time use public key only.
Input the message here that your friend has encrypted with your public key:
Below should appear your message...
{{decrypt.decrypted.message}}


|
XPMP2
X-Plane multiplayer library 2 - using instancing
|
XPMP2 provides TCAS blibs and AI/multiplayer data using TCAS Override introduced with X-Plane 11.50 Beta 8. Please do read that blog post by Laminar as it explains all what's necessary and what also XPMP2 does:
XPLMAcquirePlanes
. All what follows only happens if XPMP2 was granted access:sim/operation/override/override_TCAS
to 1 to tell X-Plane that it will use TCAS Overridesim/operation/override/override_multiplayer_map_layer
to 1 to tell X-Plane that it shall not draw icons into the map as XPMP2 provides a self-defined additional map layerXPMP2::Aircraft::aiPrio
), for each aircraft a number of dataRefs are set, see belowXPLMSetActiveAircraftCount
X-Plane is informed about the exact number of provided planes. (This might not be strictly necessary, but probably a cleaner approach than to wait 10 cylces for not updated dataRefs to be taken out of X-Plane's consideration.)When TCS Override is not available (like up to X-Plane 11.41), then TCAS is provided by writing the classic multiplayer dataRefs directly.
There is a limited number of "slots" available for TCAS/multiplayer purposes. With TCAS Override, this is currently 63, with classic multiplayer dataRefs, this is up to 19, though for many 3rd party plugins the number of actually configured AI Aircraft (X-Planes Flight Setup) plays a role, too.
XPMP2 will show the aircraft closest to current camera location. This set of aircraft will change over time. But XPMP2 will try to keep a plane, which once was shown on TCAS, in the same slot to make it easier for 3rd party plugins to follow one plane.
Keeping a plane in one slot has limits. The following rules apply:
n
slots, for which AI Aircraft are configured, are considered "lower range" because some 3rd party plugins only access as many planes as are configured as AI Aircraft (though this is unnecessary: plugins could just read all 19 dataRefs irrespective of what XPLMCountAircraft
returns.)XPMP2 writes the folloing TCAS target dataRefs when it has TCAS control:
.../tcas/targets/ | XPMP2's value from XPMP2::Aircraft |
|---|---|
modeS_id | modeS_id |
modeC_code | acRadar.code |
flight_id | what GetFlightId() returns: acInfoTexts.flightNum or acInfoTexts.tailNum or acInfoTexts.aptFrom -acInfoTexts.aptFrom , whatever is available first; this is a virtual function that you can override in your implementation |
icao_type | acIcaoType |
All dataRefs under sim/cockpit2/tcas/targets/position/
are filled as expected and documented except for weight_on_wheels
, for which no value in XPMP2::Aircraft::v
is yet available:
Values are taken from XPMP2::Aircraft::v
. Compare the indexes as defined in the enum DR_VALS
defined in XPMPAircraft.h
:
.../tcas/targets/position/ | XPMP2's value from XPMP2::Aircraft |
|---|---|
x , y , z | drawInfo.x , drawInfo.y - ac.GetVertOfs() , drawInfo.z |
vx , vy , vz | updated once a second with deltas of respective values in drawInfo devided by time passed |
psi | drawInfo.heading |
the | drawInfo.pitch |
phi | drawInfo.roll |
flap_ratio | v[V_CONTROLS_FLAP_RATIO] |
gear_deploy | v[V_CONTROLS_GEAR_RATIO] |
flap_ratio2 | v[V_CONTROLS_FLAP_RATIO] |
speedbrake_ratio | v[V_CONTROLS_SPEED_BRAKE_RATIO] |
slat_ratio | v[V_CONTROLS_SLAT_RATIO] |
wing_sweep | v[V_CONTROLS_WING_SWEEP_RATIO] |
throttle | v[V_CONTROLS_THRUST_RATIO] |
yolk_pitch | v[V_CONTROLS_YOKE_PITCH_RATIO] |
yolk_yaw | v[V_CONTROLS_YOKE_HEADING_RATIO] |
yolk_roll | v[V_CONTROLS_YOKE_ROLL_RATIO] |
lights | v[V_CONTROLS_TAXI_LITES_ON] , v[V_CONTROLS_LANDING_LITES_ON] , v[V_CONTROLS_BEACON_LITES_ON] , v[V_CONTROLS_STROBE_LITES_ON] , v[V_CONTROLS_NAV_LITES_ON] |
weight_on_wheels | - |
...is provided by X-Plane automatically when feeding above TCAS target dataRefs. That means: The lower 19 planes are mirrored into the well-known sim/multiplayer/position/plane#_*
dataRefs. Plugins still relying on these dataRefs will mainly "just work". And this without any workarounds like defining AI Aircraft in X-Plane's settings!
Please note that XPLMCountAircraft
can now return values larger than 20, up to 64 at the moment.
XPMP2 still makes sure that unused sim/multiplayer/position/plane#
slots (ie. if less than 19 planes are shown) are initialised with _x/y/z
set to 9999999.9
. They are deliberately not set to 0
if unused, because 0/0/0 is a totally valid local geographic location.


Tabs organize content in separate views.
The mode
property controls the type of the Tabs. For individual tabs set
mode="individual"
and for line tabs set mode="line"
. Omit this property for
default tabs.
Keyboard navigation: use the tab key to navigate the tabs and the space bar or enter to toggle them.


Preferences
Preferences
Options for the application's behavior
Triggers
Define hot keys or other input types
Catalog
Define the items included in a search
Plug-ins
Install plug-ins to extend Quicksilver
Resources
Documentation
of Quicksilver's features
Forums
offering hints, help, and ideas from other users. Suggestions and comments are welcome.
IRC Chat
with developers and users. Requires a
client
.
Check For Updates
to Quicksilver


| Oracle® Exadata Database Machine and Oracle SuperCluster README for Oracle Exadata Deployment Assistant Update 20505944 11g Release 2 (11.2) and 12c Release 1 (12.1) |
|
README for Oracle Exadata Deployment Assistant Update 20505944
11g Release 2 (11.2) and 12c Release 1 (12.1)
February 2015
This document describes how to apply the Oracle Exadata Deployment Assistant update. It contains the following topics:
Section 2, "Prerequisites for Oracle Exadata Deployment Assistant Deployment Tool"
Section 3, "About Oracle Exadata Deployment Assistant Deployment Tool"
Oracle Exadata Deployment Assistant includes a configuration tool, and a deployment tool. It uses the XML data file created by the configuration tool to configure the Oracle Exadata system.
Oracle Exadata Deployment Assistant configuration tool runs on a client. The client must run one of the following operating systems:
Oracle Linux x86-64
Oracle Solaris x86-64 (64-bit)
Oracle Solaris SPARC (64-bit)
Microsoft Windows
Apple OS X (64-bit)
Download the appropriate file for the client operating system. For example, if Oracle Exadata Deployment Assistant configuration tool is to be run on a Microsoft Windows client, then download the Microsoft Windows file. The operating system of the client does not have to match the operating system of the engineered system.
|
See Also: Oracle Exadata Database Machine Owner's Guide for additional information about Oracle Exadata Deployment Assistant |
The following changes are included in this release of Oracle Exadata Deployment Assistant:
Added support for Oracle Database 12c Release 1 (<IP_ADDRESS>) DBBP5, and mandatory Oracle Java Virtual Machine (OJVM) patch set update 19877336.
Added step to the installation process that allows pkey interface configuration using the ipconf script.
Added support to handle bonded InfiniBand interfaces during pkey setup.
Added support to enable the infinicheck
command when pkey is not enabled.
Added fix for bug 20287585 on top of release <IP_ADDRESS> DBBP3 for 8-socket systems.
Support for Oracle Exadata Database Machine X5-2.
Support for Oracle Exadata Database Machine X4-8 with Exadata Storage Server X5-2 Servers.
Support for Oracle Exadata Database Machine X5-2 elastic configurations.
Support for Oracle Virtual Machine user domains on Oracle Exadata Database Machine two-socket racks.
Added support for Oracle Database 12c Release 1 (<IP_ADDRESS>) DBBP4, and mandatory Oracle Java Virtual Machine (OJVM) patch set update 19877336.
Added support for Oracle Database 12c Release 1 (<IP_ADDRESS>) PSU6, and mandatory Oracle Java Virtual Machine (OJVM) patch set update 19877342.
Added support for Oracle Database 11g Release 2 (<IP_ADDRESS>) BP15, and mandatory Oracle Java Virtual Machine (OJVM) patch set update 19877440.
Added support for Oracle Database 11g Release 2 (<IP_ADDRESS>) BP26, and mandatory Oracle Java Virtual Machine (OJVM) patch set update 19877443.
Added support for Oracle Database 12c Release 1 (<IP_ADDRESS>) DBBP3, and mandatory Oracle Java Virtual Machine (OJVM) patch set update 19282028.
Added support for Oracle Database 11g Release 2 (<IP_ADDRESS>) BP14, and mandatory OJVM patch set update 19282021, and JDBC patch 19852360.
Added support for Oracle Database 12c Release 1 (<IP_ADDRESS>) DBBP2, and mandatory Oracle Java Virtual Machine (OJVM) patch set update 19282028 (for both DBBP1 and DBBP2).
Added support for Oracle Database 12c Release 1 (<IP_ADDRESS>) mandatory OJVM patch set update 19282024, and Java Database Connectivity (JDBC) patch 19852357 (for PSU5).
Added support for Oracle Database 11g Release 2 (<IP_ADDRESS>) mandatory OJVM patch set update 19282021, and JDBC patch 19852360 (for both BP13 and BP12).
Added support for Oracle Database 11g Release 2 (<IP_ADDRESS>) mandatory OJVM patch set update 19282015, and JDBC patch 19852361 (for BP25).
Added support for identification and configuration of additional spine switches during initial data configuration.
Updated the initial Oracle Exadata Deployment Assistant configuration screen to have options for Oracle Exadata Database Machine, Oracle Zero Data Loss Recovery Appliance, and Oracle SuperCluster.
Added support for Oracle Database 12c Release 1 (<IP_ADDRESS>) DBBP1.
Added support for Oracle Database 12c Release 1 (<IP_ADDRESS>) PSU5.
Added support for Oracle Database 11g Release 2 (<IP_ADDRESS>) Patch Set 3 BP12.
Added support for Oracle Database 11g Release 2 (<IP_ADDRESS>) Patch Set 2 BP25.
Reduced setup time for the Cell Alerting configuration step.
Updated the bash rpm on Linux database and storage servers to counter the bash shell vulnerability CVE-2014-6217 and CVE-2014-7169.
Support for Zero Data Loss Recovery Appliance.
Added support for Oracle Database 11g Release 2 (<IP_ADDRESS>) Patch Set 3 BP11.
Added a timestamp to the Installation Template report.
Updated the checkip.sh
script so that it no longer displays incorrect errors for Oracle Exadata Storage Expansion Rack.
Updated Oracle Exadata Deployment Assistant deployment tool so that NTP services (ntpd) are restarted before the Install Cluster Software step.
Added support for Oracle Database 11g Release 2 (<IP_ADDRESS>) Patch Set 3 BP10.
Implemented a set of questions in Oracle Exadata Deployment Assistant to clarify the proposed installation.
Enabled appliance.mode
attribute for disk groups in Oracle Database releases <IP_ADDRESS> and <IP_ADDRESS> deployments.
Enhanced Oracle Exadata Deployment Assistant validation check to disable active-active bonding on Oracle Exadata Database Machine X4-2 Solaris X64 deployments.
Corrected the reported Oracle ASM disk group size in the installation template for eighth rack deployments.
Corrected the number of InfiniBand adapters created in Oracle SuperCluster Zones deployment.
Implemented a full set of new database DBCA templates for Oracle SuperCluster deployments.
Corrected intermittent delay at the end of the Initialize Cluster step.
Fixed issues with the Apply Security Fixes step.
Addition of the Platinum support page to capture customer information.
Length validation for InfiniBand switch host names.
Corrections to the Oracle Exadata Database Machine X4-8 DBCA template.
Support for multiple InfiniBand adapters in Oracle SuperCluster Zones.
Removal of reverse DNS lookup validation in step 1 of the installation.
Note the following guidelines when using Oracle Exadata Deployment Assistant deployment tool:
Do not run Oracle Exadata Deployment Assistant deployment tool on Exadata Storage Servers.
When used for deployment, Oracle Exadata Deployment Assistant is run on any of the following systems that can access the Exadata database servers:
Oracle Exadata Database Machine database server
Oracle SuperCluster database domain
Oracle SuperCluster database zone
Microsoft Windows machine
Oracle Linux machine
Oracle Solaris SPARC machine
Apple OS X machine
The examples in this document are from using a database server on Oracle Exadata Database Machine.
The deployment tool script, install.sh
, requires the XML data file created by the configuration tool script, config.sh
, and the compressed software files from Oracle Technology Network for the software release being deployed.
|
Note: If patches are downloaded from My Oracle Support instead of Oracle Technology Network, then rename the My Oracle Support files to match the names shown in this document. |
Review My Oracle Support note 888828.1 for the latest information about issues, workarounds and guidelines about this update. My Oracle Support note 888828.1 is updated regularly with new information after a patch release.
Oracle Exadata Deployment Assistant update 20505944 supports the following Oracle Database releases and platforms:
|
Note: The requirements for Exadata Storage Servers and database servers listed in My Oracle Support note 888828.1 must be met before installing Oracle Database 12c Release 1 (<IP_ADDRESS>) or Oracle Database 12c Release 1 (<IP_ADDRESS>). |
Oracle Database 12c Release 1 (<IP_ADDRESS>) DBBP1 through DBBP5
Oracle Linux x86-64
Oracle Solaris x86-64 (64-bit)
Oracle Solaris SPARC (64-bit)
Oracle Database 12c Release 1 (<IP_ADDRESS>) GIPSU1 through GIPSU6
Oracle Linux x86-64
Oracle Solaris x86-64 (64-bit)
Oracle Solaris SPARC (64-bit)
Oracle Database 11g Release 2 (<IP_ADDRESS>) Patch Set 3 BP1 through BP15
Oracle Linux x86-64
Oracle Solaris x86-64 (64-bit)
Oracle Solaris SPARC (64-bit)
Oracle Database 11g Release 2 (<IP_ADDRESS>) Patch Set 2 BP3 through BP26
Oracle Linux x86-64
Oracle Solaris x86-64 (64-bit)
Oracle Solaris SPARC (64-bit)
The directory needs approximately 10 GB of free space. The following directory is created, depending on the operating system:
Oracle Linux x86-64: /opt/oracle.SupportTools/onecommand/linux-x64
Oracle Solaris x86-64 (64-bit): /opt/oracle.SupportTools/onecommand/solaris-x64
Oracle Solaris SPARC (64-bit): /opt/oracle.SupportTools/onecommand/solaris-sparcv9
The following procedure describes how to extract the file:
Ensure the /opt/oracle.SupportTools
directory has at least 10 GB of free space.
Create the /opt/oracle.SupportTools/onecommand
directory, if it does not exist.
Run the following command:
unzip -d /opt/oracle.SupportTools/onecommand p20505944_121111_platform
.zip
Oracle Exadata Deployment Assistant deployment tool requires patches available from Oracle Technology Network. The required files depend on the Oracle Database release to be installed by the utility. The downloaded files should be placed in the /opt/oracle.SupportTools/onecommand/
platform
/WorkDir
directory in the destination path.
|
Note: If patches are downloaded from My Oracle Support instead of Oracle Technology Network, then rename the My Oracle Support files to match the names shown in this document. |
This section contains the following topics:
Section 2.1, "Requirements When Installing Oracle Database 12c Release 1 (<IP_ADDRESS>)"
Section 2.2, "Requirements When Installing Oracle Database 12c Release 1 (<IP_ADDRESS>)"
Section 2.3, "Requirements When Installing Oracle Database 11g Release 2 (<IP_ADDRESS>)"
Section 2.4, "Requirements When Installing Oracle Database 11g Release 2 (<IP_ADDRESS>)"
|
See Also: "Oracle Exadata Deployment Assistant Support for Oracle Virtual Machines" for information about the required files for Oracle VMs. |
Oracle Database 12c Release 1 (<IP_ADDRESS>) can be installed on Oracle Exadata Database Machine and Oracle SuperCluster. The following requirements for Exadata Storage Servers and database servers must be met before installing Oracle Database 12c Release 1 (<IP_ADDRESS>):
The requirements stated in My Oracle Support note 888828.1 to run Oracle Database 12c release 1 (12.1) with Exadata Storage Servers.
Patch 6880880, OPatch release <IP_ADDRESS>.2 or later.
Patch 19774304, Database Patch for Engineered Systems and DB In-Memory <IP_ADDRESS>.2 (Nov2014) DBBP3.
Patch 18622611, Oracle Exachk utility.
The following files from Oracle Technology Network, depending on the operating system of Oracle Exadata Database Machine:
Oracle Linux x86-64:
linuxamd64_12102_grid_1of2.zip linuxamd64_12102_grid_2of2.zip linuxamd64_12102_database_1of2.zip linuxamd64_12102_database_2of2.zip
Oracle Solaris x86-64 (64-bit)
solaris.x64_12102_grid_1of2.zip solaris.x64_12102_grid_2of2.zip solaris.x64_12102_database_1of2.zip solaris.x64_12102_database_2of2.zip
Oracle Solaris SPARC (64-bit)
solaris.sparc64_12102_grid_1of2.zip solaris.sparc64_12102_grid_2of2.zip solaris.sparc64_12102_database_1of2.zip solaris.sparc64_12102_database_2of2.zip
The files are available at
http://www.oracle.com/technetwork/database/enterprise-edition/downloads/index.html
The patch for the relevant DBBP being deployed. The following are the DBBP and patch numbers for release <IP_ADDRESS>:
DBBP Patch Number Required Additional Patches 5 20329440 OJVM PSU2 19877336 4 20141343 OJVM PSU2 19877336 3 20026159 OJVM patch set update 19282028 2 19774304 OJVM patch set update 19282028 1 19404326 OJVM patch set update 19282028
Oracle Database 12c Release 1 (<IP_ADDRESS>) can be installed on Oracle Exadata Database Machine and Oracle SuperCluster. The following requirements for Exadata Storage Servers and database servers must be met before installing Oracle Database 12c Release 1 (<IP_ADDRESS>):
The requirements stated in My Oracle Support note 888828.1 to run Oracle Database 12c release 1 (12.1) with Exadata Storage Servers.
Patch 6880880, OPatch release <IP_ADDRESS>.2 or later.
Patch 18622611, Oracle Exachk utility.
The following files from Oracle Technology Network, depending on the operating system of Oracle Exadata Database Machine:
Oracle Linux x86-64:
linuxamd64_12c_grid_1of2.zip linuxamd64_12c_grid_2of2.zip linuxamd64_12c_database_1of2.zip linuxamd64_12c_database_2of2.zip
Oracle Solaris x86-64 (64-bit)
solaris.x64_12cR1_grid_1of2.zip solaris.x64_12cR1_grid_2of2.zip solaris.x64_12cR1_database_1of2.zip solaris.x64_12cR1_database_2of2.zip
Oracle Solaris SPARC (64-bit)
solaris.sparc64_12cR1_grid_1of2.zip solaris.sparc64_12cR1_grid_2of2.zip solaris.sparc64_12cR1_database_1of2.zip solaris.sparc64_12cR1_database_2of2.zip
The files are available at
http://www.oracle.com/technetwork/database/enterprise-edition/downloads/index.html
The patch for the relevant PSU being deployed. The following are the GIPSUs and patch numbers for release <IP_ADDRESS>:
GIPSU Patch Number Required Additional Patches 6 19971324 OJVM PSU2 19877342, JDBC patch 19852357 5 19392372 OJVM patch set update 19282024, JDBC patch 19852357 4 18705901 3 18139660 2 17735306 1 17272829 Oracle patch 16057129
The following files are required when installing Oracle Database 11g Release 2 (<IP_ADDRESS>) on Oracle Exadata Database Machine and Oracle SuperCluster:
Patch 6880880, OPatch release <IP_ADDRESS>.6 or later.
Patch 13390677, Oracle Database 11g Release 2 (<IP_ADDRESS>) Patch Set 3. Only the following files from patch 13390677 are required:
p13390677_112040_platform
_1of7.zip p13390677_112040_platform
_2of7.zip p13390677_112040_platform
_3of7.zip
Patch 18622611, Oracle Exachk utility.
The patch for the relevant bundle patch being deployed. The following are the bundle patches and patch numbers for release <IP_ADDRESS>:
BP Patch Number Required Additional Patches 15 20059387 OJVM PSU2 19877440, JDBC patch 19852360 14 19893788 OJVM patch set update 19282021, JDBC patch 19852360 13 19713190 OJVM patch set update 19282021, JDBC patch 19852360 12 19542004 OJVM patch set update 19282021, JDBC patch 19852360 11 19353130 10 19023390 9 18840215 8 18632316 7 18530329 6 18371656 5 18179615 4 18006587 3 17904156 2 17838803 1 17628025
The following files are required when installing Oracle Database 11g Release 2 (<IP_ADDRESS>) on Oracle Exadata Database Machine and Oracle SuperCluster:
Patch 16042459, if Oracle Exadata Storage Server Software release is release <IP_ADDRESS>.0.
Patch 6880880, OPatch release <IP_ADDRESS>.6 or later.
Patch 16844086, for the Oracle Database software home if the Oracle Grid Infrastructure home software release is 12.1.
Patch 10404530, Oracle Database 11g Release 2 (<IP_ADDRESS>) Patch Set 2. Only the following files from patch 10404530 are required:
p10404530_112030_platform
_1of7.zip p10404530_112030_platform
_2of7.zip p10404530_112030_platform
_3of7.zip
Patch 18622611, Oracle Exachk utility.
The patch for the relevant bundle patch being deployed. The following are the bundle patches and patch numbers for release <IP_ADDRESS>:
BP Patch Number Required Additional Patches 26 19955474 OJVM PSU2 19877443, JDBC patch 19852361 25 19500593 OJVM patch set update 19282015, JDBC patch 19852361 24 18835772 23 18342655 22 17747147 21 17395890 Oracle patch 16057129 (see Note) 20 16869210 19 16784993 18 16627873 17 16474946 16 16233552 15 16039087 14 15835102 13 14786157 12 14662263 11 14474780 10 14352236 9 14229857 8 14103267 7 13992240 6 13870089 5 13734832 4 13667791 3 13556853
|
Note: Oracle patch 20116094 is needed when using release <IP_ADDRESS> Bundle Patch 25 and earlier on Oracle SuperCluster Solaris SPARC. Oracle patch 16057129 is needed when using release <IP_ADDRESS> Bundle Patch 21. In addition, the compressed patch file must be renamed to following, depending on the operating system:
|
Oracle Exadata Deployment Assistant deployment tool configures the engineered system based on the configuration information entered by the customer. Oracle Exadata Deployment Assistant is provided as a compressed file. To use Oracle Exadata Deployment Assistant, extract the file on the client server. After the file has been extracted, change to the directory that has the extracted folder, and run one of the following commands:
On Linux, Apple, and UNIX:
config.sh
On Microsoft Windows:
config.cmd
When using Oracle Exadata Deployment Assistant from a database server on Oracle Exadata Database Machine, log in as the root
user, and copy the configuration files created by Oracle Exadata Deployment Assistant to a directory on the first database server in the /u01
directory, such as the /u01/oeda
directory.
When using Oracle Exadata Deployment Assistant remotely, run the assistant from the directory that has the install.sh
file.
The following steps are performed by the assistant:
1. Validate Configuration File 2. Setup Required Files 3. Create Users 4. Setup Cell Connectivity 5. Verify Infiniband 6. Calibrate Cells 7. Create Cell Disks 8. Create Grid Disks 9. Configure Cell Alerting 10. Install Cluster Software 11. Initialize Cluster Software 12. Install Database Software 13. Relink Database with RDS 14. Create ASM Diskgroups 15. Create Databases 16. Apply Security Fixes 17. Setup ASR Alerting 18. Create Installation Summary 19. Resecure Machine
|
Note: The number of steps and step numbers may be different, depending on the features selected for configuration. |
Oracle Exadata Deployment Assistant uses the configuration files located in the ./config/
directory. These files cannot be changed or edited.
Log files are generated when using the deployment tool. The log files are located in the ./log/
directory. If there is an error when using Oracle Exadata Deployment Assistant, then open a service request, and include the diagnostics file. The diagnostics file is created in the ./WorkDir/
directory, and is a compressed file that contains information relevant to the error.
The install.sh
script is used to run Oracle Exadata Deployment Assistant. The script is run by the root
user.
The following arguments are available with the script:
-l List all the steps that exist -cf The config file name (use full path) -s <step num> Run a particular step -r <num-num> Run the steps one after the other as long as no errors are encountered -u <num-num> <step num> Undo a range of steps or a particular step -h Usage
The following examples show how to use the install.sh
script:
To run an individual step:
# ./install.sh -cf ../exadatarack1.xml -s 5
To run a range of steps:
# ./install.sh -cf ../exadatarack1.xml -r 1-3
To undo a step:
# ./install.sh -cf ../exadatarack1.xml -u 3
The steps Validate the configuration files
and Apply security fixes
cannot be undone.
To undo a range of steps:
# ./install.sh -cf ../exadatarack1.xml -u 5-3
The steps are entered in descending order.
The steps Validate the configuration files
and Apply security fixes
cannot be undone.
Starting with patch 20305033, Oracle Exadata Deployment Assistant supports virtualization. Oracle Virtual Machine (Oracle VM) deployments do not use the "bare-metal" deployment method. The target Oracle VMs are created using the deployment tool script, install.sh
. The home is created from a gold image rather than installed from the standard release media files. A gold image is a copy of a software-only, installed Oracle home. It is used to copy an image of an Oracle home to a new host on a new file system to serve as an active, usable Oracle home.
The homes are available as individual patches from My Oracle Support patch sets. Two files are required from My Oracle Support, one file for the Oracle Database home, and one for the Grid Infrastructure home. The following tables list the patch sets for the gold images.
Table 1 lists the patch sets with a gold image for Oracle Database 12c Release 1 (<IP_ADDRESS>).
Table 1 Gold Image Patch Sets for Oracle Database 12c Release 1 (<IP_ADDRESS>)
| Release | Database Patch | Grid Infrastructure Home Patch |
|---|---|---|
|
<IP_ADDRESS> DBBP 5 |
20514726 |
20514738 |
|
<IP_ADDRESS> DBBP 4 |
20406097 |
20406093 |
|
<IP_ADDRESS> DBBP 3 |
20374536 |
20374491 |
|
<IP_ADDRESS> DBBP 2 |
20374535 |
20374490 |
|
<IP_ADDRESS> DBBP 1 |
20374534 |
20374489 |
|
<IP_ADDRESS> |
20374533 |
20374488 |
Table 2 lists the patch sets with a gold image for Oracle Database 12c Release 1 (<IP_ADDRESS>).
Table 2 Gold Image Patch Sets for Oracle Database 12c Release 1 (<IP_ADDRESS>)
| Release | Database Patch | Grid Infrastructure Home Patch |
|---|---|---|
|
<IP_ADDRESS> PSU 6 |
20406098 |
20406094 |
|
<IP_ADDRESS> PSU 5 |
20374532 |
20374487 |
|
<IP_ADDRESS> PSU 4 |
20374531 |
20374486 |
|
<IP_ADDRESS> PSU 3 |
20374530 |
20374485 |
|
<IP_ADDRESS> PSU 2 |
20374529 |
20374484 |
|
<IP_ADDRESS> PSU 1 |
20374528 |
20374483 |
Table 3 lists the patch sets with a gold image for Oracle Database 11g release <IP_ADDRESS>.
Table 3 Gold Image Patch Sets for Oracle Database 11g Release <IP_ADDRESS>
| Release | Database Patch | Grid Infrastructure Home Patch |
|---|---|---|
|
<IP_ADDRESS> BP 15 |
20406099 |
20406095 |
|
<IP_ADDRESS> BP 14 |
20388394 |
20388404 |
|
<IP_ADDRESS> BP 13 |
20374527 |
20374482 |
|
<IP_ADDRESS> BP 12 |
20374526 |
20374481 |
|
<IP_ADDRESS> BP 11 |
20374525 |
20374480 |
|
<IP_ADDRESS> BP 10 |
20374524 |
20374479 |
|
<IP_ADDRESS> BP 9 |
20374523 |
20374478 |
|
<IP_ADDRESS> BP 8 |
20374522 |
20374477 |
|
<IP_ADDRESS> BP 7 |
20374521 |
20374476 |
|
<IP_ADDRESS> BP 6 |
20374520 |
20374475 |
|
<IP_ADDRESS> BP 5 |
20374519 |
20374474 |
|
<IP_ADDRESS> BP 4 |
20374518 |
20374473 |
|
<IP_ADDRESS> BP 3 |
20374517 |
20374472 |
|
<IP_ADDRESS> BP 2 |
20374516 |
20374471 |
|
<IP_ADDRESS> BP 1 |
20374515 |
20374470 |
Table 4 lists the patch sets with a gold image for Oracle Database 11g release <IP_ADDRESS>.
Table 4 Gold Image Patch Sets for Oracle Database 11g Release <IP_ADDRESS>
| Release | Database Patch | Grid Infrastructure Home Patch |
|---|---|---|
|
<IP_ADDRESS> BP 26 |
20406100 |
20406096 |
|
<IP_ADDRESS> BP 25 |
20374514 |
20374469 |
|
<IP_ADDRESS> BP 24 |
20374513 |
20374468 |
|
<IP_ADDRESS> BP 23 |
20374512 |
20374467 |
|
<IP_ADDRESS> BP 22 |
20374511 |
20374466 |
|
<IP_ADDRESS> BP 21 |
20374510 |
20374465 |
|
<IP_ADDRESS> BP 20 |
20374509 |
20374464 |
To use the gold image from the patch sets, do the following:
Download the appropriate patch sets from My Oracle Support.
Extract the files.
Copy the compressed klone
files to the ./WorkDir
directory on the machine that will run the install.sh
script.
For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc
.
Access to Oracle Support
Oracle customers that have purchased support have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info
or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs
if you are hearing impaired.
Oracle Exadata Database Machine and Oracle SuperCluster README for Oracle OneCommand Utility, 11g Release 2 (11.2) and 12c Release 1 (12.1)
Copyright © 2008, 2015, Oracle and/or its affiliates. All rights reserved.
This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.
The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.
If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable:
U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.
This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.
This software or hardware and documentation may provide access to or information about content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.


How To Create a Repository
- GO TO THE WEB ADDRESS GitHub If you are new user Create an account
- From mail verify your account and Login to your github account
- Now select New Repository
- Select Create Repository. You will be presented with the below screen
- Take some screenshots while creating the repository>
- Download Git Desktop and create directories in it
- Add the images to the directory and clone and push it


This paragraph will be replaced.
This paragraph will be replaced.
This paragraph will be replaced.
This paragraph will be replaced.


Gor Mahia Hold Al Hilal 1-1 In Benghazi In Match Laced With Peace Calls
by Bonface OsanoGor Mahia rallied to hold Al Hilal SC 1-1 in an international friendly played on Saturday at Martyrs of Benina Stadium, Benina Benghazi east of Libya.
The match was symbolic as the club sought to prove to FIFA, the world’s football body, and indeed the entire world that Libya is safe and ready for international football.
A huge banner written “Libya is a country of peace and good” was boldly mounted on the stands, a clear message of intent.
For close to a decade now since the fall of Muammar Gaddafi regime, Libya has been under FIFA ban and cannot host international games over insecurity.
Read: The Significance Of Al Hilal SC vs Gor Mahia Friendly In Benghazi To Libyan Football
Sectarian violence, which broke out in 2014 worsened the situation and led to suspension of the domestic league in April this year with clubs from Tripoli bemoaning increased violence.
Things are relatively better now especially in the east of the country where the game against Gor Mahia was staged.
The success of the meet especially in regards security, is a big plus to Hilal and authorities, who have been using sports to prove that Libya is safe.
At the end of the game the message was clear and loud, “lift the ban on Libyan stadiums.”
The message also came from the Kenya.


| SchemaSpy Analysis of limestone.tolsen - Relationships Graph | Generated by SchemaSpy |
| Generated by SchemaSpy on Wed Apr 01 10:22 GMT-05:00 2009 |
| |||||||||
| SchemaSpy Analysis of limestone.tolsen - Relationships Graph | Generated by SchemaSpy |
| Generated by SchemaSpy on Wed Apr 01 10:22 GMT-05:00 2009 |
| |||||||||


Present
Journey Continues
I want your company to be a part of this timeline.
{{ dateObj | date:'long' }}
Tata Consultancy Services
Experience Energy
I started my corporate life as a developer at Tata Consultancy Services.
July 19, 2018
Bachelor of Technology
Meerut Institute of Engineering and Technology
Completed my graduation in Computer Science and Engineering with an aggregate of 77.98%
June, 2018
Higher Secondary Certificate
St. Thomas English Medium School
Completed my 12th with an aggregate of 83.6%
March, 2014
Secondary School Certificate
St. Thomas English Medium School
Completed my 10th with an aggregate of 90.7%
March, 2012


MY LIFE A film review by James Berardinelli Copyright 1993 James Berardinelli
Rating (Linear 0 to 10): 6.3
Date Released: 11/12/93 Running Length: 1:57 Rated: PG-13 (Language, mature themes)
Starring: Michael Keaton, Nicole Kidman, Bradley Whitford, Haing S. Ngor, Michael Constantine, Rebecca Schull Director: Bruce Joel Rubin Producers: Jerry Zucker, Bruce Joel Rubin, and Hunt Lowry Screenplay: Bruce Joel Rubin Music: John Barry Released by Columbia Pictures
Bob Jones (Michael Keaton) is dying. His kidney cancer has spread to his lungs and the doctors are telling him that the best he can do is enjoy the few months remaining to him. With his wife Gail (Nicole Kidman) four months pregnant, Bob's chances of living long enough to see the birth of his only child are slim-to-none. In a last-ditch effort to find some shred of hope to cling to, Gail persuades her husband to see a Chinese healer, Mr. Ho (Haing S. Ngor), whose advice--to let go of all the pain and anger within--leads Bob to explore his own past even as he makes video tapes of his last days for his offspring.
The commercials for MY LIFE make a big deal out of this as being "from the creators of GHOST," and for good reason. Much of the same heartwrenching, occasionally cloying, sentiment is present here. Those who hate tear-jerkers should resolutely avoid this film; MY LIFE will leave that crowd retching in the aisles.
Actually, when the film tunes down the manipulation, it has some genuinely moving and emotionally honest moments. Ironically, the most "real" scenes are those of Bob videotaping himself. His confessions, reflections, and comments seem far more genuine than any of the numerous melodramatic scenes that have Bob actively confronting the realities of life and death. MY LIFE lays it on thick in the drawn-out final fifteen minutes, and this hamstrings the project somewhat (you could hear a lot of nose-blowing in the darkened confines of the theater). Not that this is a surprise; fifteen minutes into the movie, it's pretty obvious how it's going to end.
Overall, the scenes that work outnumber those that fail, and that's reason enough for a die-hard cynic like myself to admit grudgingly to having liked MY LIFE. There's enough intelligent stuff contained herein to keep most viewers from dwelling on the maudlin shortcomings. This is no UNTAMED HEART, with an impossible-to-accept premise and cringingly bad overacting; MY LIFE may have obvious intentions, but at least it's skillful in presenting them.
Michael Keaton does a fine job as Bob Jones, and it may be the quality of his performance that makes much of MY LIFE work.  It's all I have left!") aren't too painful to sit through. Nicole Kidman's success is more sporadic. Coupled with finely-acted moments when it's possible to feel Gail's grief, there are times when Ms. Kidman doesn't bring enough substance to her character. This may be as much (or more) the fault of the writing as that of the actress, though, since it's hard to be consistently sincere uttering the occasional dumb line.
Haing S. Ngor is so good that the scenes featuring Chinese mysticism seem less foolish than they might otherwise. This is important, since much of MY LIFE's skeleton is formed from these sessions and what comes out of them.
It's difficult to predict how tear-jerkers will perform at the box office since this, more than any other class of motion picture, brings out the public's fickle nature. MY LIFE isn't a Russian tragedy, so there's exhilaration amidst the heartbreak, and the gallows humor manages to avoid being tasteless. Those who go to this film expecting to like it probably will, and those who don't, won't. Few will be apathetic, however.
 In addition to being far too blatant about its motives and having a plot that offers almost no surprises, the movie suffers from an unfortunate case of "cuteness". Stone-hearted movie-goers beware--many of you will loathe this film, and those that don't will probably have a hard time justifying how you could actually like it.
- James Berardinelli<EMAIL_ADDRESS>.
The review above was posted to the
rec.arts.movies.reviews newsgroup (de.rec.film.kritiken for German reviews).
The Internet Movie Database accepts no responsibility for the contents of the
review and has no editorial control. Unless stated otherwise, the copyright
belongs to the author.
Please direct comments/criticisms of the review to relevant newsgroups.
Broken URLs inthe reviews are the responsibility of the author.
The formatting of the review is likely to differ from the original due
to ASCII to HTML conversion.
Related links: index of all rec.arts.movies.reviews reviews


General
Select the default brush size:
Brush Size: 5
Brush Size: 10
Brush Size: 15
Brush Size: 20
Brush Size: 30
Brush Size: 50
Select the default brush color:
Color
Select the default background color:
Color


Components
- Overview
- Prerequisites
- User Pool
- User Schedd
- GSI
- HTCondor
Prerequisite Component Installation
Prerequisite components
The following is needed by GlideinWMS. The installer will install HTCondor but all others should be installed before you begin. The javascriptRRD directory will also need to be provided to the installer.
| Software | Version | WMS collector | Factory | User collector | Submit | Glidein Frontend | Comments |
| GlideinWMS | v3.0+ | y | y | y | y | y | |
| Linux OS | y | y | y | y | y | A reasonably recent HTCondor-supported Linux OS (RH/SL5 tested at press time). | |
| HTCondor | v7.8+/ v8.2.3+(BOSCO or Ganglia) |
y | y | y | y | The installer will use the tarball or rpm to install and
configure HTCondor inline. It is recommended to use v8
and above. Batch Submission via BOSCO: If you want to add batch resources (via BOSCO) you need HTCondor v8.2.2+. This version requirement is for the WMS Pool, submitting glideins and the HTCondor client, used to setup the BOSCO resource (bosco_cluster_add). Other components can use previous recommended versions of HTCondor. HTCondor monitoring via Ganglia. GlideinWMS provides configuration files for it. |
|
| OSG client | current version | y | y | y | y | Needed to generate GRID/VOMS proxies. See below for instructions. | |
| Python | v2.4.3+ | y | y | y | y | y | |
| HTTP server | y | y | Apache, TUX or whatever server of choice. This port will need open access to the internet, so worker nodes can download data from this service. See below for instructions. | ||||
| RRDTool | V1.2.18+ | y | y | The perl-Time-HiRes rpm is needed for this package. Please verify all dependencies: rrdtool, perl-rrdtool and python-rrdtool. These packages are available via yum using EPEL in EL6/7 or can be searched in RPMFind. | |||
| M2Crypto | v0.17+ | y | y | This can be installed using yum, if available. Or via tarball. | |||
| javascriptRRD (with flot) | v0.6.3+ | y | y | Note: JavascriptRRD and flot, are available from different sources however they may not always work when installed separately for GlideinWMS. We only support JavascriptRRD with Flot available from the sourceforge link provided. |
1. HTTP server
You will need to install an HTTP server for GlideinWMS to be used for staging and monitoring. This needs to be installed on a port accessible to the outside. The server should be installed on the same node, but a different node can be used as long as the web area is writable from this one. In particular, the staging directory will need to be accessible to glideins so they can download appropriate software.
The choice of web server is independent of GlideinWMS, but this documentation will only show the example of Apache Web Server. For most systems, this can be installed via yum:
yum install httpd
Other options are available from Apache here.
There are several recommended tasks you may want to also do post-installation to secure and prepare your web server.
- Disable all unneeded modules. Glideinwms does not any non-standard modules and many can be disabled. A list of example modules to keep enabled is below: 'access_module','include_module','log_config_module', 'mime_magic_module','expires_module','deflate_module', 'headers_module','setenvif_module','mime_module', 'status_module','autoindex_module','negotiation_module', 'dir_module','imap_module','alias_module','rewrite_module', 'cache_module','file_cache_module','mem_cache_module', 'authz_host_module','authz_default_module'.
- Disable any (unneeded) extensions in /etc/httpd/conf.d
- Recommended: disable indexes (Options -Indexes) in all directories/locations, such as frontend/factory stage/monitor directories.
2. OSG Client
The OSG Worker Node Client (formerly known as VDT Client and OSG Client) is now available as a set of RPMs. OSG provides a complete set of instructions that that we recommend. Here you can follow the instructions to install OSG Client on RHEL 6 and 7 based systems (including CentOS and SL). First you will need to enable the EPEL and OSG repositories. It is also advisable to enable the yum priorities module in order to guarantee the correct packages. For more detail, you have everything explained step by step here.
3. RRDTool
You will also need the python module for RRDTool (currently v1.7.0). Many systems come with packages for it; if possible use that.
You can install it via yum. It is available in the Scientific Linux Repository (slf-primary):
yum install rrdtool rrdtool-python
If installing as root is not an option, you can build from the sources, as the glidein factory
user, and put the python libraries into the PYTHON_PATH.
The source code can be downloaded from here.
Beware: The build process has several dependencies that make it complicated. Use this option only if you cannot install from RPMs
(or similar).
4. M2Crypto
You will need the M2Crypto python library. However, if you have the OSG repositories enabled, you can install it via yum:
yum install m2crypto
If your system does not come with m2crypto package, or you do not can/want install it as root, compile it from source as
the glidein factory user.
The source code can be downloaded from
here.
The build process is very easy:
python setup.py build
python setup.py install --root <base dir>
Finally, add M2Crypto site-packages into the PYTHONPATH, possibly in the .profile, .bashrc and/or in the .cshrc.
The exact path is system specific. On a 32bit system with python 2.3.x it will look like this:
export PYTHONPATH=$PYTHONPATH:<base dir>/usr/lib/python2.3/site-packages/
5. javascriptRRD
You will need the javascriptRRD package. It contains the javascript libraries needed by the monitoring. If you enabled the OSG repositories (above), you can install it via yum:
yum install javascriptrrd
Otherwise, download the tarball (with flot), and untar it. You will need to point the installer to this directory. The installer will copy the library files to the Web directories during the installation or reconfig steps.


---
layout: page
title: Morocco'08
date: 2008-02-27 11:45:28.000000000 -06:00
type: page
parent_id: '19'
published: true
password: ''
status: publish
categories: []
tags: []
meta:
_wp_page_template: default
_edit_last: '1412221'
author:
login: dreamessenceonthemove
email<EMAIL_ADDRESS>display_name: darribas
first_name: Daniel
last_name: Arribas-Bel
permalink: "/what/morocco-easter08/"
---
My very good friend from Sweden (she's actually spanish but I got to know her in Sweden) Clara is living in Rabat (Morocco) since last October till summer. She´s working for the Embassy in some projects on gender stuff. I felt I couldn´t waste this opportunity to explore the country and pay a visit to her, so we arranged a visit with Chemi (another friend from Sweden) and a couple of guys more for next Easter. As usual, I´ll fly by myself and we´ll all meet there (flight ticket prices made me take the decission... as usual, I was late buying them) and I´ll be in the country from March 14th. to 25th.
In order to keep track of the arrangements and the trip itself (not really once we are there, since the internet availability is expected not to exist), I´ve set up yet one more blog. One may visit
here, but it´s intended to be only for the arrangements, not for pictures and so on, so it might not be that interesting. Pictures and follows-up from the trip will show up here in this blog rather than there...


About Me
Freelance digital artist & graphic designer.
BIO
Hi I’m Samantha Mueller! Although I’ve been drawing since before I can remember, it’s only now that I have the courage to chase my dream of becoming a professional artist. I currently live in Florida with my fiance and 2 cats. I’m available to work on any digital art (animated or otherwise) or graphic design projects that I can fully immerse myself in!
Adobe Photoshop & Illustrator
I’ve been using Photoshop since the release of CS6 in 2012 and am experienced up to CC 2018. Just recently I have started learning Illustrator but am picking it up quickly. For quick illustrations I have been using Procreate on the iPad Pro which has allowed me to easily practice every day. It also allows me to quickly import sketches to Photoshop for finishing touches and/or animation.
Email Marketing
Over the course of the year I’ve had a crash course in the mechanics and metrics of sending eblasts via Mailchimp to over 250,000 subscribers twice a week. Working on a deadline, planning sales, and communicating with our graphic designer were among my duties.
Miscellaneous Skills
- HTML/CSS familiarity
- Excellent communication
- Ability to work in a team/collaborate or individually
- Ability to take criticism & problem solve
- Excellent time management and organization
- Ability to work on a deadline


Lorem ipsum dolor sit amet, consectetur adipisicing elit. A architecto blanditiis cumque doloribus, eius enim est exercitationem harum itaque iure iusto mani nam nobis? Alias aspernatur deleniti deserunt ea veniam!
HTML(Hypertext Markup Language) is the set of markup symbols or codes inserted in a file intended for display on a World Wide Web browser page. The markup tells the Web browser hot to display a Web page's words and
images for the user. Each individual markup code is referred to as an element(but many people also refer to it as a tag). Some elements come in pairs that indicate when some display effect is to begin and when it is to end.
CSS is a stylesheet language that descibes the presentation of an HTML(or XML) document. CSS descibes how elements must be rendered on screen, on paper, or in other media.


more_vertVictoria Dusini
Actually, I had a call today.
appsIra Glass
This is 311 operator Victoria Dusini.
appsIra Glass
The woman said that her fiance died in their bed, and she was pregnant, and she wanted to identify his DNA in order to get social security benefits. So she wanted to know who to contact.
drag_indicatorAngelique Pantoja
Well, a woman was cleaning her garage and she moved a box, and there was a crocodile. So I had to ask her, like a crocodile, like, big, with-- she's like, yeah, it's going snap, snap at me.


Mo Farah targeting return to track at Tokyo 2020
LONDON – Mo Farah announced Friday that he was targeting a return to the track to compete in the 10,000 meters at next year’s Tokyo Olympics.
The Briton has won double gold at each of the last two Olympics, taking the 5,000 and 10,000 crowns in London and Rio, but switched to the marathon in 2017.
Farah, 36, won the Chicago Marathon in 2018 but has decided to return to the track, admitting the marathon had been “a learning curve.”
“The big news is I’m back on the track in the 10,000 meter in Tokyo next year,” he said on his YouTube channel.
“I hope I haven’t lost my speed but I’ll train hard for it and see what I can do.”
Farah slashed 37 seconds off the European record with a time of 2 hours, 5 minutes, and 11 seconds when he won in Chicago. But with Kenya’s Eliud Kipchoge ruling the marathon world, the Briton was never as dominant at the longer distance as he had been on the track.
“To win the Chicago Marathon was nice, to finish third in London was OK, it was good. It’s been a learning curve for me,” he continued.
“(But) next year I’ve decided, Tokyo 2020, I’m gonna be back on the track. I’m really excited to be competing back on the track and give it a go in the 10,000.”
Farah has come under intense scrutiny for his cooperation with American coach Alberto Salazar, who has been banned for four years by U.S. anti-doping authorities.
Farah broke off cooperation with Salazar in 2017.
UK Athletics on Thursday announced a review into its dealings with the coach and his Nike Oregon Project.
The federation’s performance director Neil Black, who once described Salazar as a genius, left his role in October.
Before running in this year’s Chicago Marathon, Farah responded angrily to media questions about his time with Salazar, saying “I was never given anything.”
GET THE BEST OF THE JAPAN TIMES IN FIVE EASY PIECES WITH TAKE 5
JOIN THE CONVERSATION


--- layout: cohort title: Cohort 1 | Curriculum cohortlink: one cohort: ONE ---
Being in the Social Justice Pathway as an individual you start to see growth in yourself that you didn’t see before. Our teachers Mr. Bloom and Ms. Angell have put together this unique curriculum that has helped us think deeply and differently about our definition of justice.


Hasina returns after attending Dubai Airshow during UAE visit
by bdnews24.comPrime Minister Sheikh Hasina has returned home capping a four-day official visit to the United Arab Emirates.
Hasina attended the Dubai Airshow 2019 and witnessed the signing of bilateral deals. She is visiting the UAE at the invitation of the ruler of Dubai Sheikh Mohammed Bin Rashid al Maktoum.
An Emirates airline flight carrying the prime minister and her entourage took off from Dubai International Airport on Tuesday afternoon local time.
The flight arrived in Dhaka’s Shahjalal International Airport around 11pm Bangladesh time.
On Nov 17, Hasina joined the opening ceremony of the 16th biennial ‘Dubai Air Show,’ one of the largest and most successful air shows in the world and the biggest aerospace event in the Middle East, Asia and Africa.
She later witnessed the aerobatic air display at Dubai World Central, Dubai’s “airport of the future”, also known as Dubai Al Maktoum International Airport.
The prime minister joined a dinner hosted by the Bangladesh Embassy at Shangri-la hotel in Abu Dhabi on Sunday night.
Speaking at the event, she urged the UAE businessmen to invest more in Bangladesh.
On Nov 17, Hasina joined the opening ceremony of the 16th biennial ‘Dubai Air Show,’ one of the largest and most successful air shows in the world and the biggest aerospace event in the Middle East, Asia and Africa.
She later witnessed the aerobatic air display at Dubai World Central, Dubai’s “airport of the future”, also known as Dubai Al Maktoum International Airport.
The prime minister joined a dinner hosted by the Bangladesh Embassy at Shangri-la hotel in Abu Dhabi on Sunday night.
Speaking at the event, she urged the UAE businessmen to invest more in Bangladesh.


This site is best experienced on a scalable browser window
'Responsive Icons' is a project that explores scalable iconography. The concept interrogates the varying complexity of symbols used on devices, and aims to find the perfect balance of simplicity in relation to screen size. The project is currently in its early stages and I will be adding additional icons to the site shortly. Best viewed on desktop (scale your browser width to see the adaptions).
Created by Joe Harrison