$log
ng
Simple service for logging. Default implementation safely writes the message into the browser's console (if present).
The main purpose of this service is to simplify debugging and troubleshooting.
The default is to log debug
messages. You can use
ng.$logProvider#debugEnabled
to change this.
Write a debug message
Write an error message
Write an information message
Write a log message
Write a warning message


The Bio-Bridge Initiative is an overarching programme focused on catalyzing and facilitating technical and scientific cooperation among Parties to the Convention on Biological Diversity and to its Protocols on biosafety (Cartagena Protocol) and on access and benefit-sharing (Nagoya Protocol). The Bio-Bridge Initiative facilitates technical and scientific cooperation among Parties by:


On this slide…
And it even works for paragraphs. :-)
Click again on this slide…
…and it even works for paragraphs. :-)
Timesheet powwa!


Welcome to PaaS-TA Market place
Thanks to our partnership with PaaS-TA, we have the ability to gain new revenues, and our customers will gain
access to all the new technologies and benefits those technologies bring. They are exceptionally forward thinking.
they've built their business around the cloud.
~
총 건수
| No. | 카테고리 | 상품 명 | 버전 | 등록일 | 전시여부 | 승인여부 | 승인일 |
|---|


So, I went back and read the instructions myself to see what I'd done wrong. They said:
Remove the tray from the box. Pierce the overwrap several times with a fork and cook on High for 15 minutes, rotating it half way through.
I thought he'd told me fifty. No wonder it exploded in my microwave.


Trading Interface
Delivery of the Underlying
Risk Management
Margin Trading
xStation
Speculation only
A/B/C book
Leverage up to 1:5
Buroka.Exchange wallet
Physical delivery to wallets
A book only
No leverage
"Bitcoin may be the TCP/IP of money."
“[Virtual Currencies] may hold long-term promise, particularly if the innovations promote a faster, more secure and more efficient payment system.”
"Bitcoin is a remarkable cryptographic achievement and the ability to create something that is not duplicable in the digital world has enormous value"
“The Federal Reserve simply does not have authority to supervise or regulate bitcoin in any way”
“Bitcoin, and the ideas behind it, will be a disrupter to the traditional notions of currency In the end, currency will be better for it.”
“Stay away from it. It’s a mirage, basically”
Opinions and visions about Bitcoin can differ. Yet, there is clearly no doubt that
bitcoin is bound to change the nature of money as we know it.
Thus, this may be just the right moment of uncertainty to step in.
To schedule your free consultation, fill out the form below.


According to the 2010 Census, there's been a migration of more than 120,000 Nicaraguans in Miami-Dade County. Due to the Sandinista takeover in 1979, a lot of Nicaraguans uprooted and migrated to Miami. Though the initial move was not easy, Nicaraguans preserves and remain one of the largest immigrant groups.
In Miami, Nicaraguan slang has been proven impactful on the Spanish language. Here are some unique phrases coined by Nicaraguans.
Sweetwater is often referred to as Little Nicaragua. Due to the affordable rent, early immigrants were able to adjust to American life. This area has become the mecca for Nicaraguan businesses, residents, and visitors alike.
From rice and beans to elaborately wrapped meals, Nicaraguan food is certainly a Miami staple. Below is an introduction to some traditional Nicaraguan meals.


Table with three columns aligned left, center, right:
| a | b | c |
|---|---|---|
| 1 | 2 | 3 |
| 111 | 222 | 333 |
Table with leading empty column in header row:
| x | y | |
|---|---|---|
| 1 | 0.1 | 0.2 |
| 2 | 0.2 | 0.3 |
Table with empty header row:
| 1 | 2 | 3 |
Table with empty header row and leading empty column:
| 2 | 3 |
Single column table with leading pipes:
| 1 |
|---|
| a |
Single column table with pipes alternatingly left and right:
| 1 |
|---|
| a |
This table is completely empty:
This is a valid table with only a header row:
| a | b | c |
|---|
Table with only header row and no separator:
| a | b | c |
|---|
Table with multiple rows but no header separator:
| a | b | c |
|---|---|---|
| 1 | 2 | 3 |
| 4 | 5 | 6 |
Table with | escaped in cells:
| a | a | b | b | c | |
|---|---|---|
| |1 | 2 | 3 | 3 |
Table empty with only one pipe:
Table with three columns aligned left, center, right randomly indented:
| a | b | c |
|---|---|---|
| 1 | 2 | 3 |
| 111 | 222 | 333 |
Single column table with leading pipes randomly indented:
| 1 |
|---|
| a |
Single column table with pipes alternatingly left and right randomly indented:
| 1 |
|---|
| a |
This table is completely empty and randomly indented:
Table empty with only one pipe randomly indented:


{% macro fileupload(name, text='Drag and drop a file here or click') %}
Copy this URL to your clipboard and use as you wish:
Remember, it gets triggered whenever someone requests the URL.
If the URL is requested as an image (e.g. <img src="">) then a 1x1 image is served. If the URL is surfed in a browser than a blank page is served with fingerprinting Javascript.
Ideas for use:
Copy this hostname to your clipboard and use as you wish:
Remember, it gets triggered whenever someone performs a DNS lookup of the hostname.
The source IP address shown in the alert is the
Ideas for use:
tail -f /var/log/auth.log | awk '/Accepted publickey for/ { system("host k5198sfh3cw64rhdpm29oo4ga.canarytokens.com") }'
Here is a unique email address:
Remember, it gets triggered whenever someone sends an email to the address.
Ideas for use:
You'll get an alert whenever this document is opened in Microsoft Office, on Windows or Mac OS.
You can rename the document without affecting its operation.
Ideas for use:
You'll get an alert whenever this document is opened with Acrobat Reader, regardless of the user's security preferences in Reader.
You can rename the document without affecting its operation.
Ideas for use:
Unzip this file in a folder, and get notified when someone browses the folder in Windows Explorer. It will even trigger if someone is browsing the folder via a network share!
The alert will include the network domain and username of the browsing user, if present.
Ideas for use:
Remember, this token is triggered whenever the binary file is executed. For EXEs, this means direct execution and for DLLs, it means they were loaded.
Ideas for use:
Use this Javascript to detect when someone has cloned a webpage. Place this Javascript on the page you wish to protect:
When someone clones your site, they'll include the Javascript. When the Javascript is run it checks whether the domain is expected. If not, it fires the token and you get an alert.
Ideas for use:
The next step is to copy the SQL snippet below and run in your SQL Server database.
When the actions are run, your Canarytoken will be triggered.
Since DNS is used as the underlying transport, the Source IP will be that of a DNS server, not the databserver.
Ideas for use:
Use this QR Code to token a physical location or object:
When someone scans the QR Code with a reader, it will trigger the URL tied to your token and fire an alert.
Ideas for use:
Run this SVN command in a dummy repo:
Remember, it gets triggered whenever someone clones the SVN repo.
Don't forget to run
svn commitafter you've added the token.
The source IP address shown in the alert is the
Ideas for use:


