text:
First Model S speeding ticket?
First Model S speeding ticket?
Less than 200 miles on the car... busted. 53 in a 35. The cop wouldn't listen to my pleading... and then after he wrote the ticket, he asks, "so can you go in the carpool lane with this?" I say, "NOW you want to talk about the car???? Bite me!
Was NOT happy.
A friend of mine took me for a ride on his P.. I asked him to show off the acceleration and before we knew it, he was doing a 95 on a 25 zone and then took a sharp curve at 70mph .. the car handled great.. but this car is surely likely to make you an aggressive driver.
Sorry to hear about the speeding tickets. I wish we had the software enhancement to warn you when u over 10mph over the speed limit.
Software enhancement would keep you from going 95 in a 25 zone??
@desiguy, it's standard equipment ... that big round gauge in the middle of the dash ;-)
I meant some audible cue :)
Agree more personal restraint is needed
Husband got a ticket for running a stop sign in our neighborhood the other day. He talked to the cop who talked him out of traffic school for the ticket. I said he should have done it as we are both surely going to get speeding ticket in our new MS! Might as well plan ahead!
Running a stop sign is going to be pretty common for those of us who never want to touch the brake petal.
You should have gotten out of the car with a confused look, and told the officer... "Something is seriously wrong!"... "I can't find the engine!!!!!"
By the time you both go looking, and can't find it, the officer will have forgotten why he pulled you over :-)
During the Get Amped tour in our city, the reps referred to them as "a souvenir "
I've been lucky. After 3.5 years of the Roadster and 4 months of a Model S, neither of us have received a ticket. We've both deserved tickets many times, but only once was I actually pulled over. He let me go with a warning that he didn't want to pick me up off of the pavement.
the car seriously needs an audible cue that you have hit a certain speed. This feature is on many cars. It is too easy to hit 90+ just passing a car or merging.
A day after a snow storm, and few days after I got my performace model S with the snow tires, I was pulled over by a nice cop, possibly for speeding 15-20 miles above speed limit. He followed me very closely for a mile or two trying to find out what kind of a car then pulled me over. I told him I was a doctor and on my way to the hospital, so he just gave me a warning and asked me how I like my new car.I told him I love it, he then asked me about the torque, I said it is phenomenal and thanked him!!
I suggest developing your own test drive route near your home and work, just like Tesla did. For the acceleration portion incorporate highway on ramps. I think it feels natural to punch it on an on ramp. You and your passengers' heads will fall back into the headrest. They will experience a slight "face lifting" from the G's, while their eyebrows lower with confusion when their brain realizes that they don't hear the engine or feel the transmission like they would expect. The brain may attempt to convince them that it didn't actually feel fast, but a quick view of the speedometer contradicts this. The curved on ramps really demonstrate the combination of acceleration and handing that no other car I've driven has had. They typically have open grass areas or at least guard rails rather then children or cars pulling out in case the unexpected were to occur. I've also never seen a cop staked out on an on ramp looking for speeders. I tell myself that there might be a jurisdiction issue between the local and state police that might cause a local cop to hesitate to pursue you on to the highway, I'm sure I'm probably just fooling myself on this one. Then after you are merging on to the highway at 65 (or 85) in just a few seconds and your passenger is still dealing with the G's, punch it again when the coast is clear to demonstrate that his baby has power at every speed. They will be blown away, you've got that Tesla grin and No ticket. You get off the next exit taking your foot off the one pedal you'll ever use to drive and they will experience the regen braking, but will be slow to understand. They are still trying to comprehend all the other attributes about this amazing car that are totally different than anything they have come to know about cars. This is as close to demonstrating fire to a caveman as you will get with any piece of technology you have ever owned. Then you go across the highway and do it again on the way back, but for fun. If you really want to take the experience up a notch, combine it with that sense you get with a random act of kindness and do it for that random person that just comes up to you at the grocery store parking lot who has only read about the MS and is totally juiced on the rumors and hearsay.
Be as careful with the off-ramp as you are with the on-ramp. I took my foot off the accelerator to demonstrate the regen, and it felt like I was about to come to a dead stop in the middle of the off-ramp. Had there been someone behind me, he would have been justifiably pissed.
I got my car yesterday. This afternoon I was heading home on the freeway, and this Accord starts tailing me through traffic, obviously checking out the car. We're in the left lane, crest a hill, and then the car in front of me suddenly changes lanes, at which point I see a cop on the left shoulder with a laser gun. I look in the rearview and see him pull out with lights on. I start to sweat while moving over a few lanes to the right, and keep looking back only to see the cop proceed to pull over the guy in the Accord. Lol!
PWNT! Now that's funny :)
Shouldn't tailgate buddy, even if its an awesome car you're following/admiring :D
Wonder if he managed to talk his way outta a ticket or not.
Picked the car up on Dec 12th, and was heading to Seattle on Christmas eve when I received my first speeding ticket in 8 years.....
A salient lesson for everybody that is about to get an S. I was doing 65 stuck behind a line of traffic (in 70 zone), when the line cleared, I floored it to get past. The cop was sitting 100 yards ahead of where I put my foot down. By the time I saw him (it seemed like 2 seconds later), he clocked me at 90.....
I have subsequently slowed down.
Probably more like one second. Second is surprisingly long time, top 100m dash sprinter moves 10+ meters in that time.
Cops here usually don't give tickets to people passing other cars (unless speed difference is just insane), because the less time you use in wrong line the safer the pass usually is. Common sense trumps laws. That cop must have had a bad day.
It happened, had my first speeding ticket in my Model S, 83 in a 65... SIGH. Officer said at first, I'll rip this up if you give me a ride, I without hesitation said HOP IN!!
He laughed and said he can't, I hate traffic school and yes, I'll do it online and bang it out in 2 hours but still! :(
At least the cop had a sense of humor ..kinda.
Start a chart; this ticket was 18 mph over the limit. See what the long term trend line is. ;)
Shoulda started the course on the touchscreen. Instant rebate }B)
He said he would let me off the hook with a warning but then gave me the ticket? I wonder were I went wrong as I was just nice, respectful and courteous, answered all his Model S questions enthusiastically too! :( Oh well... need to drive more carefully.
Examine the ticket carefully. It may be a "warning" ticket, not a real one.
As Brian noted, it could be a warning ticket.
When they give you a warning they have to write it up anyway.
Interesting, it looks very much like a ticket to me and I have never been let off the hook before. I don't see any indication that it's a warning, looks like it's a ticket. There is an infraction code, infraction is circled, nothing about it being a warning I am afraid. You had my hopes up for a moment there.
Do they indicate the amount of the fine?
No, can take up to 3 weeks to process, gotta love government's ability to move at the speed of snail.
Just received this message as I was posting actually:
"It can take up to 60 days for the court to receive the citation from the issuing agency and then to get it entered into our case management system. Please check back in with us, or online, in 30 days to see if we have received and entered it yet.
Records & Research/Traffic Court"
"gotta love government's ability to move at the speed of snail"
A short story regarding this: while I was into military I was in an accident driving an APC (a taxicab crushed itself to the side of my APC: I was slowly turning left to a forest road and it decided to pass vehicle behind me at that moment).
About two years later I got a message that I was not being prosecuted about that incident.
@Timo, LOL, we laugh to keep from crying!
Just want to add one more piece of advice. Don't get a speeding ticket... OK, obvious, but I'm posting this as an additional warming. I absolutely love my Model S and love to take her out, but since getting the speeding ticket, my fun level has been pulled back dramatically. Don't let your fun level get reigned back dramatically, it's super sad! :(
This feel's like a DirecTV commercial??
So is the world now safe from BYT?
Just got my 1st speeding ticket 1 month after taking ownership of my P85
Haven't had one in 15yrs or so.
Just Like BYT, 83 in a 65.
I was moving with many cars going the same speed on 480 north and he (CHP) admitted to picking me out of the group.
Hmmmm.... all the speeding tickets. The increased revenue should offset the loss in Gas taxes.
Fifth day of ownership upon exiting my front gate teleported to the stop light 1/2 mile down the street. Officer immediately pull me over but let me go with a warning after checking my papers. This incident has definitely tone down my fun factor. When ever I drive this car I still feel like a kid who just got the last cookie from the cookie jar.
That's what you get for travelling in bad/fast company!
I suppose I will just have to consider these fines as part of the TCO of the car
Has nasty downstream effects on your insurance premiums.


text:
Mary Ann Piette is a Senior Scientist, Director of the Building Technology and Urban Systems Division and Senior Science Advisor to the Associate Lab Director of Energy Technologies Area at Lawrence Berkeley National Laboratory. She oversees LBNL's building energy research activities with the US Department of Energy and over 25 other R&D sponsors. She is also the Director of the Demand Response Research Center. Mary Ann's work involves developing and evaluating new technology and building components, controls, operations, simulation, whole building and electric load shape analysis and behavior. She is also lead researcher at LBNL on the automated demand response technology. Mary Ann has authored over 90 peer reviewed publications related to energy efficiency and demand response and has worked at LBNL since 1983. She has a MS in Mechanical Engineering from UC Berkeley and a Licentiate in Building Services Engineering from the Chalmers University of Technology in Sweden.
Mary Ann Piette
Scientific Division Director
(510) 486-6286
"Automated Demand Response: The Missing Link in the Electricity Value Chain." 2008 ACEEE Summer Study on Energy Efficiency in Buildings. Pacific Grove, CA, 2008. LBNL-2736E. .
"Enhancing Price Response Programs through Auto-DR: California's 2007 Implementation Experience." AESP 18th National Energy Services Conference & Exposition 2008. LBNL-212E. .
"Field Test Results of Automated Demand Response in a Large Office Building." 8th International Conference on EcoBalance. . Tokyo, Japan, 2008. LBNL-1131e. .
"Installation and Commissioning Automated Demand Response Systems." 16th National Conference on Building Commissioning. Newport Beach, CA, 2008. LBNL-187E. .
"Linking Continuous Energy Management and Open Automated Demand Response." Grid Interop Forum. Atlanta, GA, 2008. LBNL-1361E. .
"Scenarios for Consuming Standardized Automated Demand Response Signals." Grid Interop Forum. Atlanta, GA, 2008. LBNL-1362E. .
"Solutions for Summer Electric Power Shortages: Demand Response and Its Application in Air Conditioning and Refrigerating Systems." . Refrigeration, Air Conditioning, & Electric Power Machinery 29 (2008) 1-4. .

subset: commoncrawl


text:
Honor the Heroes of the Game, Preserve Its History, Promote its Values & Celebrate Excellence Everywhere
Share your pictures, videos, and stories from your visit to the Pro Football Hall of Fame on our social media. We might even feature you in one of our promotions!
Let all your friends know that in your man cave, they have to "Obey the Rule" Cowboys style!


text:
Choose Your Currency
Recently added item(s) ×
You have no items in your shopping cart.
In stock
Original MaNgu is a ready to wear designer line that features contemporary apparel for woman - in particular curvy women. It features an array of styles, colours, textures and exclusive patterns that aim to help plussize women dress confidently.
Design and Developed by FlykickDesign


text:
Louisiana vital records
This entry was originally written by Wendy Bebout Elliott, Ph.D. FUGA for Red Book: American State, County, and Town Sources.
Between 1873 and 1876, some births were recorded by county district clerks. Many of these were included in Early Texas Birth Records, 1838'1878 (reprint. Easley, S.C.: Southern Historical Press, 1982) by Alice Duggan Gracy, Jane Duggan Sumner, and Emma Gene S. Gentry. Beginning in 1903 county clerks began to register births and deaths, although compliance was not universal at first. Large cities with vital records offices maintained their own series of birth and death records. Justices of the peace also recorded births.
Mandatory recording of births and deaths began in 1903. Copies of records registered in the counties are maintained at the Texas Vital Statistics division of the Department of State Health Services, 1100 W. 49th St., Austin, TX (mailing address: P.O. Box 12040, Austin, TX 78711-2040) [1]. For fast, affordable service, order birth certificates, death certificates, and birth, death, marriage, and divorce verification letters through TexasOnline, the official eGovernment site for the State of Texas. (http://www.texasonline.state.tx.us/tolapp/ovra/) Statewide indexes were microfilmed by the Texas State Library (see Texas Archives, Libraries, and Societies), and are available at many genealogical libraries. The birth index (1903'76) is alphabetized by year. The death index is alphabetical within broader periods of time (1903'40, 1940'45, 1946'55, then annually for 1956'73). The Genealogy Section of the Texas State Library provides limited correspondence service by checking indexes for a particular name for a small fee. If a birth or death record is not found at the state level, it is prudent to check the proper municipal or county office. Online indexes for Texas death records (1964'98) can be found at www.ancestry.com.
Probated or delayed birth registrations were sometimes submitted to the respective county court for probate matters. These were then forwarded to the State Bureau of Vital Statistics. Microfilm indexes to delayed birth records may have included Texas residents born elsewhere, many of whom were seeking Social Security registration. The bureau ended delayed birth registration in 1959.
Marriage records prior to 1836, if extant, may be in custody of the Roman Catholic Church. Beginning with the date of organization most counties maintain marriage records. These are presently in the jurisdiction of the respective county clerk where the license was issued. Statewide recording of marriages began in January 1966, but certified copies of records are not available through the state office. Marriage records for African Americans were frequently recorded in separate volumes.
Members of the Daughters of the American Revolution (DAR) have compiled many marriage records for Texas. These are available in the DAR Library in Washington, D.C., and on microfilm through the Family History Library (FHL) in Salt Lake City.
Consult the County Resource section in this chapter and the Guide to Public Vital Statistics Records in Texas (n.p.: Historical Records Survey, 1941) to determine availability of vital records in municipal and county offices.
Divorce records have been maintained statewide by the Bureau of Vital Statistics since January 1968, but certified copies are not available from this facility. Divorce records are kept under the jurisdiction of the respective clerk of the district court. During the first years of the Republic of Texas, divorces were granted by special acts of Congress, but in 1841 district courts took over this responsibility, with some exceptions. After statehood, district courts had full jurisdiction over divorces.
A sampling of published works containing Texas vital records include:
- Dodd, Jordan R. Texas Marriages: Early to 1850, a Research Tool. Bountiful, Utah: Precision Indexing, 1990.
- Grammer, Norma Rutledge. Marriage Records of Early Texas, 1824'46. Fort Worth: Fort Worth Genealogical Society, 1971.
- Smith, Bennett L. Marriage by Bond in Colonial Texas. Fort Worth: by author, 1972.
- Swenson, Helen Smothers. 8800 Texas Marriages, 1824'1850. Round Rock, Tex.: n.p., 1981.
- White, Gifford. 1830 Citizens of Texas: A Genealogy of Anglo-American and Mexican Citizens Taken from Census and Other Records. Austin, Tex.: Eakin Press, 1999. Includes registers of birth.
FamilySearch.org has a variety of collections available for free online:
- Texas, Births and Christenings, 1840-1981
- Texas, Birth Certificates, 1903-1935
- Texas, Birth Index, 1903-1997
- Texas, County Marriage Index, 1837-1977
- Texas, Marriages, 1837-1973
- Texas, Marriages, 1966-2010
- Texas, Divorce Index, 1968-2010
- Texas, Deaths (New Index, New Images), 1890-1976
- Texas, Deaths, 1890-1976
- Texas, Death Index, 1903-2000
- Texas, Deaths and Burials, 1903-1973
- Texas, Death Index, 1964-1998
- Texas, Deaths, 1977-1986
External Links
- Texas Birth, Marriage, and Death Records - free up-to-date guide to accessing Texas birth, marriage, and death records (FamilySearch Research Wiki). Includes links to FamilySearch vital record databases.
- Birth, Marriage, and Death Records (BMD)


text:
Espresso done right is intense — a full-bodied, stop-time moment to savor
Posted by TheShot on 11 Jan 2007 | Tagged as: Beans, Machine, Quality Issues, Restaurant Coffee, Robusta
Tomorrow's Atlanta Journal-Constitution nails it with this article headline: Espresso done right is intense — a full-bodied, stop-time moment to savor | ajc.com. Somewhat surprisingly, what follows the headline isn't half bad either.
The author, John Kessler, goes on to note how rare a decent espresso is in this country — and in fancy restaurants in particular. But rather than merely lament the sorry state of American espresso, he makes a legitimate attempt at an explanation. He attributes this sorry state to a variety of factors, including a cultural preference for the 30-minute indulgence rather than the three-sip shot, insufficient steam pressure from many commercial machines, and an avoidance of robusta beans. It's a noble attempt worthy of examination.
One Nation, Under the Super Big Gulp®
America's culture of indulgence is dismissive of the "small tasting". The small tasting typically makes an acceptable appearance only where physical constraints make it absolutely necessary — such as part of a lavish seven-course meal. (As celeb chef Anthony Bourdain is quick to point out, after the first few bites of anything, our taste buds progressively deaden with the same stimulus. Beyond those first tastes, you're no longer satisfying your taste buds; rather, you are trying to satisfy something else entirely.) Combine this with our cultural obsession over all-you-can-eat "value", and its no wonder that our espresso is over-extracted, poured in copious amounts, and almost always washed away in a sea of steamed milk.
Unfortunately, conventional wisdom in this country suggests that espresso is a "hot, bitter brew" — with the maximum caffeinated effect. This reflects just how poor the American cultural standard for espresso really is. I would argue that if it's hot and bitter, you're not drinking espresso — you're drinking something else. In a country where our beverage choices are either "freezing" or "scalding", espresso should be served a touch closer to room temperature. And if it's bitter, whoever made it likely over-extracted the shot, and it should be sent back like a corked wine.
But — as Corby Kummer, author of The Joy of Coffee, is quoted in the article — "I hate it when people use a wine analogy for coffee." Lately, I have caught myself using a balsamic vinegar of Modena analogy. Acidic vinegar doesn't sound like the kind of appetizing thing you might, say, pour over ice cream. But if you've ever had aged balsamic vinegar of Modena, you know just how sweet and syrupy — and so unlike its wine-based American counterpart — it can be. The same is true when comparing a true espresso with the typical American version.
"You've got robusta in my espresso!"
Back to Mr. Kessler's explanation, I also have to agree that the American espresso is almost universally over-extracted and brewed at the wrong temperature. The general state of espresso equipment tuning and maintenance is sorry and sad. But training plays a huge role too. Machines tuned to perfection could be rendered irrelevant in untrained hands. All it takes is someone to leave the portafilter handles cooling in the drip tray.
However, I am in less agreement with his "aversion to robusta" argument. Sure, robusta is generally a cheaper grade coffee that many American retailers tend to avoid on this criteria alone. And the right percentage of good-quality robusta in an espresso blend can make a huge difference in an espresso's volume of crema, the richness of its aroma, and the breadth of its flavor profile. But I've also had astounding single-bean espresso shots that have blown blends out of the water.
Speaking of ever-tiresome wine analogies… On a semi-related note, today's The Washington Post today published an article where the author learned how to evaluate different bean stocks through a weekly public cupping at D.C.'s Murky Coffee: Wake Up and Cup the Coffee – washingtonpost.com.
1 Comment »
One Response to "Espresso done right is intense — a full-bodied, stop-time moment to savor"
[…] At l'università, they compared for him espresso made with 100% Arabica beans and with a 50/50 Arabica/robusta blend. Illy openly disdains robusta coffee as a cheaper coffee stock, so it's not surprising. Yet there are others who argue that the American outright avoidance of robusta in quality espresso is a major problem. In any case, I find an espresso blend of 90/10 makes a nicely balanced espresso — particularly with some of the high-end, carefully processed robusta stocks now available from places like India. […]


text:
2lushcru necesitaba un nuevo diseño de logotipo y lanzó un concurso de diseño en 99designs.
Un ganador ha sido elegido entre 119 diseños de 35 diseñadores freelance.
We are a couple with 15 -20 years each in our respective domains. He has a strong business, turnaround & tech background and she has built a strong business as a master sommelier by buying and selling for private collectors. Together, we are pursuing our dream of providing the world with access to many of the finer things typically not available to most in the areas of wine, travel, and other fine luxuries.
Successful/professional people of all levels. Our target audience will be individuals who have enough discretionary income and interest to enjoy purchasing wine, spirits, unique travel (not necessarily exotic), and value knowledge, first hand experience, and purchasing items which have a story/history related to them. This audience is always in pursuit of new things to enjoy without b.s. of elitism. As a couple, we will be building a rapid following of existing friends, clients, colleagues who are professionals.
To help here, some further explanation of our name, 2LushCru.
The 2 is for the two of us.
The "Lush" is for luxurious (described by dictionary.com as 'characterized by luxuriousness, opulence, etc') and also a play on the alcohol related connotation of "lush." A major focus for us will be visiting wines and reviewing rare wines and spirits onsite, but we will not be solely focused on alcohol.
The "Cru" is derived from the French use of the term in relation to "class" of wine, such as grand or premier cru. In this case it is worked in to mean best of the best.
Summarized, the name is meant to describe the two of us as pursuing the best of the best things to make life lush for our followers.
We are seeking a logo that is crisp and clean looking and which matches the audience we have. We want to be sure it is something not easily trivialized but also not too stodgy. We want to appeal to our rich and famous friends as well as the working professional who is interested in what we are doing.
We would like the final deliverable to include versions in .ai, jpg, and png for Web and print mediums. The initial logo will be used on business cards, the Web site, and in videos.
Descubre cómo funciona un concurso de diseño u obtén más información sobre nuestros servicios de diseño de logo.


text:
U.S. Equal Employment
Opportunity Commission
DENVER - After a three-day trial, a 12-person jury returned an $8 million verdict in federal court today for the U.S. Equal Employment Opportunity Commission (EEOC) in a lawsuit alleging that EchoStar Communications Corp. (EchoStar) violated the Americans with Disabilities Act of 1990 (ADA) when it refused to provide a reasonable accommodation to Dale Alton, a qualified blind employee. EchoStar, based in Englewood, Colorado, is a provider of advanced digital television services.
The jury verdict awards $2,000 in back pay, $5,000 in compensatory damages, and $8 million in punitive damages for Mr. Alton. In the trial, presided over by Judge Richard P. Matsch, the plaintiffs alleged the following:
"This verdict should remind employers that refusing to abide by the law in accommodating individuals with disabilities can be costly," said Joseph Mitchell, Regional Attorney of the EEOC's Denver District Office. "Many individuals with disabilities, such as Dale Alton, are ready, eager and able to work. All they need is the opportunity to do the job without discriminatory barriers based on myths, fears and stereotypes. Employers must remember that disability does not mean inability."
In the trial, the plaintiffs presented evidence that Mr. Alton, who is blind, applied for a customer service representative job at EchoStar in 1999. Prior to applying, Mr. Alton had completed training at the Colorado Center for the Blind for that very type of position. Blind individuals can perform the customer service representative job by using a computer program called JAWS (Job Access With Speech), which translates text into speech. A blind customer service rep uses a split headset, in which he hears the JAWS voice in one ear, and the customer conversation in the other ear. Using JAWS, people with vision impairments can process written language at 400 to 700 words per minute, which is faster than many sighted individuals read. At trial, the plaintiffs' expert, Nelson Reiser, demonstrated to the jury how JAWS works.
When Mr. Alton first went to EchoStar to apply, EchoStar told him it would not do him any good to put in an application because they were not set up to handle blind people. However, after receiving a copy of his charge of discrimination, EchoStar invited Mr. Alton back and put him through a sham interview process that included a Braille test, which was longer and more difficult that the test given sighted people, and a Windows skill test that consisted of a person giving him directions on how to access icons, such as "move to the left, move down, now click."
Much of the testimony related to whether, if EchoStar had tried to install JAWS in 1999, it could have worked. EchoStar asserted that JAWS could not have worked because of the complexity of the software environment. Contrary evidence presented by plaintiffs reflected that, in 1999, numerous employers in Denver such as Norwest Bank, American Express, Big Brothers/Big Sisters, and MCI had installed JAWS and employed blind customer service representatives at their call centers.
Dale Gaar, Mr. Alton's private lawyer, said, "This verdict is very rewarding because it has the potential for opening thousands of customer service representative jobs to qualified blind people around the country."
According to its web site, www.echostar.com, "EchoStar Communications Corporation (Nasdaq:DISH) serves more than 11.2 million satellite TV customers through its DISH Network(TM), and is a leading U.S. provider of advanced digital television services. DISH Network's services include hundreds of video and audio channels, Interactive TV, HDTV, sports and international programming, together with professional installation and 24-hour customer service. EchoStar has been a leader for 25 years in satellite TV equipment sales and support worldwide. EchoStar is included in the Nasdaq-100 Index (NDX) and is a Fortune 500 company."
EEOC is the federal agency responsible for enforcing the federal statutes which prohibit employment discrimination, including Title VII of the Civil Rights Act of 1964, which prohibits discrimination based on race, color, sex, national origin, or religion; the Americans with Disabilities Act (ADA), which prohibits job discrimination based on the existence or perception of a disability; the Age Discrimination in Employment Act, which prohibits discrimination against persons age 40 and over; and the Equal Pay Act (EPA), which prohibits wage discrimination based on sex. The EEOC's Denver District Office, located at 303 East 17th Avenue, Suite 510, in Denver, enforces the anti-discrimination laws in Colorado, Montana, Nebraska, North Dakota, South Dakota, and Wyoming. Further information about the Commission is available on its web site at www.eeoc.gov.


text:
Climate change is already causing disruption to marine ecosystems, according to a series of talks given at this years' American Association for the Advancement of Science meeting. Oceans are both warming and acidifying, and the effects are different from those traditionally faced by the conservation community, which is having to learn how to use new tools and adapt itself to this brave new world.
Prof. Dee Boersma of the University of Washington kicked things off with data from her group's work with the penguins of Punta Tombo, Argentina. Prof. Boersma sees the penguins as sentinels that are already telling us about severe changes underway. The egg-laying season has been shifting later and later, at the rate of about 3 days every decade. When this is coupled with the greater contrast between El Ni�o and La Ni�a years, the cost of living for penguins in Punta Tombo is going up. GPS data from tagged birds reveals that they have to travel up to 40 km farther in 2008 than 2002—a long way for a small bird.
One of the results has been a northward migration, with penguins starting new colonies further up the Atlantic coast. This lined up quite well with the following talks, both of which presented modeling data on how climate change will most likely affect marine ecosystems.
Dr. William Cheung of the University of East Anglia discussed research that used climate model predictions and data of species abundance to project the changes in distribution of over 1,000 commercially important fish and invertebrate species. Cheung's work points to a migration towards higher latitudes and deeper water as species seek out more hospitable habitats.
Practically, this means local extinctions in traditional fishing areas (already being witnessed in the Bering Sea), and species invasion into others. Countries are going to lose fish stocks to their neighbors, something we're already seeing with jumbo squid and salmon. Cheung predicts that Norway, Greenland, and Alaska are going to be the biggest winners, with China, the mainland US, Indonesia, and Chile losing the most.
The final talk of the session was by Prof. Patrick Halpin, from Duke, on the predicted effects of climate change on marine protected areas (MPA). Prof. Halpin's take-home message was that the effects will not be uniform; not every MPA is as tolerant as the next, and they won't all receive the same "dose."
According to Halpin, modeling the effects of climate change on MPAs is not nearly as simple as for land masses or the open oceans. MPAs tend to be near shore, which complicates the models (based on how much of a grid is land or water), but the data show a linear trend towards warming, and the mean increase is greater than that seen for the open oceans.
The damage being done to reef ecosystems is pretty well known, with warm water reefs being at greater risk; projections show that by the end of the current century, around 90 percent will be subject to heating greater than 2�C. Another risk highlighted by Prof. Halpin is that the connections among reefs might break down, wreaking havoc on connected but geographically dispersed ecosystems.
Prof. Halpin also spoke about upwelling systems, such as those off the coast of California that bring nutrient-rich water up from the depths. The models are more suspect here, but they predict an end to upwelling by 2100, which would have massive repercussions should it happen.
Halpin ended by suggesting that it's time to move away from MPAs and towards ocean zoning, a practice that is more effective both for minimizing the damage to sensitive ecosystems and also for allowing productive human use of the seas, be that fishing or industrial.
Overall, the session painted a pretty bleak picture for the oceans over the next hundred years, but as we found out in a different session that we'll cover shortly, it's not doom and gloom everywhere.


text:
Unlike LeBron James, the Duke Blue Devils didn't take their talents to South Beach.
Coach Mike Krzyzewski's top-ranked team seemed to leave it all back in Durham, getting blown out by 27 points by Miami (Fla.) and looking like the Hurricanes' punching bag for much of the night.
GAME STORY:Miami pounds Duke in upset
One way to tell that the Blue Devils were getting freakishly embarrassed came when TV's most Duke-biased personality completely bashed them.
Early in the second half, ESPN analyst Dick Vitale ripped Duke without any remorse, paying ultimate compliments to Miami.
"This is the poorest performance I have witnessed from a Duke team in all my years sitting courtside," Vitale said passionately on the live ESPN broadcast.
He later added, "Warm up the bus, this game is over. ...(The Blue Devils) have no one to blame but themselves."
MORE:UNC fans chant 'go to hell Duke'
With Duke reeling and left searching for answers (and a shooting touch), Miami is looking more and more like a legitimate contender to win the Atlantic Coast Conference after routing Duke and with challenger N.C. State losing to Wake Forest on Tuesday night.
Ah, cue the Will Smith. If this team advances far in the NCAA tournament, you know "Welcome to Miami" will be playing on TV as the team's anthem.


text:
Our international readers probably roll their eyes every time we write about a car that doesn't come to the U.S. Usually it's over something like a Dacia Sandero and those of you in countries where it's sold question our affection for it. Well, try living here without a truly simple and dirt cheap hatchback.
Today's object of lust from overseas was the SEAT Leon Cupra 280, something that's really similar to the Volkswagen Golf R we're getting, only way sexier. It's like a Golf that was actually styled with creases and sharp wheels.
The reasons why we're not getting it are understandable. VW has also never marketed SEATs here. Getting an entire market as large as the U.S. to be familiar with a new brand is expensive and time consuming. Then, of course, they have to deal with the jokes. And SEAT comes with a big one.
It's probably people like Arch Duke Maxyenko, Great Job who make the VW Group's marketers say "No way, SEAT" every time. Probably:
Chris Hanson-"Hello, I'm Chris Haaaaaaaaanson. What brought you into this dealership today?"
Person-"I'm, uhm, a, just looking for a car."
CH-"Do you know why I'm here?"
P-"Uh.... no? I'm just looking for a car..."
CH-"Please, have a Seat."
P-"No I was thinking more along the lines of the used Focus..."
CH-"What, you don't like V.A.G.? Just have a Seat."
P-"What?!? No, I'm just thinking about that Focus, it's only a few years old..."
CH-"Did you bring condoms?"
P-"Dude, what the fuck?"
CH-"Exactly, your on To Catch a Buyer, the sales people will be here soon."
P-"OK Fuck this I'm out" (Turns to run, instantly gets tackled by a salesman)
Exactly. Can't take you guys anywhere.
Photo: SEAT


text:
I've been to this restaurant three times in less than a month… or is it four?
Apparently, it's quite difficult to get Shi Lin's Noodles with Spicy Sesame and Peanut Sauce (P130) out of my system. I daydream inordinately about this dish in the most inopportune times, and how can I not? Noodles slightly resistant to my nibbling are awash in a sauce that's got sesame riding shotgun with peanut piggybacking. In its white bowl, it's a vibrant vista of orange like a sunrise set ablaze tempered only – but just by a little – with a swath of green from a blade of bokchoy and spring onions.
Though sugar is my cocaine of choice, it's the dish above plus two other dumplings that are the shining new stars in my culinary galaxy. At Shi Lin, the restaurant-temple for all foods Taiwanese, their version of Xiao Long Bao (P108/6 pcs) is a touch soupier than its local counterparts – a good thing – since the slightly salty broth highlights the ground pork filling. Some say that the dumpling wrapper isn't as delicate as that of a "true" xiao long bao, but whether that's true or not, I prefer the wrapper this way – it retains its integrity with the other components instead of dissolving into a diaphanous mass.
Shi Lin has been open for about three months, named after Taipei's Shilin District (also Shih-lin), best known for the Shihlin Night Market, the city's largest. A tribute to Taiwanese cuisine, the restaurant has chosen what co-owner Carlo Lorenzana describes as, "… a select few items … [It's] easy to choose, not a complicated menu, and we try to make all our items excellent."
Taiwanese cuisine originated in the Fukien/Fujian province of southern China. Because most of Taiwan's immigrants originated from there, Taiwan adopted Chinese cuisine as its own, thus the striking similarities between the two countries' national foods. Japan's 50-year occupation of Taiwan also left its imprint on the country, hence the popularity of sushi and miso soup.
Dumplings are the divas at Shi Lin, they must grace your table. The already-mentioned xiao long baos are a given and also consider the Shrimp & Pork Shaomai (P135/6pcs) that often induce gasps for their sheer artistry. Formed to resemble little flowers, the "shaomai's" swollen bases protect a portion of broth that bursts on bite, tickling the tongue. On top, the single shrimp is a garnish, a crowning touch. I also enjoy the Vegetable & Pork Dumplings (2nd photo from top; P128/6pcs) even if they irresolutely leave a telltale strand of green in my teeth every time. The same filling – I believe – is also used in the Vegetable & Pork Bun (P98/2pcs). A very interesting dish is the Drunken Chicken (P240), one that I lament not having a picture of. Chicken slices are laid out almost fan-like on a platter, the meat sitting in a potent brew of sweet rice wine laced with – what to me tastes like – ginseng, sesame oil, soy sauce, and chili peppers, all elemental ingredients in Taiwanese cuisine.
- Vegetable & Pork Bun
A rather straightforward plate is the Fried Shrimp & Pork Wonton (P110/6 pcs) shaped like tortellini. Dipped in the accompanying chili sauce, they crackle in the mouth before the pork takes over.
While I heartily recommend almost all the dishes in Shi Lin's repertoire, I urge you to (please!) not miss any of the rice dishes. I for one, have a relentless attachment to the Fried Rice with Pork Chop and Egg (P178), a seemingly simple dish until I'm actually eating it. The pork chop, crisp in its coating is perfection fried, the short-grained rice tumbles about it, a playground where the soundtrack is a chord of umami: big, meaty, can't-get-enough-go-get-your-own. Truly, the guilelessness of this dish is its steady lure. It's almost anti-climactic to say it but the Fried Chicken Chop (P165) also gets the job done.
Shi Lin is a fast-casual restaurant. I eat here while taking a break from meetings held at the Podium; another time, I'm dressed to the nines before a frenzied Friday night out. And this is the restaurant I choose for the Jessica Soho shoot. Every time, this is a comfortable, relaxing space. The service is occasionally slow but always accommodating and gracious. Sunlight filters in through the tinted glass during the day; at night, the Ortigas skyline is my backdrop. Naturally, the see-through window where one can gaze at the intricacies of dumpling-making is as always, riveting eating entertainment.
- taro dumplings
Carlo is also the distributor of La Mill Coffee & Teas, my brand of choice for caffeine. They serve them in the Hario Drip Coffee and in the two special iced teas namely, Green Mystique and Passionberry. Have these beverages during meals or pair them as I do after meals. Dumplings for dessert can be had with the Taro Dumpling (P98/6pcs), purple and precious. The Cool Almond Jelly with Lychee (P75) I understand, has quite the cult following. "Some people even have two, " Carlo tells me.
And of course, the Hot Almond Cream with Sesame Ball (P95). There are shots of me eating this dessert as seen in the segment on the Jessica Soho show. Immediately after airing, I receive texts from various people, variations on: "Never mind you, tell me about those exploding balls!" Eh, lascivious lot they are. But I understand the attraction. This is a hot dessert (in all ways imaginable): glutinous orbs with a shadowy heart, the black sesame center pulses, swims in a liquid warmth of milk, sugar, and flavoring. Sip the soup, bite the ball, midnight dark makes its mark.
Shi Lin
3/F The Podium, ADB Ave.
Ortigas Center, Mandaluyong City,


text:
Back to
Thank you for contacting the Center for Information!
Removal From Mailing or Calling Lists Request Form
Thank you for contacting the Center for Information!
Please send us an email with as much detail as possible so we can properly assist you. We will respond within three business days.
Send your email to: firstname.lastname@example.com
If you would like immediate assistance, please call us Monday-Friday 8:30 a.m. to 8:00 p.m. ET at 1-800-DIABETES (800-342-2383)


text:
I wanted to write some more sophisticated asserts in the Genome tests where the exception message is also tested for the error code (e.g. if the message contains #GENxxx).
In newer versions of NUnit there is an enhanced version of the ExpectedException attribute, where you can match the exception message in multiple ways. For example you can use a "contains" match to see if the right error code was mentioned in the exception message.
[ExpectedException(typeof(GenomeException), ExpectedMessage = "GEN01253", MatchType = MessageMatch.Contains)]
As we were using an old version of NUnit (v2.2.6) I tried to upgrade to v22.214.171.12445 to make use of the new features. As soon as I did this my R# v4.5 failed to identify the ExpectedException at all.
To make it clear: even if I leave the ExpectedException attributes as they are (no new parameters like MatchType) the test runner does not recognize it, so all the existing tests using the ExpectedException attribute fail in the Resharper running environment after the upgrade of NUnit.
As you can see this is a major problem with R# that can be a show stopper (either to upgrade NUnit or to use R# for executing the tests), but it turns out that you can upgrade to R# v4.5.2 so that it supports the ExpectedException attribute of the newer NUnit versions *again*. I have found the info here: http://www.jetbrains.net/devnet/thread/281286
After installing the new version it seems to work again. But It also turns out that the new parameterization with MatchType is still not supported. Trying the sample above the runner ignores the MatchType and claims that the message is not the same as specified. So you just get back the "basic" functionality of ExpectedException. Jetbrains "refused" to support this properly in the v4 branch and they promise improvements in v5.0 only: http://www.jetbrains.net/jira/browse/RSRP-43833
Get rid of the ExpectedException for the future anyway?
I'm not sure if this common sense, but there is a new way to expect the exception with NUnit. You can use the Assert.Throws method, where you pass the code that is supposed to throw the exception as delegate. This way you can explicitly mark "where" you expect the exception (while with the attribute it is not visible).
Also, you get back the exception in a strongly typed way and you can just write normal asserts about the exception. E.g. I can assert on the ErrorCode of the GenomeException. It is much cleaner compared to a String.Contains expressed in the ExpectedException attribute.
Another benefit is (considering the upgrade issues above) that you are more independent from the running environment, because the assertion is expressed as normal C# code. The runner does not need the "extra knowledge" unlike in the case of a special attribute.
[Test]public void CreateObjectWithDefaultDiscriminatorReference(){... var exception = Assert.Throws<GenomeException>(() => { Context.Current.Flush(); } ); Assert.AreEqual("GEN0153", exception.ErrorCode); Assert.That(exception.Message, Is.StringContaining("type discriminator")); Assert.That(exception.Message, Is.StringContaining("not set")); }}
This is not a reason to rework all the existing tests, but I'd suggest to use this new technique for the future.
Before describing the problem, let me summarize some not-so-well-known facts about LINQ. If you are experienced with LINQ and the expression trees it uses, you can even skip this part and proceed from "So much for the LINQ overview" sentence to read about the problem I ran into.
When you write a query, such as
from c in customers
where c.City == "London"
select c
the C# compiler compiles it into a method call like this:
from c in customers
where c.City == "London"
select c
customers.Where(c => c.City == "London")
customers.Where(c => c.City == "London")
You can even write the Where() call directly as well; you don't have to use the "from…" syntax. The parameter of the Where() call is a special construct called a lambda expression, which is something very similar to an anonymous method. In fact, sometimes it is an anonymous method.
Now the question is what you want to do with this lambda expression. If you want to filter customers that are already loaded into the memory, you want to have an anonymous method compiled from the lambda. However, if the customers reside in the database or in an XML file, you actually never want to evaluate the lambda as a .NET method call, but rather you want to transform it to SQL or XPath and let the underlying engine execute it. In this case, the anonymous method is not a good option, as it would be very hard to find out from the compiled CLR code that the method wanted to compare the City field to "London".
And here comes the big trick of LINQ. The C# compiler decides during compile time whether to compile the lambda expression to an anonymous method, or to an expression tree initialization code. If it compiles it to expression tree initialization, then during runtime, a new expression tree will be created whenever this Where() method is called, and this expression tree will represent the lambda expression you just described. O/RM engines like Genome can take this expression tree and transform it to SQL.
The only question remains is how the C# compiler can decide whether to compile the lambda to an anonymous method or to expression tree initialization. This decision is done by analyzing the parameter types of the Where() method you are actually about to call. If the Where() method takes a delegate as a parameter, it compiles to an anonymous method, and if it takes an Expression<T> parameter, it compiles to expression initialization.
It is good to know that the LambdaExpression class has a Compile() method, that can be used to compile the expression tree to a delegate. We don't have a transformation in the other direction however, so you cannot get an expression tree from a delegate.
Read more ...
We frequently get asked about Genome's future in the light of Microsoft's upcoming .NET 3.5 SP1 release, which includes the Entity Framework and related technologies such as LINQ and ADO.NET Data Services (see also the beta release announcement on Scott Guthrie's blog giving a broad overview about the new features).
LINQ (already released with .NET 3.5) provides query language capabilities for C# and VB.NET. Many new Microsoft technologies and products by other vendors rely on LINQ. It is crucial to integrate with it in order to stay connected with other technology trends. The distinction to LINQ2SQL needs to be emphasised, as many users confuse the two.Genome has been fully integrated with LINQ since November 2007 (although we released several preview integration versions from 2006 on). In fact, Genome was the first third party O/RM to provide LINQ integration. Developers who use Genome are thus not locked out of technology trends related to LINQ.
Astoria is the code name for Microsoft ADO.NET data services. It provides a REST interface for any data source that supports the interfaces IQueryable (introduced with LINQ) and IUpdateable (introduced with Astoria). It is not an O/RM, but rather a messaging layer over O/RMs or other data sources.Astoria's current release focuses on integrating with Entity Framework, but it appears that its extensibility is still unstable when it comes to other frameworks. Astoria is a great concept, but we doubt anyone is currently using it in production.We are confident that Genome will support Astoria in the near future (before the end of this year), when integration possibilities have matured and the integration issues on Astoria's side have been resolved. As with LINQ, developers who use Genome are not hindered from using this technology.
Entity Framework actually consists of three major modules:
Genome actually overlaps with LINQ To Entities to a certain degree. Entity Framework itself is much more than an O/RM, as it represents the next level of abstraction for data access on the .NET platform (hence its original name, ADO.vNext). If Entity Framework proves to be useful and is widely adapted by our target customers, we can imagine integrating Genome with Entity Framework by replacing LINQ to Entities and allowing CLR business models to be mapped to EDMs with Genome. This would help our customers benefit from the Genome O/RM API and utilise EDM for other applications such as reporting, etc.
Our main concerns about Entity Framework and Genome's value proposition:
There is the potential that the proposed development model and abstraction required by Entity Framework is overkill for certain applications (e.g. there are three models and all mappings between them need to be managed).
Tools provided by Entity Framework heavily depend on visual designers integrated in Visual Studio to manage the various mapping models and generate code from the models. This is especially the case with large and complex projects that involve large and complex models – which is what Entity Frameworks seems to target. We strongly doubt that relying on visual designers to that extent is a good approach. For example, resolving a merge conflict in the model (as can easily occur in projects with large teams) is not possible with a graphical designer, thus forcing developers to edit models manually.
Of course any first version of a product will have some immaturity issues which people usually have to more or less work around. However, since Entity Framework provides a radical and very complex new concept for abstracting data access, the functional completeness of Version 1 is very low compared to what the concept itself covers. The danger of encountering issues that are difficult or impossible to resolve is quite high in Version 1. This can be a particular problem in large enterprise projects, which is of course what Entity Framework appears to target.
The funny thing is that while LINQ2SQL is too simple for many applications, Entity Framework seems to be far too complex for many of our cases.
We are going to continue polishing Genome into an O/RM that we think is sophisticated enough to serve complex enterprise projects while also remaining simple enough to not force over-engineering. We are just about release Genome V4. Working on O/RM for .NET since 2002 has given us quite a lot of confidence in our approach: we balance flexibility and simplicity. We ensure that our customers are not locked out of technology trends on the .NET platform, so we will continue to integrate Genome with new technology concepts introduced by Microsoft in this field. We hope that our position as the first 3rd party O/RM to integrate with LINQ has already proven our commitment to this strategy.
Microsoft has released .NET Framework 3.5. service pack 1 beta. For all Genome users: be
aware that this package rather quietly also contains an SP2 beta for the .NET
2.0 Framework, which cannot be deployed alone. There is not too much
information available on its exact contents (see http://readcommit.blogspot.com/2008/05/microsoft-net-framework-20-service-pack.html).
Be warned
that it is possible that a Genome schema compiled with the SP beta may not load
on a machine without the SP beta (which is usual for production servers),
yielding the following error:
SerializationException: The object with ID
40221 implements the IObjectReference interface for which all dependencies
cannot be resolved. The likely cause is two instances of IObjectReference that
have a mutual dependency on each other.]
We are
sorry about any inconvenience caused. This issue may occur with Genome
V126.96.36.199 and we are currently investigating if others are affected. We are providing feedback on this issue to Microsoft and hope that it will be resolved with the release - in the meantime, please make sure that deployment
packages are generated on a machine that does not have SP1 beta installed!
Many posts (e.g.: http://blog.deploymentengineering.com/2007/06/dealing-with-very-large-number-of-files.html, http://www.wintellect.com/cs/blogs/jrobbins/archive/2007/10/19/wix-the-pain-of-wix-part-2-of-3.aspx, http://blog.deploymentengineering.com/2007/06/burning-in-hell-with-heat.html) have been written about the problem of adding large number of files to a WIX installer. This problem is the most painful when you want to add content files that do not really have any special purpose, but just have to be there (e.g. code samples or source code packages).
I also struggled with this problem, and finally I found myself creating a small MsBuild tool (WixFolderInclude.targets) that you can include in your WIX project and use to generate file installers for entire folders on the disk. I call it a tool, as I don't have a better name for it, but it is not (only) an MsBuild target, nor is it a Task. Actually it is a WIX MsBuild extension, but WIX already has a "WIX extension" term, which is something else. So let's stick to "tool".
The WixFolderInclude tool
Let's see how you can use this tool; it was tested with the latest WIX framework (v3.0.4220), but it probably works with older v3x versions as well. I'm assuming that you are more or less familiar with the WIX and MsBuild concepts. If not, you can grab the necessary information quickly from Gábor Deák Jahn's WiX Tutorial and the MSDN docs.
WIX projects (.wixproj) are MsBuild projects, and you can extend them with other MsBuild property definitions or targets. One option is to modify the wixproj file in a text editor… This is fine, but I like the WIX project to open in Visual Studio, and in this case modifying the project file is not easy. Instead, I usually always start by creating a "Build.properties" file in the WIX project (it has type "Content" so it does not modify the WIX compilation), where I can write my MsBuild extensions. I have to modify the project file only once, when I include the Build.properties file. I usually include it directly before the wix.targets import:
</ItemGroup><Import Project="$(MSBuildProjectDirectory)\Build.properties" /><Import Project="$(WixTargetsPath)" />
But you can directly write into the project file as well, if you don't use the VS integration.
Let's take a very simple example: I would like to include two code samples in the installer. They are located in some folder (C:\Temp\ConsoleApplication1 and C:\Temp\WebApplication1) and I would like to install them in a "Samples" folder inside the program files entry of my installed application. Of course both samples contain sub-folders that I also want to include.
To achieve that with my tool,
So first, let's create the folder descriptions for my sample. The tool searches for project items called "WixFolderInclude", so we have to create such items for the folders we want to include:
<ItemGroup> <ConsoleApplication1Files Include="C:\temp\ConsoleApplication1\**" /> <WixFolderInclude Include="ConsoleApplication1Folder"> <SourceFiles>@(ConsoleApplication1Files)</SourceFiles> <RootPath>C:\temp\ConsoleApplication1</RootPath> <ParentDirectoryRef>Dir_Samples</ParentDirectoryRef> </WixFolderInclude></ItemGroup>
<ItemGroup> <WebApplication1Files Include="C:\temp\WebApplication1\**" Exclude="*.scc" /> <WixFolderInclude Include="WebApplication1Folder"> <SourceFiles>@(WebApplication1Files)</SourceFiles> <RootPath>C:\temp\WebApplication1Files</RootPath> <ParentDirectoryRef>Dir_Samples</ParentDirectoryRef> </WixFolderInclude></ItemGroup>
As you can see, you can define the set of files to be included with the standard possibilities of MsBuild, so you can include deep folder structures, exclude files, or even list the files one-by-one. In the example here I have excluded the source-control info files (*.scc) from the second sample.
In the WixFolderInclude items, you have to note the following things.
As we are ready with the definition, the next step is to set up the tool. It is very simple; you just have to include the following lines in the Build.properties (or the project file):
<Import Project="$(MSBuildProjectDirectory)\Microsoft.Sdc.Tasks\Microsoft.Sdc.Common.tasks" />
The value of the CustomAfterWixTargets should point to the tool file. If you have it in the project folder, you can use the setting above directly. Also note that the tool uses the Microsofr.Sdc.Tasks library (http://www.codeplex.com/sdctasks). I have tested it with the latest version (2.1.3071.0), but it might work with older versions as well. You should import the Microsoft.Sdc.Common.tasks file only once, so if you have already imported it in your project, you can skip that line.
Now we are done with the entries in the Build.properties, so let's include the folders in the installer itself. As I have mentioned, the tool generates fragments that contain a component group for each included folder. The component group is named as follows: CG_WixFolderInclude-name. In our case, these are CG_ConsoleApplication1Folder and CG_WebApplication1Folder. So let's include them in the main feature now:
<Product ...> ...
<!-- setup the folder structure --> <Directory Id="TARGETDIR" Name="SourceDir"> <Directory Id="ProgramFilesFolder"> <Directory Id="INSTALLLOCATION" Name="WixProject1"> <Directory Id="Dir_Samples" Name="Samples"> </Directory> </Directory> </Directory> </Directory>
<!-- include the generated component groups to the main feature --> <Feature Id="ProductFeature" Title="WixProject1" Level="1"> <ComponentGroupRef Id="CG_ConsoleApplication1Folder"/> <ComponentGroupRef Id="CG_WebApplication1Folder "/> </Feature></Product>
And that's it. We are ready to compile!
Fine tuning
The tool supports some additional configuration options, mainly for debugging purposes: you can specify the folder where the temporary files are stored (by default, it is the value of %TMP% environment variable) and whether it should keep the temp files (by default, it deletes them after compilation). These settings can be overridden by including the following lines in the Build.properties.
<PropertyGroup> <WixFolderIncludeTempDir>C:\Temp</WixFolderIncludeTempDir> <WixFolderIncludeKeepTempFiles>true</WixFolderIncludeKeepTempFiles></PropertyGroup>
Possible problems
Of course, life is not that easy... so you might encounter problems with using this tool as well. One is that it kills MsBuild's up-to-date detection, so it will recompile the project even if nothing has changed. I think this could be solved by specifying some smart output tags on the target, but it is not easy, and usually I want to be sure that the installer package is fully recompiled anyway.
The other – probably more painful – problem is that you cannot include additional files from WIX to a subfolder of an included directory. We had this problem when we wanted to create a shortcut to the solution files of the installed samples. The problem is that since the IDs that the Sdc Fragment task generates are GUIDs, you have no chance of guessing what the subfolder's ID was.
I have extended the WixFolderInclude.targets to support generating deterministic names for some selected folders. The folders to be selected can be defined with the "DeterministicFolders" metadata tag of the WixFolderInclude item. The value should be a semicolon-separated list of folders relative to the RootPath. Please note that as these are folders, you cannot really use MsBuild's wildcard support, but you have to type these folder names manually. Let's suppose that we have a Documentation folder inside the ConsoleApplication1 sample, which we might be able to extend from WIX later. We have to define this as the following:
<ItemGroup> <ConsoleApplication1Files Include="C:\temp\ConsoleApplication1\**" /> <WixFolderInclude Include="ConsoleApplication1Folder"> <SourceFiles>@(ConsoleApplication1Files)</SourceFiles> <RootPath>C:\temp\ConsoleApplication1</RootPath> <ParentDirectoryRef>Dir_Samples</ParentDirectoryRef> <DeterministicFolders>Documentation</DeterministicFolders> </WixFolderInclude></ItemGroup>
As a result, the ID for the Documentation's <Directory> element will be: Dir_ConsoleApplication1Folder_Documentation, so we can extend it from our Product.wxs:
<DirectoryRef Id="Dir_ConsoleApplication1Folder_Documentation"> <Component Id="C_AdditionalFile" Guid="5D8142C1-..."> <File Name="AdditionalFile.txt" Source="C:\Temp\AdditionalFile.txt" /> </Component></DirectoryRef>
In the attached ZIP file, you will find the WixFolderInclude.targets file, and also the sample that I have used here to demonstrate the features (without the silly ConsoleApplication1 and WebApplication1 folders). Feel free to use them!
I hadn't touched the topic of web service proxy generation for a long time, but in order to fine tune our new message contract generation framework for Genome, I had to check it out once more.
My concrete problem is very simple: I want to generate a proxy for a web service, but instead of generating some DTO types based on the wsdl, I would like to use my DTO classes that are already implemented (I know that the wsdl-generated ones are just fine, but mine are a little bit better).
The old solution was to let Visual Studio generate the proxy code, and remove the shared type from it. And hope that you don't have to update it too often, because you will have to do this again. It seems that with the web service proxy there are no real improvements. Although wsdl.exe has some nice settings, like /sharetypes, you cannot invoke it from the "Add Web Reference" dialog. So you have to complicate the development workflow anyway. I wonder why MS did not implement a backdoor, by which I could provide additional wsdl.exe parameters…
The better news is that the WCF client generator can also generate clients for web services. And in the "Add Service Reference" dialog, you can even configure it to reuse types from existing assemblies, if they are referenced in the client project. Super! This is what I wanted. But it does not work :-( … At least not if the service is an ASMX web service (it seems to work fine for WCF services). It still generates my DTO classes.
I have played a lot with it. It seems that the problem is that it does not recognize the matching DTO class, because it is annotated with XML serializer attributes ([XmlType], etc.) and not with WCF attributes. Indeed, if I attribute the class with [DataContract] and [DataMember] attributes, it finds it! However, there is a checking mechanism in the client generator that can check whether the reused type matches the wsdl definition. And it is this that seems to fail, even if I apply exactly the same attributes as it would generate. I have looked around, and it seems that this checking mechanism might fail even for WCF classes.
This is a trap. There is a validation framework that provides false validation errors and cannot even be switched off. So I'm still exactly where I was 5 years ago: manually removing the generated types from reference.cs.
Posted by Gáspár
No, this article does not nag about some code I've seen that misuses new features. This is how I did it - on purpose.
I've always disliked the way I usually set up data in the database for testing: recreate the database, create the domain objects, setting all the necessary properties, commit the context. Take this code for example:
DataDomainSchema schema = DataDomainSchema.LoadFrom("SomeMappingFile");
DataDomain dd = new DataDomain(schema, connStr);
using (Context.Push(ShortRunningTransactionContext.Create()))
Customer tt = dd.New<Customer>();
tt.Name = "TechTalk";
RootProject tt_hk = dd.New<RootProject>();
tt_hk.Name = "Housekeeping";
ChildProject tt_hk_hol = dd.New<ChildProject>();
tt_hk_hol.Name = "Holiday";
ChildProject tt_hk_ill = dd.New<ChildProject>();
tt_hk_ill.Name = "Illness";
RootProject tt_g = dd.New<RootProject>();
tt_g.Name = "Genome";
ChildProject tt_g_dev = dd.New<ChildProject>();
tt_g_dev.Name = "Development";
ChildProject tt_g_mnt = dd.New<ChildProject>();
tt_g_mnt.Name = "Maintenance";
What I dislike in this is the 'setting all the necessary properties' part. Part of it is that it's hard to follow the hierarchy of the objects.
The other is that I'm lazy.
Even if I'm typing with considerable speed - and keep pressing ctrl+(alt)+space and let ReSharper do the rest - I still hate it for its repetitiousness. I always wanted to have something like ActiveRecord's Fixtures in Rails - but I never had the time to implement it. Yeah, typical excuse, and that's how we usually lose development time even in the short run, so I know I'll have do it the next time I need to create test data.
Sure, I could always create builder methods for every type to handle, passing in the property values and collections etc, but even creating those is yet another repetitious task. I always longed for some more 'elegant' write-once-use-everywhere kind of framework. So when I read this post, I thought, maybe I can get away with writing a simple, but usable enough, initializer helper extension. Here's the resulting initializing code:
using (Context.Push(ShortRunningTransactionContext.Create()))
Name => "TechTalk",
RootProjects => new Project[] {
Name => "Housekeeping",
ChildProjects => new Project[] {
dd.Init<ChildProject>().As(Name => "Holiday"),
dd.Init<ChildProject>().As(Name => "Illness")
Name => "Genome",
ChildProjects => new Project[] {
dd.Init<ChildProject>().As(Name => "Development"),
dd.Init<ChildProject>().As(Name => "Maintenance")
Prettier to the eye - but unfortunately, it's still not practical enough. For one thing, it's easy to represent a tree this way, but it still doesn't offer a solution for many-to-many relations. That's a lesser concern though, and I have ideas for overcoming this (but haven't done it so far due to lack of time, again). A greater problem is that it's not type safe: the parameter names of the lambdas (Name, RootProjects, ChildProjects) are just that - names, aliases; they are not checked during compile time. Even as a dynamic typed language advocate, I don't like too much dynamic behavior in statically type languages - that usually results in little gain if any, while losing their advantages, even 'developer-side' ones, like refactoring or intellisense support.
So, no conclusions there - I don't know which way I prefer yet. It seems that I really will have to go on and write some xml-file based initialization library (which will share some of the abovementioned problems of the non-static languages, of course, but renaming those properties in the config by hand which you just modified in the code at least feels a bit more normal).
Still, if you're interested, here's the extension for doing the job:
public static class DataDomainInitializerExtension
public static DataDomainInitializer<T> Init<T>(
this DataDomain dd, params object[] parameters)
return new DataDomainInitializer<T>(dd.New<T>(parameters));
public class DataDomainInitializer<T>
private readonly T target;
public DataDomainInitializer(T obj)
this.target = obj;
public T As(params Expression<Func<string, object>>[] expressions)
foreach (Expression<Func<string, object>> expression in expressions)
object value = GetValue(expression.Body);
string key = expression.Parameters[0].Name;
PropertyInfo property = typeof(T).GetProperty(key,
Type collectionType = GetCollectionType(property.PropertyType);
if (collectionType != null)
CopyCollection(property, collectionType, value);
property.SetValue(target, value, null);
return target;
private void CopyCollection(
PropertyInfo property, Type collectionType, object collection)
object targetProperty = property.GetValue(target, null);
MethodInfo addMethod = collectionType.GetMethod("Add");
foreach (object enumValue in (IEnumerable)collection)
new object[] { enumValue });
private static Type GetCollectionType(Type type)
foreach (Type @interface in type.GetInterfaces())
if (@interface.IsGenericType &&
== typeof(ICollection<>))
return @interface;
return null;
private static object GetValue(Expression expression)
ConstantExpression constExpr = expression as ConstantExpression;
if (constExpr != null)
return constExpr.Value;
return (Expression.Lambda<Func<object>>(expression).Compile())();
Posted by Attila.
With Genome, you can map standard 1:n and n:m collections for foreign-key/association table database patterns out of the box by using Collection<T> and <OneToManyCollection/> or <ManyToManyCollection/>.
Compared to arbitrary relationships, which can also be mapped with Genome by using Set<T> and a query, Collection<T> offers the following additional functionality:
However, for n:m collections, where the association class is annotated with additional values (besides the foreign keys), the standard Collection<T> mapping does not fit.
To provide better support for those mapping scenarios, I have created a Dictionary-like implementation for annotated many-to-many associations, where we can build the functionality on the existing collection support.
I will use a simple domain model to present the idea. Let's say we have Departments and Employees in our domain. An employee can work in multiple departments, and a department can have more than one employee. This classic many-to-many association is annotated with a job description. The job description is encapsulated in a struct called Job.
So the logical view looks like this:
In the database, we represent this kind of association with an association class/table as follows:
The task is to implement the Department.Employees property, which represents the annotated n:m relation in a consistent way.
In my opinion the best representation for Department.Employees is an IDictionary<Employee, Job>. It is ideal because the employees must be unique within the collection, and the annotation data can be accessed if you additionally specify an Employee (index into the dictionary with that employee). Note that this representation is only possible if the annotation can be represented with a single typ; however, you can encapsulate the annotations with a struct or class to achieve this at any time. You can use the <EmbeddedStruct/> mapping feature to map this struct on the EmployedAs class.
First we have to map the one-to-many collection (Department.EmployedAsCollection):
protected abstract Collection<EmployedAs> EmployedAsCollection { get; }
<Member name="EmployedAsCollection">
<OneToManyCollection parentReference="Department"/>
We will wrap this collection with a dictionary implementation to represent the annotated association. I have created a helper class AnnotatedManyToManyDictionary that carries out all necessary transformations. This strongly typed helper needs 4 generic parameters, as you have to specify the association class (TAssoc=EmployedAs), the class owning the collection (TOwner=Department), the "other side" of the association (that is, the key in the dictionary, TKey=Employee) and the annotation that is the value in the dictionary (TValue=Job). Basically, you have to wrap the collection with this helper:
public IDictionary<Employee, Job> Employees
return new AnnotatedManyToManyDictionary<EmployedAs, Department, Employee, Job>
(this, EmployedAsCollection, EmployedAsDepartmentEmployeeJobAccessor.Instance);
The helper class manages the underlying one-to-many collection and the association items to provide the required behavior. As you probably noticed in the constructor call, it still needs a little bit of help. You have to pass a strategy that "knows" how to get and set the key and value properties of the association item. In the current example, the EmployedAsEmployeeJobAccessor strategy knows how to get and set the Employee and Job properties on an EmployedAs object. Currently you have to write this piece of code to make that work:
private class EmployedAsEmployeeJobAccessor :
IAnnotatedManyToManyDictionaryAssociationAccessor<EmployedAs, Employee, Job>
public static readonly EmployedAsEmployeeJobAccessor Instance =
new EmployedAsEmployeeJobAccessor();
public Employee GetKey(EmployedAs assoc)
return assoc.Employee;
public void SetKey(EmployedAs assoc, Employee key)
assoc.Employee = key;
public Job GetValue(EmployedAs assoc)
return assoc.Job;
public void SetValue(EmployedAs assoc, Job value)
assoc.Job = value;
Having done this, you can easily iterate through the employees in a department:
Department dep = GetSomeDepartment();
foreach(Employee e in dep.Employees.Key) { ... }
You can also iterate through the association elements to retrieve the associated employees of a department along with their job:
foreach(KeyValuePair<Employee,Job> in d1.Employees) { ... }
The job of an employee now depends on the associated department. The indexer of the employees collection takes an associated employee and looks up the job annotated to association:
Employee emp = GetSomeEmployee();
Job assignedJob = dep.Employees[emp];
Similarly, the job of an employee can be set for a specific department association:
dep.Employees[emp] = assignedJob;
Finally, when associating an employee to a department, the job annotation has to be specified as well:
dep.Employees.Add(emp, assignedJob);
The first limitation is performance with larger collections.. The current implementation uses a linear search for looking up the employee key in the collection, which can cause a performance hit in larger collections when adding or removing items or getting an item's annotation (using the indexer). The reason for this is that I didn't want to replace Genome's internal representation of 1:n collections with a dictionary implementation.
The second limitation is that you need to manually code the helper strategy for getting and setting the annotation value in the association items.
Based on your feedback, we might implement this as a native mapping feature in an upcoming Genome release, thus resolving both limitations described.
Please find the source code for the example described above attached to this article.
Posted by TZ.
© Copyright 2020, TechTalk


text:
Restricted substances by Annex XVII to REACH Regulation
The list of restrictions contains those substances (on its own, in a mixture or in an article) for which manufacture, placing on the market or use is limited or banned in the European...
HTML (9346 views) (824 Downloads)
REACH registration statistics
This data shows the number of registrations received from the 28 EU Member States and from the European Economic Area countries Norway, Iceland and Liechtenstein. These statistics will...
Excel XLSX HTML (1550 views) (111 Downloads)
Visualise this dataset with REACH registration statistics - interactive infographic
List of nano-pigments on the EU market
As part of a study commissioned by the European Union Observatory for Nanomaterials (EUON) to investigate the safe use of nano-sized pigments in consumer products, as well as their safety...
HTML (186 views) (8 Downloads)
Catalogue of nanomaterials used in cosmetics
The European Commission published a catalogue of all nanomaterials used in cosmetic products in the EU in July 2017, and the catalogue is regularly updated. Many of the substances listed...
HTML (132 views)
Persistent Organic Pollutants
The POPs Regulation bans or severely restricts the production and use of persistent organic pollutants in the European Union. ECHA supports the identification of new POPs substances. It...
HTML (113 views)
Search for nanomaterials on the EU market
Here you can search for nanomaterials that are currently on the EU market. The data is collected from publicly available information from REACH registrations, the Cosmetics Regulation as...
HTML (88 views)


text:
Home > Glossary > Disciplines of Study [DoS] > Acoustics > Noise > English definition
Sunday 2 January 2005, by
In contrast to most 'musical' sounds, which have a definite pitch and a predominantly harmonic spectrum, noise consists of a theoretically infinite and continuous range of frequencies. The waveform consists not of regular periodic cycles but of random fluctuations of amplitude. In the present context, the bandwidth of the noise may be considered limited to that of human hearing. As will be seen, it is possible to speak of noise limited to a variety of bandwidths.
It is usual to use analogies to visible light when discussing different types of noise. Thus, noise, which has equal intensity at all frequencies, is referred to as 'white noise'. Because the human ear is more sensitive to high than to low frequencies, white noise will be heard as a high hissing sound.
By passing white noise through a filter, different 'colours' can be obtained. 'Pink noise' results if white noise is passed through a mildlow-pass filter. Whereas white noise has equal power at all frequencies, pink noise is defined as having equal power in each octave band (corresponding more closely to the response of the ear). Thus the power varies inversely with frequency - for this reason it is often referred to as '1/f noise'. Similarly 'red noise' is referred to as '1/f (Squared) noise', the high frequencies being much more attenuated than in pink noise. (Source - Richard Dobson (1992). A Dictionary of Electronic and Computer Music Technology. Oxford University Press.)


text:
We use the set of manually curated human reactions to electronically infer reactions in eighteen evolutionarily divergent eukaryotic species for which high-quality whole-genome sequence data are available, and hence a comprehensive and high-quality set of protein predictions exists. These species include the laboratory mouse and rat, the nematode C. elegans, budding and fission yeasts, and two plants. The estimated success rates of our orthology inference strategy can be stated as 'the percentage of eligible reactions, defined in step 2 below, in the current human data set for which an event can be inferred in the model organism. By this measure, success rates range from 83.9% for the laboratory mouse to 6.9% for the protozoan P. falciparum.
Electronic inference proceeds in four steps:
- Protein homology data were obtained from Ensembl Compara. Briefly, this method is based on the construction of gene trees, using the longest protein translation for every Ensembl gene, for all species included in the Compara database. Homologues are deduced from these trees. The method is described in more detail in EnsemblCompara GeneTrees: Analysis of complete, duplication aware phylogenetic trees in vertebrates, and Vilella et al., Genome Research, 2008. For the purpose of inferring homologous events in Reactome, we use the Core Compara database, containing vertebrate species, and the Pan Compara database, containing a wider spread of species, available from Ensembl Genomes.
- All human reactions in the Reactome knowledgebase involving one or more proteins are eligible for electronic inference, with two exceptions. Reactions that were themselves inferred based on data from the model organism, and reactions involving species in addition to human (e.g., HIV infection of human cells) are excluded from electronic inference. Eligible reactions are checked to determine whether each involved protein has at least one homologous protein (HP) in the model organism. If a human reaction involves a complex, at least 75% of the accessioned protein components of the human complex must have HPs in the model organism.
- For each reaction that meets these criteria, an equivalent reaction is created for the model organism by replacing each human protein with its model organism HP. If a human protein corresponds to more than one model organism HP, a DefinedSet called 'Homologues of …' is created, with the model organism HPs as members. For human proteins that lack a model organism HP but that are included in complexes inferred due to the 75% threshold rule, placeholder model organism entities are created.
- If this analysis generates reactions in the model organism corresponding to any of the steps of a human pathway, then the pathway event is also inferred for the model organism.
These electronically inferred reactions are predictions based on a number of assumptions. Most basically, we assume that if we can find model organism HPs corresponding to all proteins involved in a human reaction, then the proteins mediate the same reaction in the model organism. This may not be true. On the other hand we may miss a truly homologous reaction in the model organism because it is mediated by structurally divergent proteins and the Compara strategy failed to identify them. Similarly, complexes sharing less than 75% homologous subunits between species may nevertheless continue to perform the same function. The electronically inferred reactions presented in Reactome are thus not data, but hypotheses useful to direct the design of confirmatory experiments.


text:
commission(redirected from in commission)
Also found in: Dictionary, Thesaurus, Medical, Financial, Idioms, Encyclopedia.
n. 1) a fee paid based on a percentage of the sale made by an employee or agent, as distinguished from regular payments of wages or salary. 2) a group appointed pursuant to law to conduct certain government business, especially regulation. These include from the local planning or zoning commission to the Securities and Exchange Commission or the Federal Trade Commission.
commission(Act), noun accomplishment, actualization, actuation, attainment, carrying out, completion, consummation, discharge, dispatch, doing, effecting, effectuation, enactment, enforcement, execution, exercise, exercising, fruition, fulfilment, implementation, inflicting, infliction, making, mandatum, operation, realization, transaction
Associated concepts: commission of crime
commission(Agency), noun advisory group, appointed group, board, board of inquiry, body of commissioners, body of delegates, body of deputies, bureau, cabinet, consultants, convocation, council, delegation, deliberative group, embassy, executive committee, investigating committee, planning board, representatives, standing committee, trustees
Associated concepts: advisory body, Federal Trade Commission, Municipal Commission, Public Service Commission
commission(Fee), noun allotment, allowance, bonus, compensation, consideration, defrayment, dividend, earnings, emolument, extra commensation, increment, interest, pay, pay-off, payment, percentage, percentage compensation, portion, proceeds, profit, recompense, reimbursement, remuneration, return, reward, salary, share of profits, stipend, wage
Associated concepts: broker's commission, commission merchant, compensation, fees, finder's commission, profits
See also: act, agency, allow, appoint, assign, assignment, authorize, bestow, board, brokerage, bureau, charge, command, commit, committee, constitute, delegate, delegation, deputation, designate, designation, detail, dictate, direction, discharge, duty, earnings, embassy, employ, employment, empower, engage, entrust, establish, hire, induct, infliction, instruction, interest, invest, let, mission, nominate, obligation, performance, permit, post, retain, share, task, transaction, undertaking, vest, warrant
COMMISSION, contracts, civ. law. When one undertakes, without reward, to do
something for another in respect to a thing bailed. This term is frequently
used synonymously with mandate. (q.v.) Ruth. Inst. 105; Halifax, Analysis
of the Civil Law, 70. If the service the party undertakes to perform for
another is the custody of his goods, this particular sort of, commission is
called a charge.
2. In a commission, the obligation on his part who undertakes it, is to transact the business without wages, or any other reward, and to use the same care and diligence in it, as if it were his own.
3. By commission is also understood an act performed, opposed to omission, which is the want of performance of such an act; is, when a nuisance is created by an act of commission, it may be abated without notice; but when it arises from omission, notice to remove it must be given before it is abated. 1 Chit. Pr. 711. Vide Abatement of Nuisances; Branches; Trees.
COMMISSION, office. Persons authorized to act in a certain matter; as, such a matter was submitted, to the commission; there were several meetings before the commission. 4 B. & Cr. 850; 10 E. C. L. R. 459.
COMMISSION, crim. law. The act of perpetrating an offence. There are crimes of commission and crimes of omission.
COMMISSION, practice. An instrument issued by a court of, justice, or other competent tribunal, to authorize a person to take depositions, or do any other act by authority of such court, or tribunal, is called a commission. For a form of a commission to take. depositions, see Gresley, Eq. Ev. 72.


text:
British Columbia is no petro state. So why do our political leaders insist that we are a global energy power?
At the University of Calgary last month, Premier Christy Clark boldly asserted that B.C. could one day export four trillion cubic feet of natural gas per year, an amount that would put us on par with the output of Alberta's oilsands industry.
Clark also said that over the next 30 years such exports "could add over a trillion dollars" to our province's gross domestic product.
These sound like impressive numbers. But drill into them a bit, and they appear to be overstated, which raises critical questions.
What does exporting four trillion cubic feet of gas per year from B.C. actually mean, when viewed against what we have? What would the economic, energy security and climate consequences be of producing all that gas and more?
Consider the following facts.
Last year, B.C. produced a record 1.2 trillion cubic feet of natural gas — among the most water-depleting and energy-draining gas on earth, due to the deployment of highly controversial fracking technology.
The bulk of that gas went to Alberta to assist in the most water-depleting and energy-draining oil production on Earth. The next biggest slice went to the United States. What was left we used here in the province.
Presumably, we would not simply shut off the taps on these markets in the event that five new liquefied natural gas (LNG) terminals are built on our coast, and we begin shipping four trillion cubic feet of our gas to China, Japan and elsewhere. The government's energy policies would therefore see gas extraction rates quintuple in northeastern B.C. — and probably a whole lot more because natural gas will likely be burned to power all those LNG plants.
What not enough of us have asked the government about is what such policies mean in terms of depleting our non-renewable fossil fuel resources and undermining our ability to meet our legislated greenhouse gas emissions reduction targets.
Now is the time to do so. Here's why.
According to British Columbia's Oil and Gas Commission, our current reserves of natural gas total roughly 33 trillion cubic feet. Based on our premier's projections of 4 trillion cubic feet per year of gas exports, we'd drain our entire reserves in just 8 years, or less if we continued to supply our own needs and those of our existing customers.
Now the likelihood is that we have far more gas. Estimated total resources for B.C. exceed 1,200 trillion cubic feet. But even optimistically assuming we can successfully extract one quarter of those resources, we'd be completely out of gas in 75 years — that is if we exported it all and left nothing for ourselves or for our neighbours.
Speaking of neighbours, Alberta's Energy Resources Conservation Board projects a 35 per cent decline in its own gas production over the next decade. And according to Canada's National Energy Board, total Canadian natural gas production is down nearly 20% today from its peak in 2002.
The only western Canadian jurisdiction whose reserves and production show growth is here in B.C. And our elected leaders' vision is that we rush whatever we have out of the country.
Premier Clark and B.C. Energy Minister, Rich Coleman, call their gas export plans a "strategy". Their choice of wording is an insult both to the English language and to basic economics.
Billions of dollars will be needed to build gas pipelines to our coast, tens of billions more to build the liquefied natural gas plants required to process our gas so that it can be loaded onto ocean tankers.
Yet according to British Petroleum, 17 countries have more natural gas at their disposal than does Canada. In the global "foot race" — Minister Coleman's words — to supply our gas to Asian markets, we are at an extremely disadvantageous position. Worse, China, one of the proposed destination points for our gas, may be sitting on a potential motherlode of its own gas supplies.
Recently, the political war of words over the proposed Enbridge oil pipeline has ratcheted up between Premier Clark and Alberta Premier Allison Redford. What we desperately need instead is a broader national dialogue focused squarely on two things — domestic energy security and climate change. There is only so much fossil fuel to go around. And the climate implications of burning it are well known.
It's time to behave like responsible owners of those limited resources, not oil and gas pitchmen.
Dave Hughes is a geologist who has studied Canada's energy resources for more than three decades with NRCan's Geological Survey of Canada. He is president of Global Sustainability Research Inc.Ben Parfitt is a resource policy analyst with the BC office of the Canadian Centre for Policy Alternatives and author of Fracking Up Our Water, Hydro Power and Climate: BC's Reckless Pursuit of Shale Gas.