text:
8 Ridiculous Animal Myths You Probably Believe
#4. If You Throw Rice at Weddings, You're a Bird Murderer
The Myth:
If you throw rice, birds will eat it. And when they do, it will expand in their stomachs and cause them to explode like little feathery hand grenades. You may as well just hand out shotguns loaded up with bird shot for the guests to fire over the newly joined couple's heads as they make their exit.
On the upside, it's a cheap way to drum up extra entrees for the wedding dinner.
The Reality:
Fire away! With the rice, that is. Not the shotguns. It turns out that, as we expected all along, in order to make birds explode spectacularly you'll need something like firecrackers and some duct tape, or Randy Johnson's fastball. Oh, or Alka-Seltzer, because that one's totally for real (honest).
There are a few other options, of course.
According to the Cornell Lab of Ornithology, tons of birds eat rice in the fields. In fact, they say that "Some birds cause so much damage to rice crops that they are considered agricultural pests." But a bunch of facilities still ban throwing rice anyway -- either because they aren't willing to let something as crazy as the exploding-bird myth die, or because rice on sidewalks transforms all your wedding guests into potential America's Funniest Home Videos winners.
Still, the sad fact remains that if a little rice really did cause birds to blow up in a fusillade of feathers (we're imagining a '70s-era Elton John moonlighting as a fireworks designer), we would live in a significantly more hilarious universe.
Well now there's basically no reason to get married.
#3. A Goldfish Only Has a Memory Span of Three Seconds
The Myth:
A goldfish can only remember something for three, maybe five seconds, which is about how long it takes to swim from one end of its fishbowl to the other. See? You don't need to feel bad about storing your little guy in a cramped container smaller than a cookie jar. Each time he swims over to the little plastic castle, it's like a whole new experience! He's so stupid, he's having the time of his life in there!
That little bastard lives better than we do.
The Reality:
Fish can actually remember for three, maybe five months, which is plenty of time to decide that life might not be worth living if it's spent trapped in a cramped, transparent, aquatic penitentiary.
We realize that some of you immediately said "They did this one on MythBusters!" the moment you saw the headline. But even before Adam and Jamie taught their fish to swim through an obstacle course, a 15-year-old from Australia performed an experiment by training pet fish to associate a beacon with food. After removing the beacon and replacing it a week later, the fish still beelined to it.
"Steak please, garcon!"
Even more shocking, scientists at the Israeli Technion Institute of Technology spent a month training young fish to associate a particular sound with feeding time, then released the fish into the wild. The fish still responded to the sound, five months later.
You know, it's almost like natural selection wouldn't even allow a species to survive if it forgot that there was a predator behind it three seconds into the chase. Now we need a second round of experiments to see if goldfish are capable of hating their owners.
If they can remember, they can plot.
#2. One Human Year Is Equivalent to Seven Dog Years
The Myth:
Your parents probably taught you this one when trying to delicately break the news of how close little Spot was to moving away to live on a nice farm: The idea is that a 1-year-old dog is equivalent to a 7-year-old human, a 2-year-old dog is 14 in human years, etc.
Which makes Grandma the youngest person in this picture.
The Reality:
Treating your 1-year-old dog like a 7-year-old human is fine, provided you know a lot of sexually active 7-year-olds. Scientists and dog experts have been trying to quell the propagation of the seven-year myth for years, maintaining that estimating a dog's age is inexact and often changes based on the dog's breed -- average lifespans among the hundreds of different dog breeds can range from 8 to 16 years.
The math only gets more complicated from there, but generally speaking, it turns out that developmentally, a 1-year-old dog is closer to a 17-year-old human being than a 7-year-old one. Then the increments get smaller from there, you'd have to make a graph or something to track it. Or you could just get used to the idea that a 9-year-old dog is the equivalent of a 9-year-old dog and get on with your life.
"Goddammit, Bibbles. You should know better than that. Aren't you like 25?"
It's kind of surprising that this myth ever got off the ground ... surely you've heard of more 16-year-old dogs than humans who lived to be 112. But this will not be the last time in your life you'll see humans preferring their math to be simple rather than correct.
#1. Dogs See in Black and White
The Myth:
Everyone knows that dogs see the world in the same light as an edgy indie movie director. Which really makes us question the point of differentiating the various flavors of Milk-Bone by color -- maybe they should put little pictures on them or something.
Also, we kind of doubt any dog would see this shape and think "bone" in the first place.
The Reality:
The truth is more nuanced. It's true that dog eyes don't see colors the same way human eyes do, but they do see them:
Retriever Pro
So apparently we look like zombies to them.
Dogs' eyes don't have quite as many cones as humans' (if you didn't pay attention in biology class, cones are the little things that help us differentiate between colors), so they see different colors than we do. Instead of seeing the good old Roy G. Biv color spectrum, dogs see the rainbow as "dark blue, light blue, gray, light yellow, darker yellow (sort of brown), and very dark gray." In other words, dogs see the colors of the world as basically yellow, blue and gray. They see green, yellow and orange as all being yellowish, and they see violet and blue as being the same color.
So if you've ever bought a red or orange ball and tried to play fetch on green grass, your dog probably thinks you're a dick.
"You absolute bastard."
Jonathan Wojcik has more scary bugs waiting for you on Bogleech. More from Nathan can be found on TheRollerSkate.com.
For more myths you probably think are true, check out 5 Ridiculous Animal Myths That You Probably Believe and 5 Ridiculous Sex Myths From History (You Probably Believe).


text:
Home > Aston Martin > Aston Martin Dragon 88 Limited Edition
Below you will find the high resolution car photo for Aston Martin Dragon 88 Limited Edition. You may use the car photo for any of the following standard screen resolutions:
1600x1200 | 1400x1050 | 1280x1024 | 1280x960 | 1152x864 | 1024x768 (iPad) | 800x600 Full Car Details
Aston Martin Dragon 88 Limited Edition
With China becoming the biggest automotive market in the world, car manufacturers around the world take advantage of this year's Beijing Auto Show in order to reveal their latest creations. Some of them even gone a few steps forward by debuting limited edition models built specifically for the Chinese automotive market. One of these manufacturers was Aston Martin which revealed the Aston Martin Dragon 88 Limited Edition package.

subset: commoncrawl


text:
Baseball Prepares for Key SAC Series with Newberry This WeekendApril 17, 2014
ANDERSON, S.C. – In what could be perhaps its biggest South Atlantic Conference series in the program's history, Anderson University baseball has a chance to secure a spot into next week's Food Lion SAC Tournament when it welcomes Newberry to Anderson Memorial Stadium for a three-game set beginning at 1 p.m. on Friday, followed by a doubleheader on Saturday at 1 p.m.
The Trojans
After AU captured two-of-three from then-league leader Lincoln Memorial last weekend in Harrogate, the Trojans put themselves in sixth place in the SAC standings, which would hand them the final spot in the annual postseason tournament.
Currently, Anderson carries an even 13-13 record, two games ahead of Carson-Newman (11-16), which sits in seventh-place. With AU holding the tiebreaker over the Eagles due to the series win on Feb. 15-16, the Trojans need a win and a C-N loss on Friday to earn a berth into the SAC Tournament.
As a team, AU leads the league in doubles with 85 and home runs with 41, as the Trojans are currently the only team in the SAC with more than 40 homers for the year. A major contribution to the home run total is senior outfielder Nathan Galliford who homered a league-high 15 times this season, which also leads the country. Following Galliford is sophomore Steven Cooper with eight and sophomore middle infielder Kyle Bailey, who ranks ninth in the league with five round-trippers.
Despite a 0-for-5 performance against nationally-ranked Lander on Wednesday, Cooper continues to put together one of the best seasons by a Trojan. Cooper leads the SAC in doubles (17), total bases (108) and runs batted in (46). Cooper also ranks second in hits (63) and ninth in slugging percentage (.597).
Anderson is hitting .298 as a team, as five Trojans who have played in 11 games or more are hitting above .300 on the year. Senior catcher Jonathan Zalud has recorded nine hits in his last four games and has overtaken Cooper for the team lead in average at .357.
On the mound, junior right-hander Landon Beck continues to impress with his 75 strikeouts (second in SAC) in 61.2 innings pitched. Beck has tossed five complete games, which leads the conference, while averaging 10.95 strikeouts per game.
The Wolves
Currently in the SAC standings, Newberry is a half-game ahead of the Trojans as it holds a 14-13 conference record with a 26-21 overall mark. The Wolves are currently on their second longest winning streak of the season of six straight wins, their longest since beginning the season 6-0. During the streak, NC swept Coker last weekend prior to back-to-back nonconference victories over Pfeiffer and USC Aiken.
The Wolves pace the conference in hits with 459 on the campaign as junior infielder Albert Baur leads the team with 64 hits, including 20 extra-base hits. Baur also leads Newberry in RBI with 43, while slugging .484 and scoring 30 runs. Fellow infielder, senior Ryan Cranmer is hitting .371 for the year with a team-high eight home runs with 36 RBI. Cranmer has scored 41 runs while driving in 36.
Defensively, Newberry's pitching staff has held opponents to a .272 average while accumulating the conference's second lowest ERA at 3.79. Left-hander Wesley Camp has led the NC pitching staff with 87.2 innings pitched and three complete games. Camp has posted 59 strikeouts with just 19 earned runs.
The Series
Last season, Anderson captured two-of-three from Newberry for the first time as conference rivals with back-to-back wins in the final two games of the three-game series. Prior to the series win, the Wolves grabbed two-of-three from the Trojans in each of the past two seasons.


text:
WickedSun, February 24, 2013 - 6:30 PMSegerstrom Center for the Arts Segerstrom Hall in Costa Mesa, CA
We are sorry, the date for this event has already passed. This event took place on 2/24/2013. Click here to view upcoming events for Wicked.
Still unsure? Check out our user reviews for:
Have a question? Need help? Call us at 800.477.5285