Getting started¶
STEP 0: Python¶
An installation of Python (version 3.6) is required to run PCGR. Check
that Python is installed by typing python --version
in your terminal
window. In addition, a Python library
for parsing configuration files encoded with
TOML is needed. To install,
simply run the following command:
pip install toml
STEP 1: Installation of Docker¶
- Install the Docker
engine on your
preferred platform
- installing Docker on Linux
- installing Docker on Mac OS
- NOTE: We have not yet been able to perform enough testing on the Windows platform, and we have received feedback that particular versions of Docker/Windows do not work with PCGR (an example being mounting of data volumes)
- Test that Docker is running, e.g. by typing
docker ps
ordocker images
in the terminal window - Adjust the computing resources dedicated to the Docker, i.e.:
- Memory: minimum 5GB
- CPUs: minimum 4
- How to - Mac OS X
- NOTE: For query VCF’s that are very large (size to be determined) one may need to adjust these settings
STEP 2: Download PCGR and data bundle¶
Development version¶
- Clone the PCGR GitHub repository:
git clone https://github.com/sigven/pcgr.git
- Download and unpack the latest data bundles in the PCGR directory
- grch37 data bundle - 20191116 (approx 16Gb)
- grch38 data bundle - 20191116 (approx 17Gb)
- Unpacking:
gzip -dc pcgr.databundle.grch37.YYYYMMDD.tgz | tar xvf -
- Pull the PCGR Docker image
(dev) from DockerHub
(approx 5.2Gb):
docker pull sigven/pcgr:dev
(PCGR annotation engine)
Latest release¶
- Download and unpack the latest software release (0.8.4)
- Download and unpack the assembly-specific data bundle in the PCGR directory
grch37 data bundle - 20191116 (approx 16Gb)
grch38 data bundle - 20191116 (approx 17Gb)
- Unpacking:
gzip -dc pcgr.databundle.grch37.YYYYMMDD.tgz | tar xvf -
A data/ folder within the pcgr-X.X software folder should now have been produced
- Unpacking:
- Pull the PCGR Docker image
(0.8.4) from DockerHub
(approx 5.2Gb):
docker pull sigven/pcgr:0.8.4
(PCGR annotation engine)
STEP 3: Input preprocessing¶
The PCGR workflow accepts two types of input files:
- An unannotated, single-sample VCF file (>= v4.2) with called somatic variants (SNVs/InDels)
- A copy number segment file
PCGR can be run with either or both of the two input files present.
- We strongly recommend that the input VCF is compressed and indexed using bgzip and tabix
- If the input VCF contains multi-allelic sites, these will be subject to decomposition
- Variants used for reporting should be designated as ‘PASS’ in the VCF FILTER column
The tab-separated values file with copy number aberrations MUST contain the following four columns:
- Chromosome
- Start
- End
- Segment_Mean
Here, Chromosome, Start, and End denote the chromosomal segment, and Segment_Mean denotes the log(2) ratio for a particular segment, which is a common output of somatic copy number alteration callers. Note that coordinates must be one-based (i.e. chromosomes start at 1, not 0). Below shows the initial part of a copy number segment file that is formatted correctly according to PCGR’s requirements:
Chromosome Start End Segment_Mean
1 3218329 3550598 0.0024
1 3552451 4593614 0.1995
1 4593663 6433129 -1.0277
STEP 4: Configure PCGR¶
The PCGR software bundle comes with a default configuration file in the conf/ folder, to be used as a starting point for runnning the PCGR workflow. The configuration file, formatted using TOML, enables the user to configure a number of options related to the following:
- Sequencing depth/allelic support (definition of tags + thresholds)
- MSI prediction
- Mutational signatures analysis
- Mutational burden analysis
- VCF to MAF conversion
- Tumor-only analysis options (i.e. exclusion of germline variants/enrichment for somatic calls)
- VEP/vcfanno options
- Log-ratio thresholds for gains/losses in CNA analysis
More details about the exact usage of the configuration options.
STEP 5: Run example¶
A tumor sample report is generated by calling the Python script pcgr.py, which takes the following arguments and options:
usage: pcgr.py -h [options] <PCGR_DIR> <OUTPUT_DIR> <GENOME_ASSEMBLY> <CONFIG_FILE> <SAMPLE_ID>
Personal Cancer Genome Reporter (PCGR) workflow for clinical interpretation of somatic nucleotide variants and copy number aberration segments
positional arguments:
pcgr_dir PCGR base directory with accompanying data directory, e.g. ~/pcgr-0.8.4
output_dir Output directory
{grch37,grch38} Genome assembly build: grch37 or grch38
configuration_file PCGR configuration file (TOML format)
sample_id Tumor sample/cancer genome identifier - prefix for output files
optional arguments:
-h, --help show this help message and exit
--input_vcf INPUT_VCF
VCF input file with somatic query variants (SNVs/InDels).
--input_cna INPUT_CNA
Somatic copy number alteration segments (tab-separated values)
--input_cna_plot INPUT_CNA_PLOT
Somatic copy number alteration plot
--pon_vcf PON_VCF VCF file with germline calls from Panel of Normals (PON) - i.e. blacklisted variants, (default: None)
--tumor_type TTYPE Optional integer code to specify tumor type of query,
choose any of the following identifiers:
1 = Adrenal_Gland_Cancer_NOS
2 = Ampullary_Carcinoma_NOS
3 = Biliary_Tract_Cancer_NOS
4 = Bladder_Urinary_Tract_Cancer_NOS
5 = Bone_Cancer_NOS
6 = Breast_Cancer_NOS
7 = CNS_Brain_Cancer_NOS
8 = Cancer_Unknown_Primary_NOS
9 = Cervical_Cancer_NOS
10 = Colorectal_Cancer_NOS
11 = Esophageal_Cancer_NOS
12 = Head_And_Neck_Cancer_NOS
13 = Kidney_Cancer_NOS
14 = Leukemia_NOS
15 = Liver_Cancer_NOS
16 = Lung_Cancer_NOS
17 = Lymphoma_Hodgkin_NOS
18 = Lymphoma_Non_Hodgkin_NOS
19 = Multiple_Myeloma
20 = Ocular_Cancer_NOS
21 = Ovarian_Fallopian_Tube_Cancer_NOS
22 = Pancreatic_Cancer_NOS
23 = Penile_Cancer_NOS
24 = Peripheral_Nervous_System_Cancer_NOS
25 = Peritoneal_Cancer_NOS
26 = Pleural_Cancer_NOS
27 = Prostate_Cancer_NOS
28 = Skin_Cancer_NOS
29 = Soft_Tissue_Cancer_Sarcoma_NOS
30 = Stomach_Cancer_NOS
31 = Testicular_Cancer_NOS
32 = Thymic_Cancer_NOS
33 = Thyroid_Cancer_NOS
34 = Uterine_Cancer_NOS
35 = Vulvar_Vaginal_Cancer_NOS
(default: 0 - any tumor type)
--tumor_purity TUMOR_PURITY
Estimated tumor purity (between 0 and 1, (default: None)
--tumor_ploidy TUMOR_PLOIDY
Estimated tumor ploidy (default: None)
--target_size_mb TARGET_SIZE_MB
For mutational burden analysis - approximate protein-coding target size of sequencing assay (default: 34 Mb (WES))
--tumor_only Input VCF comes from tumor-only sequencing, calls will be filtered for variants of germline origin (set configurations for filtering in .toml file), (default: False)
--force_overwrite By default, the script will fail with an error if any output file already exists. You can force the overwrite of existing result files by using this flag
--version show program's version number and exit
--basic Run functional variant annotation on VCF through VEP/vcfanno, omit other analyses (i.e. CNA, MSI, report generation etc. (STEP 4)
--no_vcf_validate Skip validation of input VCF with Ensembl's vcf-validator
--docker-uid DOCKER_USER_ID
Docker user ID. Default is the host system user ID. If you are experiencing permission errors, try setting this up to root (`--docker-uid root`)
--no-docker Run the PCGR workflow in a non-Docker mode (see install_no_docker/ folder for instructions)
--debug Print full docker commands to log
The examples folder contain input files from two tumor samples sequenced within TCGA (GRCh37 only). It also contains PCGR configuration files customized for these samples. A report for a colorectal tumor case can be generated by running the following command in your terminal window:
python pcgr.py --input_vcf ~/pcgr-0.8.4/examples/tumor_sample.COAD.vcf.gz --tumor_type 10
--input_cna ~/pcgr-0.8.4/examples/tumor_sample.COAD.cna.tsv --tumor_purity 0.9 --tumor_ploidy 2.0
~/pcgr-0.8.4 ~/pcgr-0.8.4/examples grch37 ~/pcgr-0.8.4/examples/examples_COAD.toml tumor_sample.COAD
This command will run the Docker-based PCGR workflow and produce the following output files in the examples folder:
- tumor_sample.COAD.pcgr_acmg.grch37.html - An interactive HTML report for clinical interpretation
- tumor_sample.COAD.pcgr_acmg.grch37.pass.vcf.gz (.tbi) - Bgzipped VCF file with rich set of annotations for precision oncology
- tumor_sample.COAD.pcgr_acmg.grch37.pass.tsv.gz - Compressed vcf2tsv-converted file with rich set of annotations for precision oncology
- tumor_sample.COAD.pcgr_acmg.grch37.snvs_indels.tiers.tsv - Tab-separated values file with variants organized according to tiers of functional relevance
- tumor_sample.COAD.pcgr_acmg.grch37.json.gz - Compressed JSON dump of HTML report content
- tumor_sample.COAD.pcgr_acmg.grch37.cna_segments.tsv.gz - Compressed tab-separated values file with annotations of gene transcripts that overlap with somatic copy number aberrations


Memory Upgrade For Fanuc Series 0 Models A/AD/B/C/D
Installation Instructions
Copyright © 2010
Memex Automation Inc. 200 – 3425 Harvester Rd.
Burlington, Ontario Canada L7N 3N1
Ph:<PHONE_NUMBER> Fax:<PHONE_NUMBER> www.memex.ca
M100702D
Contents
M100702D Page 2
Table of Contents
Chapter 1 – Introduction ......................................................................... 3
General ............................................................................................ ......... 3
Applicable Master Boards ......................................................................... 3
Applicable Memory Cards ......................................................................... 3 Locating SRAM Module .......................................................................... 4
Chapter 2 - The Basics ............................................................................ 6
Installation Considerations ........................................................................ 6 Backup Critical Parameters ....................................................................... 6 Verify Your Control ................................................................................ .... 6
Chapter 3 - Installation for Fanuc 0 ...................................................... 7
Back Up Your Control ............................................................................... 7 Parameter Setting for Punching ......................................... 7 NC Parameters .................................................................. 8 PC Parameters .................................................................. 9 Part Programs ................................................................... 9 Tool Offsets ....................................................................... 9 Installation Procedures for Fanuc 0 ................................................. 10-11 Restoring Your Fanuc 0 ................................................................... 12-14
Chapter 5 – Appendix ............................................................................ 15 Technical Summary for Fanuc 0 ........................................................... 15 Parameter Worksheet ........................................................................ 16-18
Chapter 2 – The Basics
M100702D Page 3
Introduction General
The following instructions are for the installation of additional SRAM for Fanuc Series 0-A, 0-B, 0-C and 0-D controls. The 0-A control can be upgraded 48K (120 meters), while the 0-B, 0-C, 0-D and the Amada 0- 4PC controls can be upgraded with 128K (320 meters). The SRAM based memory is located in sockets on either the Main CPU board (0-A and 0-B) or on the Memory Card (0-C, 0-D and 0-4PC) as illustrated on pages 4 and 5. The supplied IC’s (integrated circuits) will be used to add to the existing SRAM on these boards. These instructions will assist you in completing the memory upgrade for your Fanuc 0 Series control. Please read through this document completely to familiarize yourself with the installation before actually performing your upgrade.
Applicable Master Boards
0-A & 0-AD 0-B 0-C / 0-4PC / 0-D * A16B-1010-0150 A16B-1010-0280 A20B-1002-0360 A16B-1010-0210 A16B-1010-0281 A20B-1003-0750 A16B-1010-0240 A16B-1010-0285 A20B-2000-0175
A16B-1010-0286 A20B-2000-0179 A20B-2000-0180
A20B-2001-0120 *
Sample “B” Software Versions: 415, 815…
Applicable Memory Cards (0-C and 0-4PC)
Memory Cards A16B-1212-0210 Analog Spindle (MEM-A3) A16B-2201-0103 Analog Spindle
A16B-1212-0215 16 bit, Serial Spindle A16B-1212-0216 32 bit, Serial Spindle A16B-2201-0101 32 bit, Serial Spindle
Sample “C” Software Versions: 460,462,465,469,660,662,690,665,880,135…
Chapter 2 – The Basics
M100702D Page 4
Locating SRAM Modules (0-A / 0-AD / 0-B)
I/O
BA4
CAP
CV21
CF91
CV22
CF92
CA1
CA2
PAS
SO SI WDA
(4H) (3H) (2H) (1H)
(34L) (34H)
Memory Modules
(4L) (3L) (2L) (1L)
A16B-1010-0150 (Analog) A16B-1010-0210 (Digital) A16B-1010-0240 (0-Mate)
Memory Modules
CS8
CPA4
CP11
CCX M3 M2
M49 M48 M47
PAS (1H) (2H) (3H)
(1L) (2L) (3L)
M46 M45 M44
M39 M38 M36
M36 M35 M34
M26 M27 M25 M74
CS7 CS3 CS2 (34H)
(34L)
(12H)
(12L)
Battery connection
A16B-1010-0280 A16B-1010-0281 A16B-1010-0285 A16B-1010-0286
Chapter 2 – The Basics
M100702D Page 5
Locating MEM-A3 Card (0-C / 0-4PC)
Locating SRAM Modules (0-C / 0-D / 0-4PC)
M27
M12 M26
M3 CCX5
M5 M74 CPA7
(2H) (2L) (3H) (3L)
Power Supply
Memory Card
A16B-1212-0210 A16B-1212-0215 A16B-1212-0216 A16B-2201-0101 A16B-2201-0103
Memory Modules
Battery Connection
Chapter 2 – The Basics
M100702D Page 6
The Basics Installation Considerations
The installation of the SRAM modules should be conducted with care. Never install or remove a board with the control power on (the main power can be on, but not the control). Take care with the handling of the integrated circuits, as they are static sensitive. Do not place the IC’s in any other sockets than as per pages 4 and 5. Do not force, drop or otherwise mishandle the modules during the installation procedure and always check the functionality of the machine at the end of the installation (i.e. move the axes, perform a tool change, run a program, etc.).
Backup Critical Parameters For a Fanuc Series 0 upgrades it is very important that you have a hard copy back-up of all your control’s critical parameters. The following instructions will assist you in dumping a majority of the Fanuc’s parameters to a PC to be saved. However, it is still advised to keep or make, if you haven’t already, a written copy of ALL the critical parameters. You can use the Parameter Sheets in the Appendix of this manual to write down all Settings, PC and Diagnostics parameters. All of the Diagnostic parameters between D300 and D600 must be written down here. If you have a Fanuc 0C, you can serially download the PMC Diagnostic parameters. Be sure that all of the files you downloaded have been successfully recorded and saved on your computer before performing the upgrade to your control.
Verify Your Control
Once the memory modules have been installed and all parameters have been restored, satisfy yourself that the control is working properly. Test the machine by the following procedure through either MDI or program:
Home all axes, tool-changers and pallets – check for need to reset Absolute Pulse Coders here.
Check spindle functionality through all speeds and gear ranges.
Check also Clockwise and Counter-clockwise rotation with M3 and M4 commands.
Check the tool changer. Be sure that the tool you received was the tool requested and that the carousel rotates in the proper direction.
Check the pallet changer (if applicable). If your machine requires special custom macros for a pallet changer or tool changer, be sure that they have been loaded.
Once your machine has been proven, you have successfully upgraded your control.
Chapter 3 – Installation for Fanuc 0
M100702D Page 7
Installation for Fanuc 0 Backup Your Control
Before starting the installation, power on the control and verify that the machine tool is in good working order.
I. Parameter Settings for Punching Set up the following communication parameters for the desired CNC port. Please make note of the original settings for proper restoration of the new memory (see page 16).
On the SETTINGS (HANDY) screen, set the following: TVON = 0 (TV Check off) ISO = 1 (ISO data format) I/O = 0 (port number) PWE = 0 (Parameter Write Enable OFF) TAPE = 0 Write down the previous settings so that they can be restored upon completing the upgrade. Also set the following parameters:
Chart 1 CNC
Parameter Port 1-M5
I/O=0 Port 1-M5
I/O=1 Port 2-M74
I/O=2 Port 2-M74
I/O=3 Current Settings
0002 1xxxxxx0 -- -- -- 0012 -- 1xxxxxx0 -- -- 0038 10xxxxxx 10xxxxxx xx10xxxx xx10xxxx 0050 -- -- 1xxx0xx0 -- 0051 -- -- -- 1xxx0xx0 0250* -- -- 10 -- 0251* -- -- -- 10 0552* 10 -- -- -- 0553* -- 10 -- --
* Parameters 250, 251, 552 and 553 represent the baud rate during communication and are set here to 4800
baud. Parameter 552 is used if Setting I/O=0, 553 if I/O=1, 250 if I/O=2 and 251 if I/O=3. The protocol is Even parity, 7 data bits and 1 stop bit. For more baud rate choices refer to the following Chart 2.
Chapter 3 – Installation for Fanuc 0
M100702D Page 8
Trace the RS-232 cable from the serial port connector back to the CNC MEMORY PCB to determine if you are connected to Port 1 (M5) or Port 2 (M74). Then, label the serial port connection so it is visible from the outside. Chart 2 for Serial Baud Parameter on 552/553 or 250/251
Parameter Value Baud Rate 1 50 2 100 3 110 4 150 5 200 6 300 7 600 8 1200 9 2400
10 4800 11 9600
II. PUNCHING CNC NC PARAMETERS (CNC - PC) Connect the Fanuc serial cable between the serial ports on your computer and the CNC. Set up your computer with a terminal software program (Telix / ProCom+ / Hyper Terminal). Perform the following steps on the PC and CNC as follows: PC-- Using the Baud Rate set in parameters 552 & 553, Even parity, 7 Data bits and 1 Stop bits,
set your terminal program to receive a file. PC-- Enter a file name to record the NC parameters. ie; #103.NCP (103 being the machine #) CNC-- Go into EDIT mode. CNC-- Make sure the “Memory Protect” key is off. CNC-- Press DGNOS/PARAM, [PARAM], then hold EOB while you press OUTPUT/START.
NB: Hold the EOB key while pressing the OUTPUT/START key to punch ALL the NC Parameters, including the 900 level options.
(The CNC will flash OUTPUT in the lower right corner of the CRT.) (The PC will display the text and count lines until finished.) PC-- Save the file you just received from the CNC on the computer. IMPORTANT: Check the .NCP file with a text editor to visually confirm that system parameters
N0900 series have been sent to the computer. If these parameters are not found in your listing, please repeat this section (Punching CNC Parameters). Take this moment to write down the 900 level system parameters for backup purposes.
Chapter 3 – Installation for Fanuc 0
M100702D Page 9
III. RECORD THE PMC PARAMETERS You must manually copy down on paper ALL of the Diagnostic parameters between No. 300 – 600 (see page 18). These parameters represent the Timers, Counter, Keep Relays & Data Tables used by the machine builder. On the Fanuc 0-C you can punch these PMC parameters. This backup is necessary before continuing this memory upgrade. Be sure that all of the files above have been successfully recorded or saved on your computer. If there is any doubt, please contact Memex Automation before continuing. Some parameters are changing, ignore these – generally it is every 5th one that you need as you can see on the attached chart.
Sample Fanuc 0-C PMC Parameter Dump
Delete the feed info before the first % sign
…
IV. PUNCHING CNC PART PROGRAMS (CNC - PC) Ensure that Macro files in the 9000 range can be downloaded – set NC Parameter 10 bit 4 = 0
(xxx0xxxx) so that ALL programs can be backed up properly. Perform the following steps on the PC and CNC as follows: PC-- Enter a file name to receive the NC parameters. ie; #103.PRG (103 being the machine #) CNC-- In EDIT mode, with the “Memory Protect” key off, press PRGRM, [LIB], O-9999, then OUTPUT/START. PC-- Save the file you just received from the CNC on the computer. V. PUNCHING CNC TOOL OFFSETS (CNC - PC) Perform the following steps on the PC and CNC as follows: PC-- Enter a file name to receive the NC parameters. ie; #103.TOF (103 being the machine #) CNC-- In EDIT mode, with the “Memory Protect” key off, press OFFSET, and then
OUTPUT/START.
Chapter 3 – Installation for Fanuc 0
M100702D Page 10
PC-- Save the file you just received from the CNC on the computer.
Chapter 3 – Installation for Fanuc 0
M100702D Page 11
Installation Procedures for Fanuc 0 Make a print out of your .NCP parameter file. When you are confident that you have completely saved all of your CNC information, you will be ready to proceed with your memory upgrade. The part program and system memory is located on the Master Board for Fanuc 0-A and 0-B Series controls and on the MEM-A3 card for 0-C and 0-4PC Series (see pages 4-5). Locate this board in your machine control cabinet. Check that you have received all of the information out of your CNC control. Check also that
any Custom Macro Variables have been written down and recorded.
1. Power OFF the control and the machine. Open the cabinet door to expose the control’s Master Board.
2. Clearly label all of the cables, daughter boards and their locations that are connected to the Master Board. Once all the cables and boards are labeled, you can loosen and remove the cables and daughter boards using a screwdriver including the MEM-A3 board (for 0-C and 0- 4PC upgrades). You are now ready to potentially remove the battery connection (CPA7) from the bottom of the Master Board (see “Master Trick” note blow).
Master Trick: With great care, it is possible to install the modules and not have the battery removed. If each module is carefully inserted so as not to short the battery to ground, you may find the main memory has been saved. Worst case is that you will have to do the manual restore listed below. Test this by powering up not holding RESET & DELETE in the beginning.
3. Put on an anti-static wrist strap if available and clip the other end of it to the GND post in the top corner of the Master Board. Locate the SRAM socket positions on the Master Board / MEM-A3 board (see pages 4-5). This is where you have to insert or replace the larger of the new memory modules. Optionally if there are already modules in these locations, you can use the small screwdriver or a chip puller to carefully remove them. Also locate the smaller SRAM parity socket positions on the Master Board (0-A and 0-B upgrades only). This is where the smaller of the new memory modules go.
4. One by one, remove the memory module from the kit. Check that the pins are straight and be wary of static discharge that may damage the memory modules.
5. Orient one supplied memory module above the socket with the “notch” in the same direction as the “notch” in the socket (Pointing “Down”). Place one row of pins in the socket, then with a little sideways pressure put the second row in. With steady pressure, push the memory module down into the socket. Check that none of the pins have bent in during this process. Repeat this step for the remaining modules. If components exist in the sockets – leave them.
Chapter 3 – Installation for Fanuc 0
M100702D Page 12
6. Again, check your work before replacing any daughter boards back in the control. After you replace the daughter boards and restore all of the cable connections, check your work. After you are confident that every cable has been correctly connected, power up the control.
7. If the CNC boots normally, then jump to the next step of enabling the option (set
P901=x1x00001 for 320M) and reload your 8000/9000 Macro Programs. You are done. However, if the controls comes up with a parity error, then turn off and on the CNC power while holding the RESET & DELETE keys simultaneously. This will erase the new Master Board memory in preparation for your information.
8. Now you are ready to proceed with the reloading of all of your parameters and programs.
Chapter 4 – Appendix
M100702D Page 13
Restoring your Fanuc 0 I. RESTORING THE SYSTEM PARAMETERS With the Emergency Stop button depressed, set the PWE parameter on page 2 of the SETTINGS screen to a 1. Press DGNOS/PARAM, [PARAM] and page down to parameter 900. Enter the values for parameters 900-1000. At this time, set up the communication parameters again the same way you did in Part 1-CNC Parameter Settings. When you are finished, turn off the power to the control, then power on again. II. READING CNC PARAMETERS (PC - CNC) Set the PWE parameter, then press DGNOS/PARAM, [PARAM] and set up the CNC
communication parameters in accordance with the following. On the SETTINGS (Handy) screen and in MDI mode, set the following:
TVON = 0 (TV Check off) ISO = 1 (ISO data format) I/O = 0 (desired port number placed here) PWE = 1 (Parameter Write Enable OFF) TAPE = 0
For example – if you used Port 0 you would set parameters P901.6 to 1, P552=11 (for 9600 baud), P2=1xxx xxx0 for E71 with no feed and P38=10xx xxxx to get serial communications going again. NB: Check that after using the software that Parameter 901=x1x0 0001 (where x is don’t care) for 320M on Fanuc 0B &C, or P901=x1x0 0010 is set for 120M on the Fanuc 0A. You should have the original settings written on page 16 (as per page 7) to be restored after all other parameters are restored via the serial port. In order to do this set the parameters for the serial ports as per Chart 1 (page 7) and Chart 2 (page 8).
Chapter 4 – Appendix
M100702D Page 14
Set up the communications software on your computer to send a file. Perform the following steps on the PC and CNC as follows: CNC-- In EDIT mode, press the DGNOS/PARAM, [PARAM], INPUT keys. (The CNC will flash LSK in the lower right corner of the CRT.) PC-- Send the file with the .NCP extension to the control. When the parameters have been received, Power OFF the control, then power it ON again. III. WRITING THE PC PARAMETERS You must manually input into the control, ALL of the Diagnostic parameters between No. 300-600. At the end of this entering what you can, cycle the power completely (that is power off even back to the main breaker - this reset the servo drives by the way). IV. READING CNC TOOL OFFSETS Set up the CNC parameters in accordance with section 1. Set up the communications software on your computer to send a file. Perform the following steps on the PC and CNC as follows: CNC-- In EDIT mode, press the OFFSET, then [INPUT] keys. (The CNC will flash LSK in the lower right corner of the CRT.) PC-- Send the file with the .TOF extension to the control. This should reload all of your tool offsets. CNC-- Execute this .TOF file to set the Tool Offsets. CNC-- Delete this file from the Programs in the CNC. V. READING CNC PART PROGRAMS Set up the CNC parameters in accordance with section 1. Set up the communications software on your computer to send a file. Perform the following steps on the PC and CNC as follows: CNC-- In EDIT mode, with the memory protect KEY switched off, Press the EDIT/AUTO, [PRGRM], then INPUT keys.(The CNC will flash LSK or “lead skip” in the lower right corner of the CRT.) PC-- Send the file with the .PGM extension to the control. This should reload all of your programs. Don’t forget to reset parameter 10 if you had previously changed it. That will protect your macro programs (if applicable).
Chapter 4 – Appendix
M100702D Page 15
VI. CLEAR ABSOLUTE ENCODER (if applicable) 1. Power up with “No.QRP” + “CAN” or “P” + “CAN” to clear (or reset) any absolute encoders if
applicable. You will know this is needed if the machine over-travels upon homing, but is a long way from normal home.
2. Reference machine manually as usual. Restore any of the NC parameters that you changed from their original state (see SETTING, communications settings etc. You will have to set PWE to do this. Double check the INCH versus METRIC setting in the SETTING HANDY screen (a metric setting which is the default, will make the machine seem to crawl when a program asks for what it thought was an INCH move). Check the MIRROR AXES settings as well. Also remember to re-protect your 9000 level programs with parameter 10 bit 4 (xxx1 xxxx) if
applicable. After a complete test - including exercising the tool changer if applicable - you will have completed your installation. Remember to change the 3 D cell batteries that keep your control memory backed up on a regular basis (once a year) with the CNC control power ON. Call Memex if you would like to investigate our permanent Fanuc MxBRU Battery Replacement Unit (see below). Fanuc Serial Cable: Pin 1 Frame Ground Pin 4 Request to Send Pin 7 Signal Ground Pin 2 Transmit Data Pin 5 Clear to Send Pin 8 Carrier Detect Pin 3 Receive Data Pin 6 Data Set Ready Pin 20 Data Terminal Ready Normally pins 6, 8 & 20 are jumpered on the Fanuc side. Also pins 2 & 3 are usually crossed, as are 3 & 4, when connected to a PC with a DB25 connector. Note that Fanuc has +24 volts on pin 25!
Chapter 4 – Appendix
M100702D Page 16
Chapter 4 – Appendix
M100702D Page 17
Appendix Technical Summary for Fanuc 0 PUNCHING Punch NC Parameters - EDIT mode, PARAM screen, EOB + OUTPUT/START Punch PC Parameters - EDIT mode, DGNOS screen, OUTPUT/START Punch All Programs - EDIT mode, PRGRM screen, 0-9999, OUTPUT/START Tool Offsets - EDIT mode, OFFSET screen, OUTPUT/START READING Load NC Parameters - EDIT mode, PARAM screen, EOB + INPUT Load PC Parameters - EDIT mode, DGNOS screen, INPUT Load All Programs - EDIT mode, PRGRM screen, INPUT Load Tool Offsets - EDIT mode, OFSET screen, INPUT CLEARING Delete All memory - Power On holding RESET + DELETE Standard Fanuc Serial Port: (DB-25 Female) 1 = Frame Ground 6 = Data Set Ready 2 = Transmit Data 7 = Signal Ground 3 = Receive Data 8 = Carrier Detect 4 = Ready To Send 20= Error (Data Terminal Ready) 5 = Clear To Send 25= +24 Volts DC The usual software handshaking cable configuration has 2, 3 crossed & 7 connected straight through (with 4&5 jumpered - or used if hardware handshake lines are preferred) and pins 6,8 & 20 jumpered on the control side only. Fanuc ISO Protocol: (E,7,x) The standard protocol for Fanuc controls is “Even parity”, “7 data bits” and either “1 or 2 stop bits”) See Parameters 101, 111, 121 and 131 above
Determination of Fanuc 0 Model Types To determine the version of the Fanuc 0 series CNC Control, check the master board number and/or the software version. The Master board number is found on the top left side of the main circuit board, usually mounted in the control cabinet that has the daughter card attached. It should not be confused with “A02B-????-????” numbers, which are Fanuc’s ordering numbers and are usually found on a sticker above the master board. Use the following table to determine which unit you have. You can determine the software version by powering-up the control with E-stop active (button depressed). The control should hang on the software version screen (in the lower right corner of this screen, you will see the servo version number as well). Please note that Memex has a MxBRU (Battery Replacement Unit) available that provides a maintenance-free rechargeable Lithium battery backup for this control. 1985 / 1986 Fanuc 0-MA and Fanuc 0-TA 120M maximum battery backed resident memory. 1987 / 1989 Fanuc 0-MB and Fanuc 0-TB 320M maximum battery backed resident memory. 1990 / 1998 Fanuc 0- MC and Fanuc 0-TC 320M maximum battery backed resident memory. 1999 / today Fanuc 0- MD and Fanuc 0-TD 320M maximum battery backed resident memory
Chapter 4 – Appendix
M100702D Page 18
Parameter Worksheet Company:_________________________________ Machine No.:___________ Date:_____________ Fanuc 0-___ Software Version: _______________ Main CPU Board No.: _____________________
Setting Screen Data TV ON PWE
ISO TAPE I/O
PC Parameters Par. Value Par. Value Par. Value Par. Value Par. Value
Par. = Parameter Number
Chapter 4 – Appendix
M100702D Page 19
Diagnostics Parameters
Parameter Data Parameter Data D300 D375 D301 D376 D305 D390 D306 D391 D310 D395 D311 D315 COUNTER 1 D316 D380 D320 D381 D321 D382 D325 D326 COUNTER 2 D330 D385 D331 D387 D335 D340
PC SWITCH
D341 D400 D345 D420 D346 D421 D350 D422 D351 D423 D355 D424 D356 D360
DATA TABLE
D361 D440 D365 D441 D366 D370
TOOL CHANGE
D371 D382 D387
Chapter 4 – Appendix
M100702D Page 20
Spare Parameter Sheet
No. Data No. Data No. Data No. Data. 0 0 0 0 1 1 1 1 2 2 2 2 3 3 3 3 4 4 4 4 5 5 5 5 6 6 6 6 7 7 7 7 8 8 8 8 9 9 9 9 0 0 0 0 1 1 1 1 2 2 2 2 3 3 3 3 4 4 4 4 5 5 5 5 6 6 6 6 7 7 7 7 8 8 8 8 9 9 9 9 0 0 0 0 1 1 1 1 2 2 2 2 3 3 3 3 4 4 4 4 5 5 5 5 6 6 6 6 7 7 7 7 8 8 8 8 9 9 9 9 0 0 0 0 1 1 1 1 2 2 2 2 3 3 3 3 4 4 4 4 5 5 5 5 6 6 6 6 7 7 7 7 8 8 8 8 9 9 9 9 0 0 0 0 1 1 1 1 2 2 2 2 3 3 3 3 4 4 4 4 5 5 5 5 6 6 6 6 7 7 7 7 8 8 8 8
Chapter 4 – Appendix
M100702D Page 21
Notes:
Chapter 4 – Appendix
M100702D Page 22
Memex Automation Inc. 200 – 3425 Harvester Rd.
Burlington, Ontario Canada L7N 3N1
Phone:<PHONE_NUMBER> Fax:<PHONE_NUMBER> www.memex.ca
Thank you for using Memex products
Manufacturing Connectivity Solutions™
File: /ISO9000/DOCS/ M100702D - MAI Memory Upgrade for Fanuc 0.doc


Exploring ES2015
Classic Inheritance
Collision Detection
Object: An object is a collection of related data and/or functionality


The Crew 2 update 1.5.0 brings the Blazing Shots
by Aran SuddiUbisoft has released a brand new update for The Crew 2 which adds the Blazing Shots contents pack for free. The Blazing Shots pack adds 17 live summits over five weeks with these being focused around events such as The Mix Master, Ghost Road, H2O, and Street Fight. There are also twelve new vehicles including the Bugatti Veyron 16.4, the Citreon GT, and the Mazda RX8, which will all be rolled out gradually. 78 vanity items have also been added.
Some of the fixes include not being able to break the top speed of drag vehicles, and monster trucks won’t be glitching through the arena stairs. The full list of changes can be seen below.
The Crew 2 Blazing Shots update 1.5.0
VANITY
• [Added] New vanity type: Underglows
• [Added] 78 new vanity items – to be released on a weekly basis through the shop or as LIVE Summit rewards.
o 27 new Tires
o 26 new Smokes
o 25 Underglows
SUMMIT
• [Added] 17 New Live Summits and their associated set of activities & rewards.
o Including regular Themed weeks (e.g. Ghost Road special event)
o Discover the upcoming Live Summits on https://thecrew-hub.com
• [Fixed] Persistent display of player information (level, followers and bucks) after aborting a Live Summit activity.
• [Fixed] Audio track from Live Summit introduction video keeps on playing in background while pause menu is opened.
LIVE CONTRACTS
• [Fixed] Localization issues in Spanish and French.
VEHICLES
NEW VEHICLES
• [Added] 12 Vehicles, including special editions
o Elite Bundle 3
• Citroën GT (Hypercar) – 2008
• Ferrari 599XX EVO (Touring Car) – 2011
• Porsche Carrera GT (Hypercar) – 2003
o Shop additions
• November 13th
o Bugatti Veyron 16.4 Grand Sport Vitesse (Hypercar) – 2016
• December 4th
o Mazda RX-8 (Street Race) – 2010
o Live Summit Rewards
• November 27th – Ghost Road Summit:
o Ford F-150 RAPTOR RACE TRUCK Ghost Recon Edition (Rally Raid) – 2017
o & more to be revealed, stay tuned!
PHYSICS
• [Fixed] Missing AWD on Lamborghini Gallardo LP 570-4 Super Trofeo.
• [Fixed] Dodge SRT Viper GTS can move forward while doing a burn with specific Pro Settings.
• [Fixed] Drag Race vehicles glitch allowing players to surpass vehicle top speed.
• [Fixed] Drag Race vehicles infinite nitro glitch after opening the world map.
• [Fixed] Vehicle moving before engine is started.
• [Fixed] Inconsistent breakable objects behavior.
• [Fixed] Monster Truck vehicles going through arena stairs.
• [Fixed] Missing differential Pro Setting on Mitsubishi Lancer Black Knight (Street Race).
• [Fixed] Missing differential Pro Setting on Lamborghini Huracan Performante (Hypercar).
• [Fixed] Missing differential Pro Setting on Jaguar F-Type Beta Handling (Street Race).
3C/HANDLING
• Aerobatics
o [Improved] Handling on Aerobatic full line-up (mostly rudder).
• Air Race
o [Improved] Balancing on Air Race full line-up:
• Behavior uniformization, while keeping differences of each vehicles
• Improved “Drift” (rudder).
• Monster Truck
o [Improved] Handling of the Monster Trucks full Line-up:
• New tire & suspension system
• Increased stability & trajectory anticipation
• Improved precision and accelerating/braking behavior.
• Street Race / Hypercar
o Beta Handling follow-up: deployment of an updated handling model on 10 existing vehicles.
o Please note: A dedicated survey will be shared in the upcoming weeks to collect your feedback on this topic.
• [Updated] Handling of the Audi RS5 (Street Race)
• [Updated] Handling of the BMW M4 (Street Race)
• [Updated] Handling of the KTM X-BOW (Street Race)
• [Updated] Handling of the Mercedes-Benz SLS (Street Race)
• [Updated] Handling of the Volkswagen Golf GTi (Street Race)
• [Updated] Handling of the Ferrari 458 Speciale (Hypercar)
• [Updated] Handling of the Lamborghini Huracán Performante (Hypercar)
• [Updated] Handling of the Lamborghini Veneno (Hypercar)
• [Updated] Handling of the McLaren 12C (Hypercar)
• [Updated] Handling of the Pagani Zonda F (Hypercar)
• [Improved] Handling of the Bugatti Divo Magma Edition (Hypercar)
• [Improved] Handling of the Ferrari F12 TdF (Hypercar)
• Hovercraft
o [Improved] Overall smoothing of vehicle bouncing behavior during collisions.
AUDIO
• [Improved] Sound engine for BMW X6 M (Street Race)
• [Improved] Sound engine for Dodge Viper (Street Race/Drift/Touring).
• [Improved] Sound effect for Rev Limiter on all Rally Cross vehicles.
• [Fixed] Persistent audio SFX while equipping a full performance parts set.
WORLD
EVENTS
• [Added] 17 new events – to be released along our new Live Summits.
o Please note that these one will remain available in regular progression (PVE) after their release.
• [Fixed] Inconsistent AI behaviors:
o [Rally Raid] “Portfoliage” AI performing back-on-track in loop.
o [Hypercar] “Going to Vegas” AI remains struck at starting grid.
• [Fixed] Collision issues:
o [Rally Raid] “Red Rock” Incorrect collision behavior on ramp
WORLD
• [Fixed] Floating rocks found on the mountaintop near Yosemite.
• [Fixed] Floating house in San Francisco area.
TECHNICAL
DISPLAY
• [Fixed] PC – Gamma slider changes are not taken into account while on windowed or borderless full screen modes.
CONTROLLERS
• [Fixed] PC – Unable to re-bind Accelerate or Brake actions to controllers button A or B.
• [Fixed] Key-binding conflict between quick messaging and horns.
Source: Ubisoft


BOOGIE NIGHTS A film review by Andrew Hicks Copyright 1997 Andrew Hicks / Fatboy Productions
(1997) ***1/2 (out of four)
BOOGIE NIGHTS is a movie that mixes two of my favorite things -- Marky Mark and pornography. I'm being sarcastic, of course.
Like PULP FICTION, this is an intelligent epic of the tasteless, a movie that makes sweeping points about our society and has likeable people doing reprehensible things. Written and directed by Paul Thomas Anderson, BOOGIE NIGHTS forgoes the gynecology and eroticism in painting sex as cold, emotionless and mainly just a commodity, and its success is finding the humor of '70s porn business as well as the sadness.
In that sense, it's like THE PEOPLE VS. LARRY FLINT, alternating between being fascinating and funny in its realistic portrayal of the motivations of pornographers and focusing on the empty lives of those who make their living this way. Its main actors, Mark Wahlberg and Burt Reynolds, are two people I'd never thought I'd praise, but they do great work in BOOGIE NIGHTS, as do the people you'd expect to kick ass, like Julianne Moore, Don Cheadle (from ROSEWOOD) and William H. Macy.
The story begins in 1977, as 17-year-old Wahlberg is washing dishes in a nightclub populated by an adult filmmaker (Burt Reynolds, in perhaps his most disgusting hairpiece yet).  After a pool party, Wahlberg agrees to join the porn star family under the name Dirk Diggler.
It's in these early scenes that we meet the other family members.  Cheadle is a second-string actor hoping to make it big in the world of stereo sales, Macy is one of the crew and can't seem to keep his wife (real-life porno queen Nina Hartley) from humping everything in sight and John C. Reilly is Wahlberg's best friend and a damn good porn actor in his own right.
In about 150 minutes, BOOGIE NIGHTS covers five years in the pornography industry, from the rise and fall of Dirk Diggler to the decline of porn as an art form. That's the funniest thing about this movie, the conviction held by all the characters that they're making something significant. The Reynolds character's main goal is to make a XXX-rated movie that is so good that its customers stay in the theater long after sticky-ing up the floor and Dirk helps him out by making some hilarious action hero porno flicks.
BOOGIE NIGHTS, like LARRY FLINT, humanizes something most people don't think of as very worthy of epic treatment. A lot of its middle scenes, the ones involving Dirk's brief recording career and the imminent arrival of videotape as the medium for porno, are amusing, but the closing scenes pack a punch.  It's frank without being graphic, emotional without being melodramatic and funny without being unbelievable.
--
Visit the Andrew Hicks: Movie Critic at LARGE homepage at http://www.missouri.edu/~c667778/movies.html
Serving America For More Than 1/25th of a Century!
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


This is for information only - it might help some who were not aware of this mega internal reference voltage and how arduino.h implements it or makes it available. The mega 2560 runs EmonLib perfectly.
It is already implemented in EmonLib.cpp due to the call to arduino.h
I have run Emonlib on a Freetronics Ethermega and the program works fine.
From the Arduino Reference ( http://arduino.cc/en/Reference/AnalogReference?from=Reference.AREF )
Configures the reference voltage used for analog input (i.e. the value used as the top of the input range). The options are:
DEFAULT: the default analog reference of 5 volts (on 5V Arduino boards) or 3.3 volts (on 3.3V Arduino boards)
INTERNAL: an built-in reference, equal to 1.1 volts on the ATmega168 or ATmega328 and 2.56 volts on the ATmega8 (not available on the Arduino Mega) INTERNAL1V1: a built-in 1.1V reference (Arduino Mega only)
INTERNAL2V56: a built-in 2.56V reference (Arduino Mega only)
EXTERNAL: the voltage applied to the AREF pin (0 to 5V only) is used as the reference.
In Arduino.h ( \hardware\arduino\cores\arduino\arduino.h ) IDE V1.0.3 ERW , modified IDE
#if defined(__AVR_ATtiny24__) || defined(__AVR_ATtiny44__) || defined(__AVR_ATtiny84__) || defined(__AVR_ATtiny25__) || defined(__AVR_ATtiny45__) || defined(__AVR_ATtiny85__)
#define DEFAULT 0
#define EXTERNAL 1
#define INTERNAL 2
#else
#if defined(__AVR_ATmega1280__) || defined(__AVR_ATmega2560__) || defined(__AVR_ATmega1284P__) || defined(__AVR_ATmega644P__)
#define INTERNAL1V1 2 //this is the mega 1.1Volts internal voltage call
#define INTERNAL2V56 3 //and here is the mega 2.56volts internal reference call
#else
#define INTERNAL 3
#endif
#define DEFAULT 1
#define EXTERNAL 0
#endif
Arduino mega internal voltage reference
Submitted by platypus on Sat, 29/06/2013 - 02:55This is for information only - it might help some who were not aware of this mega internal reference voltage and how arduino.h implements it or makes it available. The mega 2560 runs EmonLib perfectly.
It is already implemented in EmonLib.cpp due to the call to arduino.h
I have run Emonlib on a Freetronics Ethermega and the program works fine.
From the Arduino Reference ( http://arduino.cc/en/Reference/AnalogReference?from=Reference.AREF )
Configures the reference voltage used for analog input (i.e. the value used as the top of the input range). The options are:
DEFAULT: the default analog reference of 5 volts (on 5V Arduino boards) or 3.3 volts (on 3.3V Arduino boards)
INTERNAL: an built-in reference, equal to 1.1 volts on the ATmega168 or ATmega328 and 2.56 volts on the ATmega8 (not available on the Arduino Mega)
INTERNAL1V1: a built-in 1.1V reference (Arduino Mega only)
INTERNAL2V56: a built-in 2.56V reference (Arduino Mega only)
EXTERNAL: the voltage applied to the AREF pin (0 to 5V only) is used as the reference.
In Arduino.h ( \hardware\arduino\cores\arduino\arduino.h ) IDE V1.0.3 ERW , modified IDE
#if defined(__AVR_ATtiny24__) || defined(__AVR_ATtiny44__) || defined(__AVR_ATtiny84__) || defined(__AVR_ATtiny25__) || defined(__AVR_ATtiny45__) || defined(__AVR_ATtiny85__)
#define DEFAULT 0
#define EXTERNAL 1
#define INTERNAL 2
#else
#if defined(__AVR_ATmega1280__) || defined(__AVR_ATmega2560__) || defined(__AVR_ATmega1284P__) || defined(__AVR_ATmega644P__)
#define INTERNAL1V1 2 //this is the mega 1.1Volts internal voltage call
#define INTERNAL2V56 3 //and here is the mega 2.56volts internal reference call
#else
#define INTERNAL 3
#endif
#define DEFAULT 1
#define EXTERNAL 0
#endif


Opportunities
What is it
The difficult part when learning these ‘engineering manager’ terminology/phisolophy is realistically approaching a subordinate, rather, them approaching you with you setting them up to think they are. Instead of focusing on nuances, the important aspect as an manager is providing opportunities to younger engineers for them to take or not, tasking opportunities to senior engineers, then the middle ground where it’s a slight mix of both. A stronger version of providing opportunities and little on the plate of tasking opportunities. How the maximise is the question.
Problem identification
It’s easy to sit back, at least for me, and identify a lot of problems. I approach the system with the customer mindset learned from entrepreneur days; what exactly is it that would attract ‘me’ as a customer? Seamless/frictionless, intuitive, robustness, etc. The importance varies greatly among peoples experience and goal: straightforward or experience. It’s finding the middle ground with the business value in mindset that is important.
Wordage
Wording your approach is key in moving forward with a solution. Due dilligence needs to be done before laying it on the table but first, getting the person in charge on board. Use their method of incentives against them, tailer it to their ears. As stupid is it may be in this current economy, the concept of tailering each resume for a job is blasphemy. You have no reference on who is looking at the resume as if they always are. You can get a general gist of the ‘mission’ of a company but frankly it’s generic and broad corporate linguistics that realistically attract other businesses. One big hustle. Not to stray away but understand words are powerful, get the gist across in the tailored method.


Show Menu
Home
Tracking
View Map
View Database
Assignments
Wiki
About
Assignments
{% if is_Valid == True %}
{% for assignment in assignments %}
UUID: {! assignment[0] !}
Is Vehicle:
{% if assignment[1] %}Yes{% else %}No{% end if %}
Name:
{! assignment[2] !}
{% end for %}
Change Assignment
Platoon
Vehicle
{% end if %}


This widget attempts to load some remote resource using a cross-origin XMLHttpRequest. While the load is in progress, the circle is filled yellow. After a successful load it turns green, in case of an error it will become red.


---
title: "Many Solutions, One Goal."
layout: splash
permalink: /
header:
overlay_color: "#5e616c"
overlay_filter: ".65"
overlay_image: assets/images/aplura-splash-graphic.jpg
actions:
- label: "About"
url: /Services/
excerpt: "Information Security: Operations, Consulting, and Development"
intro:
- image_path: assets/images/alogo_cleaned.png
image_size: 224px
title: "What We Do"
excerpt: "We are committed to improving the IT security of organizations by providing expert knowledge and ingenuity to
produce solutions tailored to our clients’ specific needs. Our measurable results are highlighted by diminished
security-related incidents leading to reduced overall client costs."
feature_row:
- image_path: assets/images/logo_splunk_powered_high_resized.png
alt: "Splunk_Logo"
title: "Splunk - need to confirm use of logos"
excerpt: "As a [Splunk](https://www.splunk.com/) integration partner and [powered consultant](https://www.splunk.com/view/partner-directory/SP-CAAAGQY) since 2008, Aplura is Splunk’s longest-running partner in this category.
Aplura is trusted to fulfill professional services on behalf of Splunk via sub-contract and is regarded highly throughout the international Splunk community."
btn_label: "Read More"
btn_class: "btn--primary"
- image_path: assets/images/Gigamon_Logo_resized.png
image_size: 100%
alt: "placeholder image 2"
title: "Gigamon"
excerpt: "Our staff’s security engineering and intrusion detection experience is complimented by the innovative features of [Gigamon](https://www.gigamon.com/)
which we have supported since 2011. Additionally, through Aplura’s partner relationship, we provided sub-contract Gigamon professional
services. Rely on our staff to help your organization get the most out of your network’s data and tool analytics by having us help you implement and or manage your Gigamon products."
- image_path: assets/images/pan-logo-badge-blue-medium-kick-up_resize.png
image_size: 100%
title: "Palo Alto Networks"
excerpt: "To shore up your organization’s network gateway, Aplura can assist with your Palo Alto Networks deployment. After integrating with Palo firewalls for years with other technologies (Splunk and Gigamon), and leveraging them internal to our organization, we began providing Palo consulting services in 2014. A properly executed Palo engagement will provide your organization tremendous functionality over legacy firewalls. Additionally, we can plan the engagement to minimize and potentially eliminate network downtime."
feature_row2:
- image_path: assets/images/placeholder_image.png
image_size: 50%
title: "I need something here"
excerpt: "Something needs to go here to help break up the page but i would like a secound opion on what should go here"
btn_class: "btn--primary"
feature_row3:
- image_path: assets/images/lock.png
image_size: 4em
alt: "placeholder image 2"
title: "Security Services"
excerpt: 'Aplura provides robust and innovative solutions for our clients, including:
• [Consulting]()
• [Operations and Managment]()
• [Development]()
'
url: "/Services"
btn_label: "Services"
btn_class: "btn--primary"
- image_path: assets/images/news.png
image_size: 4em
alt: "book_logo"
title: "Resources"
excerpt: 'Aplura’s staff provide papers, seminars, and lectures to raise security awareness for their peers, clients,
and community. We encourage interested parties to contact us if a specific paper or lecture topic might be
valuable to their organization. Feel free to check the schedule or download any content that might be valuable to your organization.'
url: "/Services"
btn_label: "Read More"
btn_class: "btn--primary"
- image_path: assets/images/paper.png
image_size: 4em
alt: "placeholder image 2"
title: "News"
excerpt: '[Splunk Application Development]()
[Introducing Aplura Security for Splunk]()
[ISC2 Exam Developer Workshop]()'
url: "#test-link"
btn_label: "Read More"
btn_class: "btn--primary"
---
{% include feature_row id="intro" type="left" %}
Aplura’s staff of credentialed IT security professionals provides our clients information security
resources for daily operations as well as project-based expert technical assistance. Our engineers
specialize in the following technologies:


Thank you for confirming you have completed the callback.
Message:
"{{ details.notes }}"
To add a note, write any action taken below.
This will go to UH Notes and CRM.
Officer email: {{ email }}
There was a problem saving the response to the callback request. Please try again.
If this continues you will need to contact ICT.
There was a problem fetching information about the callback request. Please try again.
If this continues you will need to contact ICT.


Issue 3663
: too much recursion when logging array contains itself
Steps to reproduce
Open Firebug and select+enable the Console Panel
Press this button
Execute
The Console panel should display:
["a1", [...], "b1"]
[...]
represents a cycle reference


There was a problem submitting some of your assessments
- Competition:
- Innovation Lead:
- Accept applications deadline:
- Submit applications deadline:
There are currently no assessments for you to review.
Submitted assessment ()
-
PERCENTAGE
Overall scoreVERDICT


aided by interactive sandbox excerises
explore in the CSS sandbox
in our mutliple choice test section


| DOSE: |
4 tsp |
oral |
Nutmeg |
(ground / crushed) |
Having just been dumped by my girlfriend and being immersed in the gray swirling vortex of clouds that is Portland, Oregon. I decided that I needed an escape from my troubles. It was April, and me and my friends were all still in school. Nutmeg sounded interesting to me as it is just a household spice. The idea that it could get me high was just something I had to try for myself.
I went down the street to an organic food store near my house and purchased some bulk nutmeg: about seven nuts for $1.77. I pulverized the nuts with my physics text book and ground up the chunks in a coffee grinder, and put precisely four teaspoons in a plastic baggie. I was going to go to the beach tomorrow with my friends, and I was going to get high (not on marijuana because I'd given it up for lent).
I awoke early the next morning to leave for the spot I was getting picked up by my friends. Before I left I ate two teaspoons of the dreadful stuff. It tasted like someone was making Chai in my throat at first, and then it just got disgusting. I took the bus across town and waited for them to roll up in their car. As I waited (for two hours), I looked up at the sky. It was a morning sky with the sun rising in between patches of gray and white clouds. To me it looked beautiful, like a big orange egg yoke smiling at what would become a wonderful day. This could have been intensified by the drug, but I doubt it and I remember having the odd feeling that the sky was closer to me than usual, almost like a ceiling directly above me. That, I attributed to the nutmeg.
When my friends finally arrived, I hopped in the car and they showed me the psilocybin mushrooms they were going to eat and the marijuana they would smoke. I responded with a firm 'not me' and I whipped out my bag of nutmeg and started eating the rest. The taste of it was bad for me, it felt like eating sawdust and I felt a bit a twinge of nausea. Fortunately, I have a very weak sense of taste, and this permitted me to eat it all the old fashioned way. On the way to the beach (three hours where we were going), I played a miniature guitar to distract myself from the nausea of both the nutmeg and the car ride (I'm not used to riding in cars with automatic transmissions).
It was during this drive (T +5) that I began to feel the effects of the nutmeg. It was like a drunken/stoned kind of buzz, except that I still felt like I could think clearly, and according to the people around me, I was.
We actually got to the beach shortly after I could feel the nutmeg, and once there, I took in the bright white of the beach and the salt smell. My friends turned on some loud music and started eating mushrooms and smoking marijuana, and I sat down and played some guitar. I remember looking at the ceiling, which had a stucco-ed texture, and it looked like it was slowly moving away from me. I was playing guitar while I was looking up, and while I wasn't looking at the neck, I could clearly see it in my mind. I had absolute control over the instrument, and my friends were all really impressed.
After they'd done their drugs and we'd settled into the beach house, we all walked down to the shore. I was the only person seriously funked up at the time, and I still remember how cool it looked and felt with the salty air and our beachball games in the crazy wind. We walked down to haystack rock (which is this huge outcropping on the oregon coast) it was awesome. Everything took on a surreal quality and it felt like the world was a bright and beautiful place.
After a while on the beach, we went back to the house. It was during this time that I noticed my heart beating really fast. I thought I'd lay down and try and rest my head, so I layed down on a bed and closed my eyes. The instant I closed my eyes I saw these odd hallucinations which were, in ways, the most vivid hallucinations I'd ever seen. At first, I just saw these amoeba-shaped blobs of bright shifting colors, and then I opened my eyes and shut them again. This time, I saw a Jamaican band leader in a high-school-band-type marching band usiform playing a marimba with a loose calypso rhythm. He appeared to be like a moving stained-glass window, and as he played, I began to hear the music he was making inside my head.
I tried to tell my friends about this when we bought some ice-cream, but they really weren't interested. We went for a drive with one of my friends without a license driving, and I freaked out because he was really bad. After that, we returned to the beach and ran down the dunes until it got dark. Going down the dunes felt liberating, and over my vision appeared a slight white haze that gradually intensified. And I had intense afterimages of everything I saw. Looking back on it, I can't remember any exact times I went down the dunes, I just remember how it felt.
When it was dark, we went to the beach one last time and made a fire. Everyone was getting down with their girlfriends, and me without mine, I decided to ask this girl who I had met that day if she wanted to make out with me. Surprisingly, she said yes (I think she was getting back at her ex-boyfriend who was on the trip). So we did a little of this and a little of that.
We drove back that night, and I didn't sleep until I got home (at about one in the morning). I was really tired. The next day, I was able to reflect on the experience, but there was still a white haze over my vision. I realized I shouldn't have made out with that girl (she not my type, I couldn't really talk to her, it was not a good thing). But what was the most disturbing was the fact that I could still feel the nutmeg in me. I went to dinner with my parents that night, and it felt so wierd, like I was barely on top of the conversation, and that at any moment, the next comment might put me completely under the tide of words.
Time passed, and my daily sleep at that point was very low. I was taking classes starting at 7:20 AM, and I was doing homework and stuff until about 11 PM every night. I was not getting enough sleep for my standards, and I became enveloped in the white hazy nutmeg life. I remember sitting in Physics class and understanding the words that our teacher was saying, but not comprehending their meaning. It was just like a part of my brain was not switched on.
Furthermore, one day in my history class, I was trying my hardest to pay attention, when suddenly, an huge purple plasma V emerged from my teacher's chest framing his head. I was gaping, open-mouthed at the spectacle, and I don't think I will ever forget that.
After lent, my life returned to normal. I would only think about doing nutmeg if I had a lot of time to waste. It was an interesting experience, and it felt beautiful when I was actually high, but the coming down period was very wierd and prolonged.
Experience Reports are the writings and opinions of the individual authors who submit them.
Some of the activities described are dangerous and/or illegal and none are recommended by Erowid.


3 Organising an R project at Grattan
All our work at Grattan, whether it’s in R or some other software, should heed the “hit by a bus” rule. If you’re not around, colleagues should be able to access, understand, verify, and build on the work you’ve done.
Organising your analysis in a predictable, consistent way helps to make your work reproducible by others, including yourself in the future. This is really important! If your analysis is messy, you’re more likely to make errors, and less likely to spot them. Other people will find it hard to check your analysis and you’ll find it harder to return to it down the track.
This page sets out some guidelines for organising your work in R at Grattan. It covers:
- Using RStudio projects and relative filepaths;
- Using a consistent subfolder structure; and
- Naming your scripts and keeping them manageable.
Using a consistent coding style also helps make our work more shareable; that’s covered on the next page.
3.1 Use RStudio projects, not setwd()
In Excel, your data, code and output generally all live together in one file. In R, you have a script, which will usually load some data, do something to it, and save some output. You end up with multiple files - the raw data, your script, and some output. Your R script is like a recipe in a cookbook - when R is cooking your recipe, it needs to know where to find your ingredients (the data) and put the finished product (your delicious analysis).
When it’s executing your script, R needs to know where to read files from and save files to on your computer. By default, it uses your working directory. Your working directory is shown at the top of your console in RStudio, or you can find out what it is by running the command getwd()
.
You can tell R which folder to use as your working directory by using the command setwd()
, as in setwd("~/Desktop/some random folder")
or setwd("C:\Users\mcowgill\Documents\Somerandomfolder")
. This is a bad idea that you should avoid! If anyone - including you - tries to run your script on a different machine, with a different folder structure, it probably won’t work.
In the words of Jenny Bryan:
if the first line of your R script is
setwd("C:\Users\jenny\path\that\only\I\have")
I will come into your office and SET YOUR COMPUTER ON FIRE.
Seems fair.
Creating a ‘project’ in RStudio sets your working directory in a way that’s portable across machines.
3.1.1 How to create a project
Creating an RStudio project is straightforward: click File, then New Project. You can then choose to start your project in a new directory, or an existing directory. Simple!
RStudio will then create a file with an .Rproj extension in the folder you’ve chosen.
3.1.2 Opening a project
When you want to work on a particular project, just open the .Rproj
file, or click File -> Open project in RStudio. Your working directory will be set to the directory that contains the .Rproj file.
3.2 Use relative filepaths
A benefit of using RStudio projects is that you can use relative filepaths rather than machine-specific filepaths.  Who wants to type out a full filepath everytime you load or save a file?
Bad, machine-specific filepaths, boo, hiss
hes <- read_csv("/Users/mcowgill/Desktop/hes1516.csv")
hes <- read_csv("C:\Users\mcowgill\Desktop\hes1516.csv")
grattan_save("/Users/mcowgill/Desktop/images/expenditure_by_income.pdf")
Instead, use relative filepaths. These are filepaths that are relative (hence the name) to your project folder, which you set by creating an RStudio project.
Good, relative filepaths, cool, yay
The first example above tells R to look in the ‘data’ subdirectory of your project folder, and then the ‘HES’ subdirectory of ‘data’, to find the ‘hes1516.csv’ file. This file path isn’t specific to your machine, so your code is more shareable this way.
At Grattan, we even have our own R package, called grattandata that helps load certain types of data in R in a way that makes your script portable and reusable by colleagues. We cover that more in the Reading Data chapter.
3.3 Keep your stuff together
Your script(s), data, and output should generally all live in the same place.3 That place should be the project folder - that’s the folder that contains the .Rproj file that was created when you created an RStudio project (you did that, right? Scroll back up the page if not).
Don’t just put everything in your project folder itself. This can get really overwhelming and confusing, particularly for anyone trying to understand and check your work. Instead, separate your code, your source data, and your output into subfolders.
A good structure is to have a subfolder for:
- your code - called ‘R’
- your source data - called ‘data’
- your graphs - called ‘atlas’, like in our LaTeX projects
- your non-graph output, like formatted tables, called ‘output’
Sometimes your data folder might have subfolders - ‘raw’ for data that you’ve done nothing to, and ‘clean’ for data you’ve modified in some way. Don’t keep ‘raw’ data together in the same place as data you’ve modified.
Other folder structures are OK and might make more sense for your project. The important thing is to have a folder structure, and to use a structure that is easily comprehensible to anyone else looking at your analysis.
3.4 Keep your scripts manageable
Unless your project is very simple, it’s not a good idea to put all your work into one R script. Instead, break your analysis into discrete pieces and put each piece in its own file. Number the files to make it clear what order they’re supposed to be run in.
Here’s a useful structure:
- 01_import.R
- 02_tidy.R
- 03_model.R
- 04_visualise.R
You don’t need to use these filenames. Think about what works best for your project.
It should be clear what each script is trying to do. Use meaningful filenames that clearly indicate the overarching purpose of the script. Use comments to explain why you’re doing things. Err on the side of over-commenting, rather than under-commenting (we cover this more elsewhere in this guide). At the end of each script, you can save the script’s output, and then load the file you create in the next script.[^Alternatively, source()
the previous script.]
3.5 Make your filenames readable by both machines and humans
Have another look at the example filenames set out above:
- 01_import.R
- 02_tidy.R
- 03_model.R
- 04_visualise.R
They’re sortable - they start with a number. They don’t have spaces, so any and all software should be able to handle them. And, even though they’re short and minimal, they give humans a good idea about what the files do. These are what you should strive for when choosing filenames.
For more on good principles for naming files, see this excellent presentation by Jenny Bryan, which includes the following examples:
Don’t create multiple versions of the same script (like analysis_FINAL_002_MC.R
and analysis_FINALFINAL_003_MC_WM.R
.) We’re all familiar with this hellish scenario: you do some work in a Word document (shudder, shudder, the horror, etc.), email it to a colleague, the colleague edits it and sends it back with a tweaked filename, like cool_word_doc_002.docx
. Soon enough your hard drive and email client is cluttered with endless iterations of your document. Try to avoid replicating this nightmare in R.
If you do end up with multiple versions, put everything other than the latest version in a subfolder of your “R” folder, called “R/archive”. To avoid a horrible mess of analysis_FINAL_002.R
type documents cluttering up your folder, consider using Git for version control.
3.6 Include a README file
Your analysis workflow might seem completely obvious to you. Let’s say that in one script you load raw ABS microdata, run a particular script to clean it up, save the cleaned data somewhere, then load that cleaned data in a second script to produce a summary table, then use a third script to produce a graph based on the summary table. Easy!
Except that might not seem easy or self-explanatory to anyone who comes along and tries to figure out how your analysis works, including you in the future.
Make things easier by including a short text file - called README - in the project folder. This should explain the purpose of the project, the key files, and (if it isn’t clear) the order in which they should be run. If you got the data from somewhere non-obvious, explain that in the README file.
3.7 Keep your workspace clean
Sometimes R doesn’t behave the way you expect it to. You might run a script and find it works fine, then run it again and find it’s producing some strange output. This can be the result of changes in your R environment. You can set different options in R, which can (silently!) affect things. Or maybe you had some different objects - data, functions - defined in your environment the second time round that you didn’t have originally, or some extra packages loaded.
To avoid this situation, keep your workspace tidy. When you load a script, do it in a fresh R session.
But… don’t clean your workspace within your analysis script. People sometimes do this using this command:
This removes all objects from your environment. But it doesn’t completely clear your R environment, and it doesn’t do anything to any packages you have loaded. As Jenny Bryan puts it, this command is “a red flag, because it is indicative of a non-reproducible workflow.”
3.8 Quick guide to starting a project
When you’re starting a new project:
- Open RStudio;
- Click ‘File -> New project’
- Click ‘New Directory’
- Click ‘New Project’
- Give your new project a name, choose where it should go, and click ‘Create Project’
- Create subfolders in your project folder using the ‘New Folder’ button (by default in the lower-right pane of RStudio) - start with an ‘R’ folder
- Click ‘File -> New File -> R Script’
- Save your R script in your R folder.
Now you’ve got a good shell of a project - a dedicated folder, with an associated RStudio project, and at least one subfolder. This is a good base to start your work.
This isn’t always possible, like when you’re working with restricted-access microdata. But unless there’s a really good reason why you can’t keep your data together with the rest of your work, you should do it.↩


4 Indian-origin ministers inducted in Canadian PM Justin Trudeau's new cabinet
Another key portfolios reshuffle was Chrystia Freeland who has been moved from foreign affairs to become Canada’s Deputy Prime Minister.
by REUTERSMumbai: Canadian Prime Minister Justin Trudeau on Wednesday announced members of Cabinet, following swearing-in ceremony, which included four Indian-origin ministers.
Four Indian-origin MPs Navdeep Singh Bains, Harjit Singh Sajjan, Bardish Chaggar and Anita Anand have been included in the new cabinet. Anita is the first ever Hindu minister in the cabinet, who has been made minister of public services and procurement.
Bains becomes minister of innovation, science and industry. Chagger has been appointed as minister of diversity, inclusion and youth, while Sajjan remains the minister of national defence.
Another key portfolios reshuffle was Chrystia Freeland who has been moved from foreign affairs to become Canada’s Deputy Prime Minister. Freeland, 51, will be responsible for trying to repair regional fractures.
Trudeau’s Liberals lost all their seats in the oil-rich provinces of Alberta and Saskatchewan, furthering a sense of alienation in a region already deeply frustrated with the government’s energy and pipeline policies.
Here are details of ministers with key portfolios:
Finance: Bill Morneau
Morneau has been Canada’s finance minister since 2015, the same year he was first elected to office. Prior to 2015, the Toronto member of parliament headed the human resource firm Morneau Shepell. He is also a former chair of the C.D. Howe Institute, a Canadian thinktank.
He is married to Nancy McCain, an heir to Canada’s McCain Foods empire.
Foreign Affairs: Francois-Philippe Champagne
A lawyer by profession, Champagne spent more than 20 years working for large multinational companies, including Swiss-Swedish automation firm ABB Group, before being elected in 2015.
Champagne, an international trade specialist, served as minister of international trade in 2017 where he led Canada’s negotiations for the Comprehensive and Progressive Trans Pacific Partnership before moving to the infrastructure ministry.
Environment: Jonathan Wilkinson
Wilkinson is the former CEO of QuestAir Technologies, a company that specializes in gas purification systems, and BioteQ Environmental Technologies, a company that specializes in water management within the mining industry.
Wilkinson, who represents a constituency in the left-leaning province of British Columbia, said in June he was in favor of the Trans Mountain pipeline, a contentious issue in Western Canada. He previously served as Canada’s fisheries minister.
Natural Resources: Seamus O’Regan
A former TV anchor, O’Regan has previously served as Canada’s veterans minister and minister of indigenous services. He comes from the oil-producing province of Newfoundland and Labrador.
O’Regan, who is one of Trudeau’s closest friends and attended his wedding, faced criticism in December after he compared his own career arc as similar to the problems facing many ex-military members.
Agriculture: Marie Claude Bibeau
First elected in 2015, Bibeau was appointed as Canada’s first female agriculture minister in March. Bibeau, who hails from the French-speaking province of Quebec, was previously minister of international development.


Total Residential Units: {{analytics.total_residential_units}}
Total Non-residential Sqft: {{analytics.total_non_residential_sqft | numeraljs:'0,0'}}
Total Acres: {{analytics.total_acres | numeraljs:'0,0'}}
Raw Residential Capacity: {{analytics.raw_residential_capacity | numeraljs:'0,0'}} Units
Raw Non-res Capacity: {{analytics.raw_non_residential_capacity | inMillions | numeraljs:'0,0.00'}}M Sqft


THE BROTHERS A film review by Annette Cardwell Copyright 2001 filmcritic.com
Like many other African-American-targetted flicks like The Best Man and Waiting to Exhale, The Brothers is best when it's trying to be a comedy and comes off as fluffy if not sappy and lame when attempting to teach us more serious lessons about life and love. But this movie about the trials and tribulations of four attractive, successful "buppies" will definitely entertain, and it's sure to rake in the box office cash.
The four "brothers" are commitment-fearing Jackson (Morris Chestnut, who also starred in The Best Man), woman-hating playboy Brian (Bill Bellamy), not-so-happily married Derrick (D.L. Hughley) and reformed womanizer Terry (Shemar Moore). When Terry decides to get married, his boys start sizing up their own lives.
Jackson's new girl Denise (Gabrielle Union) seems like "the one," until he finds out a secret from her past. Derrick's wife (Tamala Jones) isn't meeting his -- ahem -- needs. And Brian is busy fighting off crazy "sistahs" and venturing into interracial dating, only to find that all women are -- to him -- just plain crazy anyway. In the end, they all have a lot to learn, as all these kinds of movies seem to preach.
Unfortunately, you'll have to endure the film's preaching to enjoy the truly hilarious dialogue and ad libbing from this talented cast.  He's especially a riot in the outtakes shown at the end of the movie, where he invents new versions of one of the film's already hysterical speeches.
Bellamy and Chestnut are serviceable and sometimes even good in their roles, but the wooden Moore is clearly just hunky, chiseled, Rick Fox-wannabe eye candy. Thankfully for him, this is definitely the type of movie that calls for a guy like Moore. It's a picture that's tailor-made for the ladies -- especially black women -- who will be swooning over these almost-perfect, hard-working, educated "brothers" who just need a good woman to make them "wanna be a man." And, it doesn't hurt to throw in a few gratuitous shirtless basketball scenes that could rival the famous volleyball scene from Top Gun.
For anyone who's already a fan of Hughley or the comedy of Chris Rock and his ilk, or even if you just like ogling a pack of "fine" young African-American men, The Brothers has a lot to offer. Don't go looking for any sage revelations on life, love and happiness. When this hit-and-miss script gets up on its pulpit, you may want to walk out on the sermon.

Visit filmcritic.com on the Web at http://www.filmcritic.com
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


This is a modern commercial port with little attraction as a cruising destination. Few cruisers visit, except to visit the beautiful city of Antigua which is 1.5 hours away.
Carbon soot discharge from ships just west of the marina can be a problem here if a westerly breeze moves in. This gritty, sharp, grey sand will cover your boat. The ENRON bunker diesel power plant operates just inside the Puerto Quetzal entry channel, to the east, which adds to the commercial port environment.
This new port was built on the Pacific side to replace the old port of San José.
Port Control should be contacted on VHF Channel 16 for instruction on where to berth for clearance. You need to contact Port Control at the sea buoy to get permission to enter. They will assign an agent to handle all the paperwork. It is very expensive with the cost of an agent at around $300 as well as the $2/ft/night charge for berthing.
To ensure the safety of visiting yachts, the Navy requires that yachts come directly to the naval basin, where security is excellent. All formalities are completed from there.
Last updated August 2012.
Once into the harbour, enter the western basin and there is docking for yachts in a small basin on the northern side.
The marina, whilst secure, is open to swells from the SW and the surge here is reported to be very bad, with reports of burst fenders and broken dock lines.
Last updated April 2014.


| Home | Trees | Indices | Help |
|
|---|
|
|
object --+ | BaseSequenceParser
FASTA parser template. Subclasses must implement the way FASTA strings
are handled by overriding
BaseSequenceParser.read_sequence
.
| Nested Classes | |
|
__metaclass__ Metaclass for defining Abstract Base Classes (ABCs). |
| Instance Methods | |||
|
|||
| SequenceCollection |
|
||
| SequenceCollection |
|
||
| iterator |
|
||
| AbstractSequence |
|
||
|
Inherited from |
| Class Variables | |
__abstractmethods__ =
|
| Properties | |
| class |
product_factory Factory used to build sequence products |
| enum item |
product_type Default sequence type of the products - a member of SequenceTypes |
|
Inherited from |
| Method Details |
x.__init__(...) initializes x; see help(type(x)) for signature
|
Read FASTA sequences from a (m)FASTA file
|
Read FASTA sequences from an (m)FASTA-formatted string
|
Read FASTA sequences from an (m)FASTA file.
|
Parse a single FASTA string
|
| Property Details |
product_factoryFactory used to build sequence products
|
product_typeDefault sequence type of the products - a member of SequenceTypes
|
| Home | Trees | Indices | Help |
|
|---|
| Generated by Epydoc 3.0.1 on Tue Jul 4 20:19:04 2017 | http://epydoc.sourceforge.net |


You requested to change some of your data in our newsletter
Click here to modify your data
If you did not requested to change your data, just ignore this mail