text:
Sorry, the page you are trying to open is available only for our paid subscribers.
- Please sign in below if you wish to continue
- New users, please register
Corning posts stronger results for 2Q16
Displays | 13min ago
SJSemi, Qualcomm announce mass production of 14nm wafer bumping
Bits + chips | 52min ago
China imports 71,000 tons of polysilicon in 1H16
Green energy | 59min ago
- AUO to start 6G LTPS production in eastern China in 4Q16
- Nanya, Inotera deals with Micron still proceeding
- UMC looks to 2-3% shipment growth in 3Q16
- Digitimes Research: Taiwan ships nearly 8.5 million LCD TVs in 2Q16
- Coretronic nets NT$1.13 per share for 1H16
- MLS upbeat about synergy with Osram
- BlackBerry launches new Android smartphone
- SPIL reports NT$0.90 EPS for 2Q16
- Pegatron automates factory in Shanghai, says chairman
- Nanya 2Q16 profits fall
- Connector maker Sinbon reports earnings for 2Q16
- Digitimes Research: Over 4,000 models of LTE-enabled devices launched as of February 2016
- Osram to sell lamp business unit to China-based consortium
- AUO reports operating profit for 2Q16
- Notebook players less keen to adopt USB Type C
- Taiwan to be flexible in allocating frequency band for IoT, says minister
- ET Solar, LONGi set up joint venture for PV module marketing
- State Power Investment procures 2.75GWp of PV modules
- Component makers to see weak orders for tablets and wearables
- China may lower target PV installation capacity in 13th 5-year plan
- HTC to face increasing competition in VR market in 2H16
- Nuvoton reports NT$1.25 EPS for 2Q16
- Analog Devices, Linear to merge
- E-sports expected to push demand for gaming notebooks, desktops in 2H16
- Hangzhou factories concerned about impact of air pollution controls during G20 Summit
28-Jul-2016 markets closed
|TSE electronic
|OTC electronic
- How AMD CEO Lisa Su tripled the chip maker's stock in 5 months (Jul 22) - Fortune
- With Verizon's backing, Yahoo's longtime suitor gets his prize (Jul 26) - Bloomberg
- AMD mulls a CPU+GPU super-chip in a server reboot (Jul 24) - PC World
- AMD officially diversifies 14nm manufacturing with Samsung (Jul 25) - Forbes
- Apple's iPhone 7 could launch on September 16 (Jul 25) - Fortune
- Intel ships Kaby Lake chips, pointing to PC availability in a few months (Jul 20) - PC World
- Wi-Fi gets multi-gigabit, multi-user boost with upgrades to 802.11ac (Jun 30) - Ars Technica
- Verizon to end Yahoo survival fight with US$4.8 billion deal (Jul 25) - Bloomberg
- Releases
- White papers
- Bulletin
- CAYIN to rollout system software upgrade and new product line
- Digital signage proficiency holds the key to smart retail
- Taiwan International Fruit and Vegetable Show to highlight potential of local IT sector in helping spur agricultural innovation
- All about Security, Fire and Safety in IFSEC Southeast Asia 2016
- GMobi shifting gears aiming for automotive market
- Unisys IT Implementation of Unisys Stealth Solution for Data Center Segmentation
- Getting the Most Out Of Your Next Generation Digital Security Surveillance System
- Embracing the New Generation Intel Atom Family with DDR3 Memory Support
- Got The Message? Ensuring efficient and reliable delivery of content across a mission critical digital signage network
- Emb' Store On-Demand Software Service for Embedded Computing
- Perforce Software Wins Develop Industry Excellence Award for the Second Year in a Row
- Perforce Teams with Leading Git Client Developer fournova
- Perforce Introduces Helix GitSwarm: Flexible Git Ecosystem Mirrored to a Powerful Mainline Repository
- Perforce Helix Distributed Version Control System Brings Greater Flexibility While Maintaining Enterprise-class Security, Auditability and Control
- Perforce Powers Development of Legacy Quest for iOS and Android
- Digitimes Research: 4 million 9.7-inch iPad Pros to ship in 1H16
- Digitimes Research: Global all-in-one PC shipments to drop 3.9% on year in 2015
- Digitimes Research: iPad Pro shipments to be less than 3 million units in 4Q15
- Digitimes Research: Intel processor shipments rely on Windows tablets for growth
- Digitimes Research: Tablets with phone functionality from white-box players to suffer over 15% decline in 2Q15
The early success Google's Android platform has achieved in the handset market has caused system makers, software developers and semiconductor players...
Taiwan notebook Original Design Manufacturers (ODMs) account for more than 90% of global notebook production and Digitimes is there to provide daily...
Virtual reality has become the latest topic of the PC industry with players such as Samsung, HTC, Google and Sony, all aggressively pushing into.
HTC is banking on its VR device to revive its business
The gaming notebook competition: Q&A with Jone Chang from Gigabyte notebook department
Gaming notebooks have become the main focus of Gigabyte Technology's notebook department and despite...
Powering the cloud: Intel embraces new identity
The next wave of computing is now beginning to define the IT industry, where the boundaries of computing...
A new cycle begins for desktop motherboards: Q&A with Gigabyte technical marketing manager, Leon Chen
The launch of virtual reality headsets for the consumer market and the increasing demand for ultra...
IoT, Big Data and biological sciences: Q&A with Dassault Systemes president Bernard Charles
Dassault Systemes, a European multinational software company that develops 3D design, 3D engineering,...
- Smartphone and tablet industry: The view from Taiwan - May 2012
Taiwan-based companies have a long and successful history of involvement in the supply chain for mobile devices, which for the purposes of this article consist...
- Taiwan motherboard industry overview - May 2012
The year 2011 saw the motherboard industry reverse its trend of declining shipments year-on-year, to post a slight 0.2% growth. This upturn in fortunes was expected...
- Notebook market overview - Jun 2011
The notebook industry in 2010 experienced several major events that significantly changed the industry's ecosystem for the year and the industry is also believed...
- Taiwan motherboard industry overview - Jun 2011
The motherboard industry began 2010 with optimism and expected to see a reversal of the previous two years' declines in revenues and shipments as the impact of...
- Wireless broadband developments in Southeast Asia markets
As of 2013, the 10 ASEAN nations had a total of over 700 million mobile subscriptions, with the CAGR from 2003-2013 reaching 24%. This Digitimes Research Special Report analyzes the various mobile broadband markets in ASEAN and looks at the respective trends in 4G LTE development for those markets.
- 2015 global tablet demand forecast
This Digitimes Research Special Report provides a 2015 forecast for the global tablet market and analyzes the strategies of key market players such as Google, Apple, Intel, and Microsoft.
- 2015 China smartphone panel trend forecast
This Digitimes Research Special Report analyzes the strategies of key China-based major panel makers BOE, Tianma and IVO for attacking the different market segments through technology and pricing, and their relationship to local vendors Huawei, Lenovo, ZTE, Xiaomi and Coolpad.


text:
The Seahawks' Grabby Talons
Seattle's Defense Relies On a Brazen Tactic: Rampant Interference
On Saturday, the New Orleans Saints take their flashy passing offense up to dreaded Seattle. We wish them the best of luck with that.
The Seattle Seahawks—the favorites to make the Super Bowl out of the NFC—employ an exasperating defensive game plan: They blitz rarely and drop an army of defenders into pass coverage. And those defenders mug, obstruct and foul opposing receivers on practically every play.
Quietly, the Seahawks have achieved a 13-3 record and home-field advantage throughout the NFC playoffs by exploiting a loophole: NFL referees are reluctant to throw endless flags for pass interference and defensive holding, even if defenses deserve them.
"They look at it and say, 'We may get called for one but not 10,'" said Mike Pereira, a former NFL vice president of officiating who is now a Fox analyst.
League insiders say this divisional-round matchup between the Seahawks and Saints, the NFC's top passing offense, may be Seattle's rule-bending masterpiece.
"They just seem to not care about the rules," said New York Giants wide receiver Louis Murphy, whose team was routed 23-0 by Seattle this season.
The Seahawks' success is widely attributed to the outstanding play of quarterback Russell Wilson and the earsplitting din of CenturyLink Field, their home stadium. Seattle's backbone remains its defense, which led the NFL this season in points allowed and yards allowed (the latter by far). The strategic idea behind that defense is uncommonly aggressive pass coverage.
The Seahawks had the most pass-interference penalties in the league this season—13, or nearly one per game. Defensive pass interference, a spot foul that comes with an automatic first down, is called when a defender impedes a receiver while the ball is in the air. If the ball isn't airborne, grabbing a receiver more than five yards downfield merits a defensive-holding penalty. The Seahawks have 10 of those this season.
There is a certain brilliance to this approach: Since 2001, nine teams have committed 20 or more of these penalties (including this season's Seahawks). None of them had a losing record, and most of them won big.
So many pass-interference plays meant that many more of them went uncalled, choking the life out of opposing offenses in a pass-dependent league—a big advantage for Seattle's physical brand of defense, led by hulking cornerbacks such as 6-foot-3 star Richard Sherman.
The Seahawks didn't respond to requests for comment, but defensive coordinator Dan Quinn said earlier this season that the Seattle coaches educate their players on what type of interference plays are being called around the league.
"We challenge and we play at the line and we like that style," he said.
Expect the no-calls to get worse in the playoffs. This season, NFL officials called 12.2 penalties a game, but in last week's wild-card round, they called 7.8. There has been a 41% drop in postseason penalties since the 2008 playoffs, while in the regular season, penalties are up 8.9% in that time.
Pereira said aggressive pass-coverage teams like Seattle "test" referees early in the game with a few potentially obvious pass-interference infractions. "They want to see what kind of tone the officials are going to set," he said, adding that he expects to see a couple of penalties called but also the usual brand of Seahawks grabbing.
Game-film analysis reveals plenty of instances in which more penalties could have been called. Facing a third-and-10 on the first possession of their Week 5 matchup with Seattle, the Indianapolis Colts called for a pass to star receiver Reggie Wayne. As soon as the ball was snapped, Wayne was engulfed in a bear hug by Seahawks cornerback Brandon Browner, who proceeded to grab the Colts receiver by his shoulder pads, spin him around and force Andrew Luck's pass to fall incomplete.
The Seahawks' defense adopted a similar strategy early in a Week 8 victory over the St. Louis Rams. On their opening drive, the Rams faced a third-and-6 from their own 38. Rams receiver Tavon Austin ran a short curl route and was immediately clobbered by Seahawks safety Earl Thomas. There was only one problem: The ball hadn't even left the quarterback's hand. Kellen Clemens threw the pass anyway, Austin's arms were pinned to his sides and the Rams were forced to punt.
Former Seahawks quarterback Brock Huard, now a radio host for ESPN Radio in Seattle, said the contact between receivers and the Seahawks' defensive backs forces offenses to change their entire game plan. For instance, basic routes like the skinny post, on which a receiver bounces slightly toward the middle of the field (in the direction of the goal post), must be scrapped because receivers can't accelerate fast enough after contact.
Even if the receivers do get to full speed, the long arms of defensive backs such as Sherman simply poke the ball away if a pass is anywhere near them. That goes for "vertical" routes, too, the straight-ahead patterns that are a favorite of the Saints, the Seahawks' opponent Saturday.
Former Seahawks quarterback Warren Moon said the only way to combat the grabby defensive backs is by running plenty of slant-and-go routes and other patterns that involve receivers making cuts. The idea is to get the defense's big cornerbacks on the move and hamper their ability to get their hands on a receiver.
Waiting for the officials to save you isn't a strategy. "If you think they're going to be called and expect that to be the solution to the problem, you're going to be sadly mistaken," said former Giants offensive coordinator Kevin Gilbride, who said the Seahawks' persistent interference happens on nearly every play. "They've perfected the art."
Write to Kevin Clark at email@example.com and Jonathan Clegg at firstname.lastname@example.com
- 19


text:
NEW MARTINSVILLE When you are trying to come up with a defense to stop a 2,000-yard passer, as a coach you almost have to assume that trying to contain that player may be the best way to go because stopping him may not be an option.
Magnolia head coach Mark Batton and defensive coordinator Bob Ripley had no such thoughts when they went to work on putting a game-plan together to try and stop Steubenville Catholic Central junior quarterback Brenton Colabella. All that they could hope for was that the defense go out and do their respective jobs.
They did everything they set out to do against the gun-slinging Colabella, and then some.
Article Photos
Art Limann
TOUGH NIGHT — Catholic Central quarterback Brenton Colabella goes back to pass during Friday's 35-0 loss at Magnolia.
Magnolia limited the Crusaders to just 39 total yards of offense, including just 61 through the air for Colabella, while the Blue Eagles rolled up 426 stripes on offense in cruising to a very impressive, and very important, 35-0 victory over Catholic Central on Senior Night at Alumni Field.
The victory sends Batton's squad into the regular season finale next week at Oak Glen with an 8-1 record and also all but wraps up at least a first-round home playoff game in Wetzel County. Meanwhile, Coach Steve Daley's Crusaders fell to 6-4 and finisn as the No. 8 seed in Ohio Division VI, Region 21, and brings with it a date with top-ranked Mogadore next week.
"Wow, did Coach Ripley come up with a great game-plan and the kids executed it to perfection," a smiling Batton said. "We had kids coming at them from every direction and when they got there they were able to make tackles.
Fact Box
Magnolia 35, Steubenville Central 0
Steubenville Central 0 0 0 0 - 0
Magnolia 7 14 7 7 - 35
M: Keller 11 run (Raitmayr kick)
M: Hanna 1 run (Raitmayr kick)
M: Keller 66 pass from Hanna (Raitmayr kick)
M: Ritz 15 pass from Hanna (Raitmayr kick),
M: Rohde 10 run (Raitmayr kick)
RUSHING: Steubenville Central 19-(-22) ( Colabella 10-(-30), Potenzini 1-1, Romano 2-1, Murphy 3-5, Parise 3-1). Magnolia 46-199-3 (Keller 18-78-td, Rohde 17-90-td, Hanna 7-26-td, Rogalski 1-0, Anderson 3-5).
PASSING: Steubenville Central 9-16-61 (all by Colabella). Magnolia 13-22-227-2 (all by Hanna).
RECEIVING: Steubenville Central 9-61 (Laukert 1-5, Romano 1-(-4), Herrington 2-38, Fletcher 3-8, Carapellotti 1-7, Murphy 1-6). Magnolia 13-227-2 (Keller 6-130, Rogalski 4-57, Deem 1-13, Rohde 1-12, Ritz 1-15-td).
FIRST DOWNS: Steubenville Central 2; Magnolia 20.
PENALTIES: Steubenville Central 5-44; Magnolia 7-92.
FUMBLES: Steubenville Central 2-2; Magnolia 3-2.
"This is a big win for us with a lot of points as far as the playoffs go. And Steubenville Central and coach Daley have an excellent program and we wish them nothing but the best."
Early on it looked like the Blue Eagles were really going to start racking up the points, driving all the way to the Catholic Central one to open the contest before fumbling and then taking over following a 13-yard put at the enemy 15 a short time later.
However, that short drive ended on a missed 33-yard field goal attempt by Clemens Raitmayr.
But when Magnolia really got the offense going the Eagles started putting up points while the Crusaders was having major difficulty just getting a first down.
The hosts finally found the end zone with just three minutes showing in the opening frame. It came after the first of four first half sacks of Central junior quarterback Brenton Colabella, with Big Blue setting up shop at the 17. Just three plays later Keller took a delay up-the-middle, bolted to the outside and found pay dirt from 11 yards out for a 7-0 lead.
Another short punt led to Magnolia's second score, this time coming at 9:48 in the half with quarterback Tanner Hanna darting through the line from one-yard away to make it 14-0.
Daley's crew managed to drive the ball into Blue Eagles' territory midway through the second, picking up their first and only stick-mover of the half along the way, however, on fourth-and-four from the 30, Colabella was again sack and the ball changed hands on downs.
This time Hanna got the job done through the air, without the help of senior do-it-all Stephen Rogalski, as Keller took a screen pass, broke through a pair of tackles near midfield and completed a 66-yard pitch-and-catch for the score at 5:02. It provided a 21-0 score that stood to the half.
After recovering a fumble on the second half kickoff, the Blue Eagles all but put things away with a nearly five minute drive that culminated with a 15-yard quick-hitter from Hanna to freshman tight end Kyle Ritz to push the margin to 28-0.
Kage Rohde, who played an outstanding game on both sides of the ball, made it a 35-0 margin when he ran in from 10 yards away early in the final period.
With senior standout Doug Maslowski missing in the backfield due to an injury, Colabella was chased all night long, sacked a total of six times and had very little time to get anything going.
"Doug (Maslowski) is a big part of our offense and we missed him (Friday)," Daley admitted. "Hopefully he will be cleared by the doctors to play next week. It is tough to try and piece things together when you are missing a player like that, especially against a very good team.
"We knew we were going to have to rely on the passing game, but our line didn't do a very good job in protection and Magnolia put a ton of pressure on us."


text:
I just had an interview, and I was asked to create a memory leak with Java. Needless to say I felt pretty dumb having no clue on how to even start creating one.
What would an example be?
We started with Q&A. Technical documentation is next, and we need your help.
Whether you're a beginner or an experienced developer, you can contribute.
I just had an interview, and I was asked to create a memory leak with Java. Needless to say I felt pretty dumb having no clue on how to even start creating one.
What would an example be?
Here's a good way to create a true memory leak (objects inaccessible by running code but still stored in memory) in pure Java:
This works because the ThreadLocal keeps a reference to the object, which keeps a reference to its Class, which in turn keeps a reference to its ClassLoader. The ClassLoader, in turn, keeps a reference to all the Classes it has loaded. It gets worse because in many JVM implementations Classes and ClassLoaders are allocated straight into permgen and are never GC'd at all.
A variation on this pattern is why application containers (like Tomcat) can leak memory like a sieve if you frequently redeploy applications that happen to use ThreadLocals in any way. (Since the application container uses Threads as described, and each time you redeploy the application a new ClassLoader is used.)
Update: Since lots of people keep asking for it, here's some example code that shows this behavior in action.
Static field holding object reference [esp final field]
(Unclosed) open streams ( file , network etc... )
Unclosed connections
Areas that are unreachable from JVM's garbage collector, such as memory allocated through native methods
In web applications, some objects are stored in application scope until the application is explicitly stopped or removed.
Incorrect or inappropriate JVM options, such as the
See IBM jdk settings.
A simple thing to do is to use a HashSet with an incorrect (or non-existent)
If you want these bad keys/elements to hang around you can use a static field like
Below there will be a non-obvious case where Java leaks, besides the standard case of forgotten listeners, static references, bogus/modifiable keys in hashmaps, or just threads stuck without any chance to end their life-cycle.
I'll concentrate on threads to show the danger of unmanaged threads mostly, don't wish to even touch swing.
(I can add some more time wasters I have encountered upon request.)
Good luck and stay safe; leaks are evil!
The answer depends entirely on what the interviewer thought they were asking.
Is it possible in practice to make Java leak? Of course it is, and there are plenty of examples in the other answers.
But there are multiple meta-questions that may have been being asked?
I'm reading your meta-question as "What's an answer I could have used in this interview situation". And hence, I'm going to focus on interview skills instead of Java. I believe your more likely to repeat the situation of not knowing the answer to a question in an interview than you are to be in a place of needing to know how to make Java leak. So, hopefully, this will help.
One of the most important skills you can develop for interviewing is learning to actively listen to the questions and working with the interviewer to extract their intent. Not only does this let you answer their question the way they want, but also shows that you have some vital communication skills. And when it comes down to a choice between many equally talented developers, I'll hire the one who listens, thinks, and understands before they respond every time.
Most examples here are "too complex". They are edge cases. With these examples, the programmer made a mystake (like don't redifining equals/hashcode), or has been bitten by a corner case of the JVM/JAVA (load of class with static...). I think that's not the type of example an interviewer want or even the most common case.
But there are really simpler cases for memory leaks. The garbage collector only frees what is no longer referenced. We as Java developpers don't care about memory. We allocate it when needed and let it be freed automatically. Fine.
But any long-lived application tend to have shared state. It can be anything, statics, singletons... Often non-trivial applications tend to make complex objects graphs. Just forgetting to set a reference to null or more often forgetting to remove one object from a collection is enough to make a memory leak.
Of course all sort of listeners (like UI listeners), caches, or any long-lived shared state tend to produce memory leak if not properly handled. What shall be understood is that this is not a Java corner case, or a problem with the garbage collector. It is a design problem. We design that we add a listener to a long-lived object, but we don't remove the listener when no longer needed. We cache objects, but we have no strategy to remove them from the cache.
We maybe have a complex graph that store the previous state that is needed by a computation. But the previous state is itself linked to the state before and so on.
Like we have to close SQL connections or files. We need to set proper referenres to null and remove elements from the collection. We shall have proper caching strategies (maximum memory size, number of elements, or timers). All objects that allow a listener to be notified must provide both a addListener and removeListener method. And when these notifiers are no longer used, they must clear their listener list.
A memory leak is indeed truly possible and is perfectly predictible. No need for special language features or corner cases. Memory leaks are either an indicator that something is maybe missing or even of design problems.
The following is a pretty pointless example, if you do not understand JDBC. Or at least how JDBC expects a developer to close
The problem with the above is that the
In such an event where the
Even if the JDBC driver were to implement
The above scenario of encountering exceptions during object finalization is related to another other scenario that could possibly lead to a memory leak - object resurrection. Object resurrection is often done intentionally by creating a strong reference to the object from being finalized, from another object. When object resurrection is misused it will lead to a memory leak in combination with other sources of memory leaks.
There are plenty more examples that you can conjure up - like
Probably one of the simplest examples of a potential memory leak, and how to avoid it, is the implementation of ArrayList.remove(int):
If you were implementing it yourself, would you have thought to clear the array element that is no longer used (
Any time you keep references around to objects that you no longer need you have a memory leak. See Handling memory leaks in Java programs for examples of how memory leaks manifest themselves in Java and what you can do about it.
You are able to make memory leak with sun.misc.Unsafe class. In fact this service class is used in different standard classes (for example in java.nio classes). You can't create instance of this class directly, but you may use reflection to do that.
Code doesn't compile in Eclipse IDE - compile it using command
I can copy my answer from here: Easiest way to cause memory leak in Java?
"A memory leak, in computer science (or leakage, in this context), occurs when a computer program consumes memory but is unable to release it back to the operating system." (Wikipedia)
The easy answer is: You can't. Java does automatic memory management and will free resources that are not needed for you. You can't stop this from happening. It will ALWAYS be able to release the resources. In programs with manual memory management, this is different. You cann get some memory in C using malloc(). To free the memory, you need the pointer that malloc returned and call free() on it. But if you don't have the pointer anymore (overwritten, or lifetime exceeded), then you are unfortunately incapable of freeing this memory and thus you have a memory leak.
All the other answers so far are in my definition not really memory leaks. They all aim at filling the memory with pointless stuff real fast. But at any time you could still dereference the objects you created and thus freeing the memory --> NO LEAK. acconrad's answer comes pretty close though as I have to admit since his solution is effectively to just "crash" the garbage collector by forcing it in an endless loop).
The long answer is: You can get a memory leak by writing a library for Java using the JNI, which can have manual memory management and thus have memory leaks. If you call this library, your java process will leak memory. Or, you can have bugs in the JVM, so that the JVM looses memory. There are probably bugs in the JVM, there may even be some known ones since garbage collection is not that trivial, but then it's still a bug. By design this is not possible. You may be asking for some java code that is effected by such a bug. Sorry I don't know one and it might well not be a bug anymore in the next Java version anyway.
Here's a simple/sinister one via http://wiki.eclipse.org/Performance_Bloopers#String.substring.28.29.
Because the substring refers to the internal representation of the original, much longer string, the original stays in memory. Thus, as long as you have a StringLeaker in play, you have the whole original string in memory, too, even though you might think you're just holding on to a single-character string.
The way to avoid storing an unwanted reference to the original string is to do something like this:
For added badness, you might also
Doing so will keep both the original long string and the derived substring in memory even after the StringLeaker instance has been discarded.
Take any web application running in any servlet container (Tomcat, Jetty, Glassfish, whatever...). Redeploy the app 10 or 20 times in a row (it may be enough to simply touch the WAR in the server's autodeploy directory.
Unless anybody has actually tested this, chances are high that you'll get an OutOfMemoryError after a couple of redeployments, because the application did not take care to clean up after itself. You may even find a bug in your server with this test.
The problem is, the lifetime of the container is longer than the lifetime of your application. You have to make sure that all references the container might have to objects or classes of your application can be garbage collected.
If there is just one reference surviving the undeployment of your web app, the corresponding classloader and by consequence all classes of your web app cannot be garbage collected.
Threads started by your application, ThreadLocal variables, logging appenders are some of the usual suspects to cause classloader leaks.
A common example of this in GUI code is when creating a widget/component and adding a listener to some static/application scoped object and then not removing the listener when the widget is destroyed. Not only do you get a memory leak, but also a performance hit as when whatever you are listening to fires events, all your old listeners are called too.
Maybe by using external native code through JNI?
With pure Java, it is almost impossible.
But that is about a "standard" type of memory leak, when you cannot access the memory anymore, but it is still owned by the application. You can instead keep references to unused objects, or open streams without closing them afterwards.
I recently encountered a memory leak situation caused in a way by log4j.
Log4j has this mechanism called Nested Diagnostic Context(NDC) which is an instrument to distinguish interleaved log output from different sources. The granularity at which NDC works is threads, so it distinguishes log outputs from different threads separately.
In order to store thread specific tags, log4j's NDC class uses a Hashtable which is keyed by the Thread object itself (as opposed to say the thread id), and thus till the NDC tag stays in memory all the objects that hang off of the thread object also stay in memory. In our web application we use NDC to tag logoutputs with a request id to distinguish logs from a single request separately. The container that associates the NDC tag with a thread, also removes it while returning the response from a request. The problem occurred when during the course of processing a request, a child thread was spawned, something like the following code:
So an NDC context was associated with inline thread that was spawned. The thread object that was the key for this NDC context, is the inline thread which has the hugeList object hanging off of it. Hence even after the thread finished doing what it was doing, the reference to the hugeList was kept alive by the NDC context Hastable, thus causing a memory leak.
Create a static Map and keep adding hard references to it. Those will never be GC'd.
I have had a nice "memory leak" in relation to PermGen and XML parsing once. The XML parser we used (I can't remember which one it was) did a String.intern() on tag names, to make comparison faster. One of our customers had the great idea to store data values not in XML attributes or text, but as tagnames, so we had a document like:
In fact, they did not use numbers but longer textual IDs (around 20 characters), which were unique and came in at a rate of 10-15 million a day. That makes 200 MB of rubbish a day, which is never needed again, and never GCed (since it is in PermGen). We had permgen set to 512 MB, so it took around two days for the out-of-memory exception (OOME) to arrive...
I thought it was interesting that no one used the internal class examples. If you have an internal class; it inherently maintains a reference to the containing class. Of course it is not technically a memory leak because Java WILL eventually clean it up; but this can cause classes to hang around longer than anticipated.
Now if you call Example1 and get an Example2 discarding Example1, you will inherently still have a link to an Example1 object.
I've also heard a rumor that if you have a variable that exists for longer than a specific amount of time; Java assumes that it will always exist and will actually never try to clean it up if cannot be reached in code anymore. But that is completely unverified.
As a lot of people have suggested, Resource Leaks are fairly easy to cause - like the JDBC examples. Actual Memory leaks are a bit harder - especially if you aren't relying on broken bits of the JVM to do it for you...
The ideas of creating objects that have a very large footprint and then not being able to access them aren't real memory leaks either. If nothing can access it then it will be garbage collected, and if something can access it then it's not a leak...
One way that used to work though - and I don't know if it still does - is to have a three-deep circular chain. As in Object A has a reference to Object B, Object B has a reference to Object C and Object C has a reference to Object A. The GC was clever enough to know that a two deep chain - as in A <--> B - can safely be collected if A and B aren't accessible by anything else, but couldn't handle the three-way chain...
You can create a moving memory leak by creating a new instance of a class in that class's finalize method. Bonus points if the finalizer creates multiple instances. Here's a simple program that leaks the entire heap in sometime between a few seconds and a few minutes depending on your heap size:
I came across a more subtle kind of resource leak recently. We open resources via class loader's getResourceAsStream and it happened that the input stream handles were not closed.
Uhm, you might say, what an idiot.
Well, what makes this interesting is: this way, you can leak heap memory of the underlying process, rather than from JVM's heap.
All you need is a jar file with a file inside which will be referenced from Java code. The bigger the jar file, the quicker memory gets allocated.
You can easily create such a jar with the following class:
Just paste into a file named BigJarCreator.java, compile and run it from command line:
Et voilà: you find a jar archive in your current working directory with two files inside.
Let's create a second class:
This class basically does nothing, but create unreferenced InputStream objects. Those objects will be garbage collected immediately and thus, do not contribute to heap size. It is important for our example to load an existing resource from a jar file, and size does matter here!
If you're doubtful, try to compile and start the class above, but make sure to chose a decent heap size (2 MB):
You will not encounter an OOM error here, as no references are kept, the application will keep running no matter how large you chose ITERATIONS in the above example. The memory consumption of your process (visible in top (RES/RSS) or process explorer) grows unless the application gets to the wait command. In the setup above, it will allocate around 150 MB in memory.
If you want the application to play safe, close the input stream right where it's created:
and your process will not exceed 35 MB, independent of the iteration count.
Quite simple and surprising.
What's a memory leak:
Typical example:
A cache of objects is a good starting point to mess things up.
Your cache grows and grows. And pretty soon the entire database gets sucked into memory. A better design uses an LRUMap (Only keeps recently used objects in cache).
Sure, you can make things a lot more complicated:
What often happens:
If this Info object has references to other objects, which again have references to other objects. In a way you could also consider this to be some kind of memory leak, (caused by bad design).
I don't think anyone has said this yet: you can resurrect an object by overriding the finalize() method such that finalize() stores a reference of this somewhere. The garbage collector will only be called once on the object so after that the object will never destroyed.
Everyone always forgets the native code route. Here's a simple formula for a leak:
Remember, memory allocations in native code come from the JVM heap.
Threads are not collected until they terminate. They serve as roots of garbage collection. They are one of the few objects that won't be reclaimed simply by forgetting about them or clearing references to them.
Consider: the basic pattern to terminate a worker thread is to set some condition variable seen by the thread. The thread can check the variable periodically and use that as a signal to terminate. If the variable is not declared
If you only have a handful of threads these bugs will probably be obvious because your program will stop working properly. If you have a thread pool that creates more threads as needed, then the obsolete/stuck threads might not be noticed, and will accumulate indefinitely, causing a memory leak. Threads are likely to use other data in your application, so will also prevent anything they directly reference from ever being collected.
As a toy example:
there are many different situations memory will leak. One i encountered, which expose a map that should not be exposed and used in other place.
I think that a valid example could be using ThreadLocal variables in an environment where threads are pooled.
For instance, using ThreadLocal variables in Servlets to communicate with other web components, having the threads being created by the container and maintaining the idle ones in a pool. ThreadLocal variables, if not correctly cleaned up, will live there until, possibly, the same web component overwrites their values.
Of course, once identified, the problem can be solved easily.
The interviewer might have be looking for a circular reference solution:
This is a classic problem with reference counting garbage collectors. You would then politely explain that JVMs use a much more sophisticated algorithm that doesn't have this limitation.
-Wes Tarle
An example I recently fixed is creating new GC and Image objects, but forgetting to call dispose() method.
GC javadoc snippet:
Image javadoc snippet:
Thank you for your interest in this question.
Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).
Would you like to answer one of these unanswered questions instead?


text:
I define $X_i$ as a random variable that is uniformly distributed between (0,1). What is the expected number of such variables I require to make the sum go just higher than 1. Thanks
I asked a related question in MathOverflow a while back. Here is the link. Let $N$ be the number of $U(0,1)$ random variables needed for the sum to cross $1$. It is in fact possible to derive the pmf of $N$ and compute $E(N)$ as David Bar Moshe has indicated. But there is a nifty derivation if we are only interested in $E(N)$ that involves conditioning on the very first random variable $U_1$ that we pick. I have sketched an outline below. Let me know if any part of the derivation isn't clear.
Let $N(x)$ be expected number of $U(0,1)$ random variables needed for the sum to cross $x$ where $0 \leq x \leq 1$. Then, a recursion can be derived for $f(x) = E(N(x))$ as
$f(x) = \int_{0}^{1} E(N(x) \mid U_1 = y) dy$.
This integral naturally splits into two - that between $0$ and $x$ and that between $x$ and $1$. If $U_1 < x$, $E(N(x))$ is simply $1 + f(x-U_1)$. If $U_1 > x$, $E(N(x))$ is just $1$. This will give us an integral equation for $f(x)$ that can be solved to get the solution (with suitable initial condition) as $f(x) = e^x$.
This problem is well-known. For an answer, see, for example, the first part of Section 2 in http://myweb.facstaff.wwu.edu/curgus/Papers/27Unexpected.pdf, or Equations (7)-(10) in http://mathworld.wolfram.com/UniformSumDistribution.html
I don't know the exact value, but by Wald's equation it is between 2 and 4.
Edit: Let $N$ be the number of terms required. $N$ is a stopping time for the sequence $X_1, X_2, \dots$, so Wald's equation gives us $$E[X_1 + \dots + X_N] = E[N] E[X_1].$$ We have $E[X_1] = 1/2$, and $1 \le X_1 + \dots + X_N \le 2$, so rearranging gives us $2 \le E[N] \le 4$.


text:
Conditions of the Newborn (Martin, et al., 2002):
Anemia: hemoglobin level of less than 13.0 g/dL or a
hemocrit of less than 39 percent.
Injury: impairment of the
body function or structure due to adverse influences which
occurred at birth.
Fetal Alcohol Syndrome: a syndrome of altered perinatal growth and development
occurring in infants born of women who consumed excessive
amounts of alcohol during pregnancy.
Membrane Disease/RDS: a
disorder primarily of prematurity, manifested clinically by
respiratory distress and pathologically by pulmonary hyaline
membranes and incomplete expansion of the lungs at birth.
Aspiration Syndrome:
aspiration of meconium by the fetus or newborn affecting
the lower respiratory system.
Ventilation: a
mechanical method of assisting respiration for newborns with
respiratory failure.
Seizures: a seizure of any etiology.
Score: a summary measure
of an infant's clinical condition based on heart rate, respiratory
effort, muscle tone, reflex irritability, and color taken
at one and five minutes after delivery.
Each of the factors is given a score of 0, 1, or 2;
the sum of these five values is the Apgar score which can
range from 0 to 10. A
score of 10 is optimal and a low score (usually considered
to be less than 7) is considered an indication of potential
health problems and raises concerns about the subsequent health
and survival of the infant.
Weight: the first weight of
the fetus or newborn obtained after delivery.
Birth weight is recorded in grams.
of Labor and/or Delivery (Martin, et al., 2002):
Febrile: a fever greater than 100 degrees F or 38 C occurring
during labor and/or delivery.
or Heavy Meconium: meconium
consists of undigested debris from swallowed amniotic fluid,
various products of secretion, excretion, and shedding by
the gastrointestinal tract; moderate to heavy amounts of meconium
in the amniotic fluid noted during labor and/or delivery.
Rupture of Membranes (more than 12 hours):
rupture of the membranes at any time during pregnancy and more
than 12 hours before the onset of labor.
Placenta: premature separation
of a normally implanted placenta from the uterus.
Previa: implantation of the
placenta over or near the internal opening of the cervix.
Excessive Bleeding: the
loss of a significant amount of blood from conditions other
than abruptio placenta or placenta previa.
[An EBC software cross-edit does not allow this complication
to be selected unless blood loss greater than or equal to
750 cc for vaginal deliveries and 1,200 cc for cesarean deliveries
is entered.]
Seizures During Labor: maternal seizures occurring during labor from
any cause.
Labor (less than 3 hours):
extremely rapid labor and delivery lasting less then
3 hours.
Labor (more than 20 hours):
abnormally slow progress of labor lasting more than
20 hours.
Labor: failure to progress
in a normal pattern of labor.
at birth, the presentation
of the fetal buttocks rather than the head, or other malpresentation.
Disproportion: the relationship of the size, presentation, and
position of the fetal head to the maternal pelvis which prevents
dilation of the cervix and/or descent of the fetal head.
Prolapse: premature expulsion
of the umbilical cord in labor before the fetus is delivered.
Anesthetic Complications: any complication during labor and/or delivery
brought on by an anesthetic agent or agents.
Distress: signs indicating fetal
hypoxia (deficiency in amount of oxygen reaching fetal tissues).
Anomalies of the Child (Martin, et al., 2002):
Nervous System Anomaly:
includes anencephalus, spina bifida/meningocele, hydrocephalus,
microcephalus, or other anomaly of the brain, spinal cord,
or nervous system.
Malformation: congenital
anomaly of the heart.
Circulatory/Respiratory Anomaly: other specified anomalies of the circulatory
or respiratory systems.
Anomaly: includes rectal atresia/stenosis,
tracheo-esophageal fistula/esophageal atresia, omphalocele/gastroschisis,
or other anomaly of the gastrointestinal system.
Anomaly: includes malformed
genitalia, renal agenesis, or other anomaly of the organs
concerned in the production and excretion of urine, together
with organs of reproduction.
Lip/Palate: cleft lip is a fissure or elongated opening of
the lip; cleft palate is a fissure in the roof of the mouth.
Polydactyly/Syndactyly/Adactyly: polydactyly is the presence of more than five
digits on either hands and/or feet; syndactyly is having fused
or webbed fingers and/or toes; adactyly is the absence of
fingers and/or toes.
Foot: deformities of the foot,
which is twisted out of shape or position.
Musculoskeletal/Integumental Anomaly: includes diaphragmatic hernia or other anomaly
of the muscles, skeleton, or skin.
Syndrome: the most common chromosomal
defect with most cases resulting from an extra chromosome.
Chromosomal Anomaly: any other chromosomal aberration.
Birth: the complete expulsion
or extraction from its mother of a product of conception,
irrespective of the duration of pregnancy, which, after such
separation, breathes or shows any evidence of life, such as
beating of the heart, pulsation of the umbilical cord, or
definite movement of voluntary muscles.
Birth Weight: birth
weight of less than 2,500 grams or approximately 5 pounds,
8 ounces. Prior to
1989, New Jersey defined low birth weight as 2,500 grams or
Status: the marital status
of the mother for statistical purposes is determined for
years after 1988 by the response to the birth certificate
item, "Mother married? (At birth, conception, or any time between)".
Risk Factors for This Pregnancy (Martin, et al., 2002):
Anemia: hemoglobin level of less than 10.0 g/dL during
pregnancy or a hematocrit of less than 30 percent during pregnancy.
Disease: disease of the heart.
or Chronic Lung Disease:
disease of the lungs during pregnancy.
metabolic disorder characterized
by excessive discharge of urine and persistent thirst; includes
juvenile onset, adult onset, and gestational diabetes during
Herpes: infection of the skin
of the genital area by herpes simplex virus.
Hydramnios/Oligohydramnios: any noticeable excess (hydramnios) or lack (oligohydramnios)
of amniotic fluid.
a blood disorder caused
by alteration in the genetically determined molecular structure
of hemoglobin (example: sickle
cell anemia).
Hypertension: blood
pressure persistently greater than 140/90, diagnosed prior
to onset of pregnancy or before the 20th week of gestation.
Hypertension: an
increase in blood pressure of at least 30mm Hg systolic or
15mm Hg diastolic on two measurements taken 6 hours apart
after the 20th week of gestation.
Eclampsia: the occurrence of convulsions and/or coma unrelated
to other cerebral conditions in women with signs and symptoms
of preeclampsia.
Cervix: characterized by painless
dilation of the cervix in the second trimester or early in
the third trimester of pregnancy, with premature expulsion
of membranes through the cervix and ballooning of the membranes
into the vagina, followed by rupture of the membranes and
subsequent expulsion of the fetus.
Infant 4,000+ Grams: the
birth weight of a previous live-born child was over 4,000
grams (8 pounds, 14 ounces).
Preterm or Small-for-Gestational Age Infant: previous birth of an infant prior to term (before
37 completed weeks of gestation) or of an infant weighing
less than the tenth percentile for gestational age using a
standard weight-for-age chart.
Disease: kidney disease.
Sensitization: the process or state of becoming sensitized to
the Rh factor as when an Rh-negative woman is pregnant with
an Rh-positive fetus.
Bleeding: any clinically significant bleeding during the
pregnancy taking into consideration the stage of pregnancy;
any second or third trimester bleeding of the uterus prior
to the onset of labor.
Births: individual
births in twin, triplet, quadruplet, and higher order multiple
Procedures (Martin, et al., 2002):
Amniocentesis: surgical transabdominal perforation of the uterus
to obtain amniotic fluid to be used in the detection of genetic
disorders, fetal abnormalities, and fetal lung maturity.
Fetal Monitoring: monitoring with external devices applied to the
maternal abdomen or with internal devices with an electrode
attached to the fetal scalp and a catheter through the cervix
into the uterus, to detect and record fetal heart tones and
uterine contractions.
of Labor: the initiation of uterine
contractions before the spontaneous onset of labor by medical
and/or surgical means for the purpose of delivery.
of Labor: augmentation of previously
established labor by use of oxytocin.
Tocolysis: use of medications to inhibit preterm uterine
contractions to extend the length of pregnancy and, therefore,
avoid a preterm birth.
Ultrasound: visualization of the fetus and the placenta
by means of sound waves.
Plurality: singleton, twin, triplet, quadruplet, etc.
Pregnancy Terminations:
from the mother's pregnancy history on the certificate
of live birth, a previous spontaneous or induced termination
of pregnancy at any time after conception that did not result
in a live birth.
Birth: birth
to a mother under 20 years of age.
Alcohol, and Drug Use during Pregnancy: use of these substances self-reported by mother.
of Pregnancy: the first trimester includes the first 12 weeks
of pregnancy, the second trimester encompasses the thirteenth
through twenty-fourth weeks and the third trimester is the
period after the twenty-fourth week through delivery.
Low Birth Weight: birth
weight of less than 1,500 grams or approximately 3 pounds,
5 ounces.
of Death Classification:
a system of specification of the diseases and/or injuries
which led to death and the sequential order of their occurrence. The version of the system in use in 2001 was
the International Statistical
Classification of Diseases and Related Health Problems, Tenth
Revision, sponsored by the World Health Organization. Beginning with 2001 data, codes were added for deaths due to terrorism (U01-U03). Deaths coded U01-U02 are grouped under homicides and those coded U03 are grouped under suicide.
a number used to measure the effect of changes in classification
and coding rules between revisions of the International Classification
of Diseases (ICD). Comparability
ratios less than 1.0 result from fewer deaths being classified
to cause x under ICD-10 compared with the comparable cause under
ICD-9. Ratios greater
than 1.0 result from more deaths being classified to cause
x under ICD-10.
Preliminary comparability ratios used in this report
should not be used on data prior to 1994 and caution should
be exercised when applying the ratios to age-, race-, or sex-specific
Death: death prior to the
complete expulsion or extraction from its mother of a product
of conception; the fetus shows no signs of life such as breathing
or beating of the heart, pulsation of the umbilical cord,
or definite movement of voluntary muscles.
Fetal deaths are also referred to as stillbirths, miscarriages,
or abortions.
Death: death within the first
year of life.
Death: a death in which the
certifying physician has designated a maternal condition as
the underlying cause of death.
In the Tenth Revision of the International
Statistical Classification of Diseases and Related Health
Problems, this includes only those deaths assigned to
causes related to or aggravated by pregnancy or pregnancy
management (ICD-10 codes O00-O95, O98-O99, and A34) and which
occur within 42 days after delivery or other termination of
Death: death of an infant within
the first 27 days of life.
Mortality: death
of an infant from 28 days to one year of life.
Cause of Death: the
disease or injury which initiated the train of events leading
directly to death or the circumstances of the unintentional
injury or violence which produced the fatal injury.
All cause-of-death data in this report relate to the
underlying cause of death coded from the death certificate.
of Potential Life Lost (YPLL): a measure of the number of years of life not
lived by each individual who died before reaching a predetermined
age. This measure weights deaths at younger ages
more heavily than deaths at older ages; the younger the age
at death, the greater the number of years of potential life
lost. The YPLL for a population is computed as the
sum of all the individual YPLL for individuals who died during
a specific time period. Prior
reports in this series contained tables of YPLL, but the
data are now available from CDC's WISQARS query system.
Stated: an inclusive term used
to represent data which are missing, unknown, not available,
or not classifiable.
The presentation of
vital statistics in the form of rates and ratios facilitates
comparisons between political subdivisions with populations
of different sizes or between subgroups of a population.
Crude rates are calculated by dividing the number of
events of a type that occur to the residents of an area (e.g.,
births, deaths) by the resident population of an area or subgroup.
The events are limited to those that occur within a
specific time period, usually a year, and the population is,
in general, the mid-year estimate of the resident population
of the area, although census counts as of April 1 may be used
in decennial census years.
Crude rates are expressed in terms of occurrences within
a standard, rounded population, usually 1,000 or 100,000.
In order to compare
birth and death experiences among various ages and races or
between the sexes, rates may be computed for subgroups of
the population. These are referred to as age-, race-, or sex-specific
rates and are calculated by dividing the relevant events within
a subgroup by the population in the subgroup.
Death rates from specific causes may also be calculated,
with the numerator consisting of the deaths from the particular
cause in an area and the denominator comprised of the population
at risk of the disease or condition.
The numbers of births
and deaths in an area are directly related to the demographic
characteristics of the area's population.
In comparing rates over time or among geographic areas,
it is helpful to eliminate the effects of the differences
in the populations' demographic characteristics on the comparison.
This can be accomplished through adjustments of the
rates for the particular characteristics of interest.
The most common type of adjustment of rates is for
age. Direct adjustment
of vital statistics rates involves application of existing
rates (age-, race-, or sex-specific) to a standard population
to arrive at the theoretical number of events that would
occur in the standard population, at the rates prevailing
in the actual population. These events are then divided by the total number
of persons in the standard population to arrive at an adjusted
rate. Adjusted rates are index numbers and cannot be compared
to crude or other actual rates.
The use of adjusted rates is limited to comparison
with other adjusted rates, based on the same standard population.
The standard population used in this report is the
United States 2000 standard million, derived from the projection
of counts from the 2000 decennial census. Reports in this series prior to 1999 used the
US 1940 standard million for age-adjustment.
The definition of rates
and ratios used in this report follows.
It should be noted that alternative forms exist for
some of these statistics.
Some other states and the federal government may employ
different formulae for the computation of selected rates.
Birth Rate: the number of resident live births per 1,000
Fertility Rate: the
number of resident live births per 1,000 females aged 15-44
Fertility Rate: age-specific
birth rates of women in five-year age groups multiplied by
five and summed to form a total for all ages.
This rate indicates the number of children a cohort
of 1,000 women would bear if they experienced the existing
age-specific birth rates throughout their childbearing years.
Birth Rate: the number of resident live births to females
in a specific age group per 1,000 females in the age group.
Death Rate: the
number of resident deaths per 100,000 population.
Death Rate: Direct
Method-the elimination of the effect of age on the crude death
rates for purposes of comparison with other rates by applying
actual age-specific rates to a standard population.
The resulting death rate in the standard population
is age-adjusted and can be compared to other death rates age-adjusted
to the same standard population.
Death Rate: the
number of resident deaths from a specific cause per 100,000
Death Rate: the number of resident deaths under one year
of age per 1,000 population.
Mortality Rate: the
ratio of the number of deaths to children less than one year
of age in a given year per 1,000 births in the same year.
Death Rate: the number of resident infant deaths within the
first 27 days of life per 1,000 live births.
Death Rate: the
number of resident infant deaths from 28 days to one year
of life per 1,000 live births.
Death Rate: the number of resident fetal deaths of 20 or
more weeks gestation per 1,000 resident live births plus fetal
deaths of 20 or more weeks of gestation.
Rate: the number of
marriage certificates issued in an area per 1,000 population.
Rate: the number of divorces
occurring in an area per 1,000 population.
should be exercised in the interpretation of rates and ratios
based on small numbers. Chance variations in the number of vital events
occurring in sparsely populated areas can cause rates to fluctuate
widely over time. In
accordance with National Center for Health Statistics (NCHS)
standards, percentages or rates based on fewer than 20 cases
are considered unreliable for analysis purposes.
Therefore, these percentages and rates are not displayed
and are indicated by ** in the appropriate cell.
For purposes of analyzing vital statistics rates for
small areas, calculation of three- or five-year average rates
and other statistical methodologies for analyzing small numbers
may provide more meaningful measures.
The cause-of-death rankings
found in this report are based on distinct causes of death
from the list of 31 cause groups and two residual categories
employed in the cause-of-death distributions by race-sex groups
and age and by county in the report.
This list is derived from the NCHS List of 113 Selected
Causes of Death (Arias, 2003) and modified for use in New
The cause-of-death ranking
of infant and fetal deaths is based on the NCHS List of 130
Selected Causes of Infant Death (Arias, 2003).
race group (White, Black, American Indian/Alaska Native, Chinese,
Japanese, Hawaiian, Filipino, Asian Indian, Korean, Samoan,
Vietnamese, Guamian, other Asian/Pacific Islander, other race,
and an unknown race category) and an ethnicity (Non-Hispanic,
Mexican, Puerto Rican, Cuban, Central or South American, other
Hispanic, and an unknown ethnicity category) are reported
for each individual for whom a birth, death, or fetal death
record is filed. The
race and ethnicity of an infant are not reported on the birth
or fetal death certificate and are classified for statistical
purposes as the race and ethnicity of the mother.
Race/ethnicity designations
used in the birth chapter of this report are white (non-Hispanic),
black (non-Hispanic), Hispanic, Asian/Pacific Islander (non-Hispanic),
and other (non-Hispanic) races.
The Hispanic category includes persons of Mexican,
Puerto Rican, Cuban, Central/South American, or other Hispanic
ethnicity, regardless of race. The Asian/Pacific Islander (non-Hispanic) category
includes persons of Chinese, Japanese, Hawaiian, Filipino,
Asian Indian, Korean, Samoan, Vietnamese, Guamian, and other
Asian and Pacific Islander descent who were not reported as
Hispanic. The other
(non-Hispanic) race category includes all race groups other
than white, black, and Asian/Pacific Islander who were not
reported as Hispanic.
Race and ethnicity classifications
are based on self-reports, or in the case of death records,
on reports from respondents, usually a family member, or from
persons responsible for preparing the death certificates.
Race and ethnicity reporting on birth and fetal death
certificates has been found to be virtually complete, therefore
birth, infant death, and fetal death data for Asian/Pacific
Islanders and Hispanics are presented. However, race reporting for races other than
white and black and reporting of Hispanic ethnicity on death
certificates is incomplete; therefore, data presented in the
body of the death chapter are only given for white and black
races, regardless of ethnicity. Persons who are identified as Hispanic have
been included in the analysis of mortality data by race based
on the race reported on the decedent's death certificate
in Tables M1-M42 and are reported
separately in Tables MH1-MH9.
Asians and Pacific Islanders are included in the other
race category in Tables M1-M42
and are reported separately in Tables
The birth chapter encompasses
births to New Jersey residents during the calendar year 2001. The birth certificate is the source document
for data included in the analysis.
New Jersey law requires that the attending physician,
midwife, or person acting as midwife file a certificate of
birth with the Local Registrar within five days of a birth
within the state. Statistics
on births to New Jersey residents which occurred in other
states are also included in this report.
The inclusion of these data is made possible through
the auspices of the Vital Statistics Cooperative Program,
which encourages the exchange of information on vital events
between the states of occurrence and residence.
In January of 1996,
the New Jersey Department of Health began
a pilot test of its electronic birth certificate (EBC) in
four maternity hospitals in the state.
Upon successful completion of this test, the EBC was
systematically installed in other New Jersey birthing facilities
over the next two years. By
the end of 1998, all New Jersey birthing facilities were reporting
births to the State through the EBC system.
Future reports in this series will benefit from the
improved quality and timeliness of the data afforded by the
EBC, as well as the enhanced array of perinatal data provided
through this system.
format of the birth certificate was revised and expanded in
1989. The position
of items on the revised birth certificate led to considerable
confusion between the reporting of a mother's mailing address
and her residence address. In 1998, the Center for Health Statistics completed
a multi-year project involving the application of address
standardization software to convert mailing-label type information
so that birth records could be accurately assigned to geographic
areas. With the resolution of this problem, it is once
again possible to display data at the municipality level.
The mortality information
contained in this report covers deaths of New Jersey residents
during the 2001 calendar year.
The report's source document is the death certificate. New Jersey law requires the prompt filing of
a death certificate by the proper authority, such as hospital
personnel, physicians, medical examiners, and funeral directors,
in the event of a death occurring in the state.
These certificates are submitted to the office of the
State Registrar, where they are recorded and filed permanently.
Statistics on deaths of New Jersey residents which
occurred in other states are obtained through participation
in the national Vital Statistics Cooperative Program.
Unless otherwise noted, the data presented in this
report are for New Jersey residents.
All of the causes of
deaths included in this report are underlying causes, and
were coded by the National Center for Health Statistics' SuperMICAR
and ACME software in accordance with the International
Statistical Classification of Diseases and Related Health
Problems, Tenth Revision, adapted for use in the United
States. Additional causes of death listed on the certificates,
including the immediate and intermediate causes, are not considered
in the analysis. The
inclusion of all listed causes of death (multiple causes of
death) could lead to somewhat different results.
mortality data are presented from the linked infant death-birth
match file which has death certificates for infants matched
with their birth certificates. This file allows analysis of maternal characteristics
and newborn health information that is not on the death certificate.
is important to note that in reports in this series prior
to the 1998 report, when infant mortality was reported by
race, it was the race of the child as reported on the death
certificate. Beginning
with this report, the race of the mother on the birth certificate
will be used. The race and ethnicity of an infant are not
reported on the birth certificate and are classified for statistical
purposes as the race and ethnicity of the mother.
By analyzing infant deaths based on the mother's race
and ethnicity, the data will be comparable with the birth
data used for denominators in calculating infant mortality
rates. This also allows
the analysis of infant deaths by Hispanic ethnicity which
was not done prior to the 1998 data year due to poor ethnicity
reporting on the death certificate.
Fetal deaths occurring
after the completion of 20 or more weeks of gestation are
required to be reported to the State Registrar by New Jersey
law. Induced abortions of 20 weeks or more gestation
are encompassed by this requirement, but are not included
in the fetal death count.
Fetal death figures presented in this report, therefore,
include only spontaneous abortions beyond 19 weeks of gestation.
Fetal deaths of unknown or unstated gestational age
are also included. Only
fetal deaths occurring to females who were New Jersey residents
are included.
on marriages in this report was obtained from marriage certificates
issued in New Jersey. Marriage
certificates are filed with the State Registrar. Divorce and annulment statistics were provided
by the New Jersey Administrative Office of the Courts, Family
Division. Marriages
are recorded by the place of issuance of the certificate and
divorces and annulments are recorded by place of judgment.
Since no mechanism for interstate exchange of resident
marriage and divorce data exists, marriages, divorces, and
annulments of New Jersey residents which occur outside of
the state are not included in this report, while marriages
and divorces of out-of-state residents occurring in New Jersey
are included.
The birth, death, fetal
death, and marriage data presented in this report were generated
from data files available at the time of preparation of the
respective chapters. Any
data pertaining to a vital event for which a certificate was
filed after that time or relating to corrections or revisions
made since the data were processed for this report are not
included. Vital events
computer files are periodically updated by Bureau of Vital
Statistics and Center for Health Statistics staff based on
correction reports received from local registrars and from
quarterly data quality control analyses conducted by the Center
for Health Statistics. This
report incorporates data from the most recently updated files. Thus, 2001 data presented in future reports
of vital events may differ slightly from numbers presented
in this report.
Population estimates presented in this
report and used to calculate various rates were derived from
the "Bridged-race Vintage 2002 postcensal population estimates" file prepared by the National Center for Health Statistics
in collaboration with the U.S.
Bureau of the Census.
These estimates result from bridging
the 31 race categories used in the 2000 Census, as specified
in the 1997 federal OMB
standards for the collection of data on race and ethnicity,
to the four race categories specified under the 1977 standards.
Many data systems, such as vital statistics, are continuing
to use the 1977 standards during the transition to full implementation
of the 1997 standards. Estimates were developed for each state and
its counties by age, race, Hispanic ethnicity, and
sex categories. The
current set of estimates presented in this report has not
been rounded. However, it should not be presumed that they
have the degree of accuracy which such precise figures might
imply. NCHS does not consider these estimates to be
accurate for each individual cell and recommends aggregating
the individual cells to larger groups when the data are used
for purposes of analysis. Estimates are distributed by five-year age groups,
sex, four race groups (White, Black, American Indian and Alaska
Native, and Asian and Pacific Islander), and Hispanic ethnicity
for the state and each county (Tables
P1-P22). Hispanics may be of any race and are already
included in the race groups in each table.
Population estimates are given for municipalities with
40,000 or more residents in 2001 (Table
P23). These are the municipalities listed in the birth
and death chapters of this report.
The reporting of births
and deaths is considered to be essentially complete. According to NCHS, more than 99 percent of births
and deaths are registered.
Reporting of fetal deaths is believed to be somewhat
less complete. For later periods of gestation, however, fetal
death reporting is thought to be more complete (NCHS, 1994). The completeness of reporting by residence is
dependent on the effective functioning of the interstate data
exchange program for certificates which is fostered and encouraged
by NCHS. Research has shown that there is some degree
of slippage in receiving information on all births and deaths
of New Jersey residents occurring in other states.
However, the number of missing events is thought to
be small, relative to the overall number of events.
The quality of the birth,
death, and fetal death data included in this report is a function
of the accuracy and completeness of the information recorded
on the respective certificates and of the quality control
procedures employed in the coding and keying processes.
A query program in which the individual(s) responsible
for completing the certificate is questioned about missing
or conflicting information is carried out by staff of the
Bureau of Vital Statistics of the New Jersey Department of Health.
This process is augmented by the data quality control
analyses performed by the Center for Health Statistics using
all of the NCHS edit criteria.
In order to participate
in the national Vital Statistics Cooperative Program, states
had to achieve an error rate of two percent or less on each
certificate item for three consecutive months.
The error rates relate to both coding and data entry
errors. New Jersey
has met the error tolerance requirements for the cooperative
program. After satisfying
initial requirements, a monthly sample of records is used
to determine that the error rate on each birth certificate
item is approximately four percent or less and is no more
than two percent for each death certificate item other than
the medical cause-of-death information.
Due to the complexity of the coding system, cause-of-death
coding has a five percent error tolerance level set by NCHS.
Multiple cause-of-death coding of New Jersey death
records is performed by NCHS staff.
For public health planning
and policy determination, the most useful population to study
is usually the resident population of an area.
In the case of births, deaths, and fetal deaths, the
existence of resident certificate exchange agreements among
the registration areas in the country permits analysis of
resident birth and death statistics. In this report, the data presented for births,
deaths, and fetal deaths represent vital events of the resident
population. Marriage
and divorce statistics in this report represent vital events
which occurred in New Jersey, regardless of the state of residence
of the individuals involved.
Allocation of vital
events by place of residence within the state is sometimes
difficult because classification depends on the statement
of the usual place of residence provided by the informant
at the time the certificate is completed. For a variety of reasons, the information given
may be incorrectly recorded.
A common source of error is the confusion of mailing
address with residence address. A major project to correctly allocate New Jersey
births by municipality of mother's residence has been completed. Since the 1998 report, selected birth data has
been presented for all municipalities with over 40,000 residents. The degree to which incorrect information on
municipality of residence has been recorded on death certificates
is not precisely known, but this issue is generally a problem
only for certain minor civil divisions.
Therefore, death data are only presented for municipalities
with over 40,000 residents and which are known to have a relatively
low level of uncertainty in allocation of municipality.
Return to Health Statistics 2001
department: njdhss
home | index by topic | programs/services
statewide: njhome | my
new jersey | people | business
| government | departments
| search
© State of New Jersey, 1996-2004
Department of Health
P. O. Box 360
Trenton, NJ 08625-0360
Last Updated:


text:
Stay involved in Music at Cal Poly!
Cal Poly students from any major can be involved in Cal Poly's music programs.
Explore our online brochure to find out what we have to offer
A print version is available from the Music Department office
- Cal Poly Symphony
- Mustang Band (marching/pep band)
- Percussion Ensemble
- University Jazz Bands
- Wind Orchestra
- Wind Ensembles
- Brass Ensembles
- String Ensembles
- Arab Music Ensemble
- Piano Ensemble
- Guitar Ensemble
- Saxophone Quartets
- Wind Quintets
- PolyPhonics
- University Singers
- Early Music Ensemble
- Cal Poly Vocal Jazz (not offered every year)
- Student Opera
Guitar Ensemble
The Cal Poly Guitar Ensemble is a group of classical guitarists whose focus is learning repertoire for performance. The repertoire is generally classical in nature, though other genres are sometimes included. Concerts consist of ensemble pieces as well as solo, duo and trio performances. Students must be able to read music on the guitar and be proficient in classic guitar technique "beyond a beginning level." For more information, please contact the guitar instructor Jim Bachman.
Percussion Ensemble
(not offered fall quarter)
The Cal Polyrhythms, Cal Poly's Percussion Ensemble, is dedicated to performing a wide range of percussion chamber music, from modern masterworks to the "classics" of the twentieth century. Comprised of music majors and non-music majors alike, the performers bring a diversity of experience to the group, but share in the common goal of committing themselves wholly to the music. The Cal Polyrhythms are known for their dynamic and thoughtful performances of some of the genre's most fascinating works. The director of the ensemble is Dr. John Astaire.
Brass Ensembles
The members of the Brass Ensembles include Cal Poly students from a variety of majors. Several groups comprise the ensembles, including two brass quintets and a brass choir. The Brass Ensembles perform concerts each quarter, and are also featured on the annual "A Night at the Mission" Chamber Ensemble Concert.
String Ensembles
Several string chamber groups are active each quarter through the String Ensembles program. These groups involve students from many majors on campus, and range from string trios, quartets and quintets to chamber groups that also include piano or wind instruments. These chamber ensembles perform on a yearly "Evening of String Music" recital as well as for school functions, professional engagements and student recitals.
The String Ensembles are coordinated by Dr. David Arrivée, conductor of the Cal Poly Symphony. Each group is coached by Dr. Arrivée and periodically by other faculty and outside artists including Kathleen Lenski and Michael Nowak. For more information on the String Ensembles, contact Dr. Arrivée.
Student Opera Theatre
Participation and registration of singers and instrumentalists by audition and the recommendation of the conductor, producer and musical directors. Auditions for roles in the annual spring quarter productions are held the end of fall quarter. The one-act operas are double cast to allow maximum participation, and are performed fully staged and directed in Cal Poly's Spanos Theatre, with costumes and orchestra. Operas recently performed include Mozart's "The Impresario" and Haydn's "The Apothecary." For more information, contact the directors: Jacalyn Kreitzer and Katherine Arthur.
Arab Music Ensemble
The Arab Music Ensemble performs the art and popular music of a wide range of Arabic-speaking societies while particularly focusing on the areas around the Eastern Mediterranean. Arab art music has intersected substantially with folk and religious musical traditions and has benefited deeply from the contributions of interconnected social groups including men and women of diverse ethnic, religious, and philosophical backgrounds. It also has connected historically to neighboring cultures of the larger region including those of Iranian (Persian) and Turkish (Ottoman) music. The repertoire of the Arab Music Ensemble comprises pieces ranging from the Ottoman era up to the present. The music is rooted in the traditional systems of melodic and metric modes (maqam and iqa` systems), and takes the form of instrumental improvisation (taqsim), vocal improvisation (layali and mawwal), and pre-composed works in many formal genres (e.g., dulab, sama`i and muwashshah). Students sing and perform instrumentally in a chamber music ensemble (takht) as well as in a larger orchestra (firqa). The traditional instruments employed include the `ud (lute), kamanja (violin), qanun (zither), nay (reed flute), riqq or daff (tambourine), darabukka or tabla (goblet drum), and others. Consistent with developments in composition and performance practice over the past century, the ensemble also employs instruments adapted from Euro-American traditions including the contrabass, violoncello, accordion, electric guitar, and drum set as well as Latin percussion, brass instruments, and others. Participation in the ensemble is open to all Cal Poly students and community members. Previous experience is not required. Performances include a formal concert at the end of each quarter and additional concerts in different configurations for other occasions.
For more information on the Arab Music Ensemble, contact Dr. Ken Habib.


text:
By ELIZABETH BINGHAM
Guest Writer
Shortly after turning 53, Judy Shaw looked in the mirror and saw a mother and wife who cared so deeply for others but, like so many caretakers, she'd neglected herself and it was starting to show in the way she carried herself.
Shaw had recently returned to the corporate world, a place she hadn't visited for nearly a decade. She knew her no-nonsense jeans and T-shirt look was outdated, but more than anything, she wanted to feel better. "I just wanted someone to please tell me what to do," she recalled.
After hearing Shaw's story, the talented stylists at Joseph's Salon & Spa and the ladies at Clodhoppers set out to make Judy over.
The Consultation
The makeover began at Joseph's, where hair was the first item on the agenda. During the consultation, Judy expressed how let down she'd been with her hair lately. From the ages of 17 to 35, she'd visited the same hairdresser because, as Shaw put it, "She just knew me." But her original hairdresser, now lived far away, and with little time to spare, Judy began settling for wherever she could get a haircut, which had contributed to her lackluster 'do.
Hair & Makeup
The professionals at Joseph's added a few highlights to match the lighter brown color of Shaw's brows and updated her short cut to make it more current.
Next was makeup, which seemed to be the biggest challenge. Shaw felt she lacked time for herself; this carried over into her makeup routine.
Before Judy reentered the business world, she had purchased all of her makeup products from a department store, where they were hand-selected specifically for her skin and preferences.
Over time, however, her busy working schedule didn't allow her the luxury to spend the time needed to be this selective with her makeup. Instead she usually found herself in the aisles of drugstores, hurriedly scanning the shelves and choosing whichever color or brand she found first.
At Joseph's, a makeup artist wiped off Shaw's thick, layered foundation, dark lip- and eyeliner, and rouge-colored cheeks. Then came the advice: less is more, particularly as we age, since women over 50 tend to have more wrinkles. Thick makeup can exacerbate the appearance of lines, which is why an Aveda tinted moisturizer was used instead of foundation as a base.
Shaw was used to wearing black or dark brown on the top lash line because she felt that it opened up her eyes. But, she learned, as we age, our eyes tend to narrow, so it's better to shy away from dark lining because it will actually give the eyes a sunken look rather than bring them out. Instead, Shaw was instructed to use a taupe and somewhat shimmery base all across the lid, a light brown in the crease, and a medium brown along the lash line. To top it off she used a dark brown mascara on both top and bottom lashes, waiting a minute or two between coats to avoid clumping.
A peachy, bronze blush was applied along her cheekbone and on the apples of her cheeks to give a sunny glow. Aveda lipstick in Cherrybud was applied to Shaw's lips and added the necessary finishing touch to her vibrant new look, making her look years younger.
With her hair and makeup finished, the next stop was Clodhoppers.
Shaw tried on numerous dresses at the St. Matthews boutique, finally deciding on a little black dress, a wardrobe must-have. The Clodhoppers staff added a pop of color by draping a blue pashmina around Shaw's shoulders and tying it in the back.
The Result
"I feel myself smiling just a little more," Shaw said days after the makeover. "As far as my daily routine goes, a little less time is spent worrying and fixing. And when I look at myself, I feel like I'm a little less hard on myself. I'm not so bad, after all!"
Photos By TONY BENNETT | Contributing Photographer


text:
3 Dec 2012 7:48 PM #1
- Join Date
- Oct 2012
- Location
- Brisbane, QLD, Australia
- Posts
- 50
- Vote Rating
- 14
Create your next TreeStore JSON data using FreeMind mind mapper
Creating JSON data for a TreeStore can be a thankless task. Don't you just love copy/pasting leaf: false ... err no! Well now you don't have to .
I've used FreeMind for a while as a cool mind mapping tool. The UI is very keystroke efficient for creating tree models and even most end user can wing it (right arrow creates a child node, ENTER creates a sibling node etc.). Being the nice open source project that it is, it saves it's data in XML and even provides numerous Export formats including an option to apply any XSLT script to the XML.
So I've just posted this GitHub project that includes the XSLT script you'll need to export JSON for your next TreeStore. The script is easy to customize. FreeMind supports many annotations that you could exploit in your TreeStore model just by tweaking the XSLT.
4 Dec 2012 8:48 AM #2
Looks very helpful. I will have to give this a try.


text:
The Complete Matrix Trilogy Blu Ray for $36.99
Box set includes:
The Matrix (BLU RAY)
The Matrix Reloaded (BLU RAY)
The Matrix Revolutions (BLU RAY)
DVD Description:
The Complete Matrix Trilogy features all three films in the trilogy together for the first time in mind-blowing high definition, with a newly re-mastered picture and sound for The Matrix.
For those who got burned by the Deepdiscount bogus deal (like me) before Christmas. Includes 4 discs of bonus features. Shipping is $2.59, so under $40 shipped seems pretty good.
15 Comments add a comment
I was burned by the deepdiscount deal but I still want the Ultimate Matrix Bluray collection for all the extra content. Good price on the trilogy but I'll pass.
Crap looks even more like crap in 1080P!
A region free, NTSC import from UK?? Has anyone heard of any legitimate blu-ray discs like this before (heck, even on DVD), or does this sound "suspicious" (read: "bootleg")?
I thought they only made one. :P
Saw this when WBShop failed to ship the one I ordered back on November 18th (they still haven't shipped it either), but held off from buying it here for not knowing if it is legit or the same thing as the Ultimate Matrix Collection on Blu-ray (including the discs with the bonus content).
Having looked at this more closely, I don't think this includes the all the bonus material that the Ultimate Matrix collection includes. Still not a bad deal if you don't care about all the extraneous stuff.
@nemo2005: "Still not a bad deal if you don't care about all the extraneous stuff."
The second and third movies?
I got this particular set used off of eBay (not realizing it was from the UK till I got it) and it plays just fine on my Samsung Blu-Ray player, but it does not come with any bonus discs, just the movies, though their may be bonus content on the discs themselves, not sure. Also, the case for each disc is a lot thicker and robust than the typical blu-ray case we see here in the states, it's basically a standard DVD case that's shorter and blue. It's a nice alternative to the Ultimate set if you want it a bit cheaper, or don't care about the bonus stuff.
Strange - I hit submit and it went to a page that said "not in here." WTF does that mean?
I got the confirmation in my email so it may go through still. Guess I will wait a week before filing any issues.
@marcoselmalo: Exactly
Might have to pick this up.
The first movie was great. The second movie was passable; it had interesting new characters and plot devices, but its value depended on how the threads were tied up in the third movie. Unfortunately the third movie was so awful I almost felt insulted by the Wachowski brothers.
Okay, nevermind, I talked myself out of it.
I have this set. It's the Euro collection.
It's region free and is only the 3 movies, where as the Ultimate Collection has the movies with The Animatrix and tons of bonus material.
A solid deal, this is about what I paid for mine.
How is this different from this one?
Looks like you can grab it used for $18 (with shipping).
Just bought this set on 1/18, got it Today 1/20! The Free shipping was FAST!!! Never tried Compuplus before, seems to be a good company. MUCH better then the SCAM ARTISTS at DEEPDISCOUNT. (Never again DD!!!)
Yes, this is the Euro version, SHOULD be region free...looks to be just 3 discs each with its own bonus materials. Not a bad deal.
FYI: No extra bonus disc of extras, No Animatrix. For a decent price you can have just the 3 movies on Blu-ray. Will pop it in my Sony player tonight and update on the Region Free...