text:
Fatal parasail accidents renew calls for rules
MIAMI BEACH, Fla. — Soaring high above the ocean, tethered to a boat, a parasail ride is at once exhilarating and peaceful, even quiet. But every year, there are accidents.
The Parasail Safety Council, which tracks injuries and deaths nationwide, reports more than 70 people have been killed and at least 1,600 injured between 1982 and 2012, out of an estimated 150 million parasail rides during those 30 years.
That's a casualty rate of about one per 90,000 rides. In comparison, the chance of being seriously injured at an amusement park is about one in 9 million rides, according 2010 data from the International Association of Amusement Parks and Attractions.
Despite parasailing's inherent risk, few federal or state safety regulations exist for it. In Florida, which has by far the largest number of parasail operators at about 120, repeated efforts to enact new rules following fatal accidents have gone nowhere. Florida is seen by safety proponents as a national bellwether because of parasailing's popularity in a state highly dependent on tourist dollars.
The lack of safety regulations frustrates Shannon Kraus, mother of two girls who crashed into a Pompano Beach hotel roof in 2007 when their parasail line snapped during a storm. One of the girls, 15-year-old Amber May White, later died of her injuries, while her sister Crystal, then 16, has had a long road to recovery from head injuries.
"Nobody has listened to me from day No. 1," Kraus said. "I've just been shoved aside. I've kind of been ignored and I'm pretty angry about that."
Crystal White, now a mother of two herself and a massage therapist, said most people who sign up to parasail have little idea it's less regulated than the average carnival ride.
"They just need to know that if they go up, and something bad happens, there's nothing they can do about it, because there are no laws, or rules, or regulations," she said.
Indeed, five years after the girls' accident just off the same beach, a Connecticut woman died when her harness gave way and she fell about 150 feet into the ocean. The Aug. 15 death of 28-year-old Kathleen Miskell has prompted the first National Transportation Safety Board investigation into a parasailing fatality. Safety advocates hope Florida lawmakers will give the issue a fresh look.
Mark McCulloh, who runs the Parasail Safety Council, said in the U.S. and its territories about 620 vessels offer parasail rides to about 4 million people a year. He said only New Jersey and Virginia have relatively comprehensive regulations, while the Federal Aviation Administration and U.S. Coast Guard oversee some limited aspects of the activity.
In Florida, state Sen. Gwen Margolis, a Democrat, said the proposed regulations would include inspections of parasailing equipment, new rules restricting rides during certain weather conditions and prohibitions against parasailing near fixed objects such as power lines. The proposal would also require operators to buy insurance.
Margolis said past efforts have run into opposition by parasail operators and a general anti-regulation attitude among many lawmakers in the Republican-controlled Florida Legislature.
"When you get onto anything that's recreational, you assume that somebody's inspected it and everything's OK. And you can't assume that," she said.
Most parasail operators, however, are willing to submit to safety regulations as long as they are sensible, said Dan Breitenstein, who runs Miami Beach Parasail.
"If you have someone who has never been on a parasail boat or doesn't know the workings of it, if they're making up rules that would have little effect on what we do" it wouldn't make sense, Breitenstein said. "There's definitely things we can do."
People who sign up for Miami Beach Parasail generally pay about $75 for a 15-minute ride that can take them as high as 350 feet in the air. They sit in swing-like harnesses attached to a tow bar, which is connected by ropes to the kite-like parasail above and a winch in the boat below.
As the 33-foot "High Anxiety" boat moves across the water, the parasail passengers are slowly lifted into the air and the line is let out. After the ride, the boat is slowed gradually as the line is brought in so parasailors land back on the boat on their feet.
It all seems fairly safe, and you can't beat the view, which on one recent day featured an umbrella-dotted South Beach and, beyond, its famed Art Deco hotel and entertainment district, with the greenish-blue Atlantic Ocean below.
The lack of regulation, however, means no one is looking over the operator's shoulder to make sure ropes damaged by sun and salt water are replaced. There are also little or no rules regarding age limits or experience for "spotters" who observe the riders.
And there's nothing beyond common sense to prevent an operator for taking people up windy weather, which many people say is the one variable that can most often lead to an accident.
Breitenstein, who has radars on his boats, said he maintains a five-mile buffer from any nearby bad weather. But he said in Florida, storms can develop quickly offshore — and sometimes operators might be tempted to take a little risk to make more money.
"Weather is our biggest, toughest thing," he said. "Taking chances, that's a bad habit to get into."
Follow Curt Anderson on Twitter: http://twitter.com/Miamicurt .


text:
Office Phone:
View Phone Number
(732) 528-3700
View Phone Number
(732) 528-3833
Ward Wight Sotheby's International Realty
208 East Main StreetManasquan, NJ 08736
View my Additional Website
(ARA) - So it's time to move and you're excited, but it's a lot of work getting all your stuff from one location to the next. Hiring a moving company can help reduce the stress of moving and professionals help make sure your items get to wherever you are going safely.
So how do you know what you should look for when hiring a moving company? After all, you want to hire someone you trust with your possessions. There are some things every person should consider when hiring a company to move their items.
1) Research It's smart to check out several companies before choosing the right one for you. Web sites like MovingGuru.com are quick and easy ways to connect you with a variety of moving companies in your area. Instead of having to call various companies for quotes, simply fill out the form on the site and up to six companies will call or e-mail you. After receiving bids you can book the best deal.
2) License and Insurance Make sure the mover you use has a license and comprehensive insurance. You can opt for insurance coverage that will protect the worth of all your belongings should something happen. Ask about the details.
3) Extra Fees Depending on what you need, you might be required to pay extra fees. Most moving companies charge based on weight, but under special circumstances, they can add charges that can cost you a lot. Remember to ask about what you could be charged for extra services so you know what to expect.
4) Complaints Checking out complaint registries are a good place to find out if the company has any major issues. Search online for reviews or check the Better Business Bureau. You can also ask the company if they have anyone you can contact that would recommend them.
A good moving company will have a presence in your area, will visit your home prior to your move, and will answer any questions you might have before signing or paying for anything.
Don't get stuck with an unprofessional moving company and a high bill. Visit www.MovingGuru.com to fill out a simple form that lets a variety high-quality moving professionals come to you.
Copyright © 2008, ARAnet, inc.

subset: commoncrawl


text:
Modern-Day Puritans Want to Ban Things That Make Us Happy
The government bans fun, not danger.
People say America is a free country. But what if you want to drink, have a cigarette or make a bet? Government often says "no" to protect us from ourselves.
It's as if the government is still run by the Puritans who settled this land four centuries ago. They said pleasure and luxury are sinful.
Today's government has a better argument when it seeks to restrict activities that might harm others, but I notice that even then, it often focuses more on things that upset modern-day Puritans.
Drinking and driving can be fatal. But government data show that sleeplessness and driving are just as deadly. Having kids in the back seat, looking at GPS map instructions, fiddling with the radio and eating while driving are often deadly, too.
But sleeplessness doesn't seem as decadent and irresponsible as drinking. Nor is there an easy way for police to test for such discretions—no breathalyzer test for excessive radio tuning.
Why is the DUI test all about alcohol level, rather than behavior? Government keeps lowering legal blood-alcohol levels—recently from .10 to .08—and now they want to lower it to .05. But some people are good drivers even after a drink or two. It would be better to punish people for "reckless" driving.
Alcohol-related driving deaths are down. Groups like MADD (Mothers Against Drunk Driving) credit tougher DUI laws, but it's not clear that they are right.
Maybe people are simply more aware of the dangers, thanks to publicity from groups like MADD. Safer car designs helped, too. Non-alcohol-related driving deaths are also down.
Stats that some cite to claim alcohol is the cause of a third of highway accidents are misleading. That just means that a third of the people had alcohol in their systems; it doesn't necessarily mean alcohol caused the accident.
I don't suggest that drinking and driving is safe or smart. But the puritanical obsession with drinking distracts us from other ways we could make driving safer.
At least DUI laws seek to protect people from others. But government puritans go well beyond that, banning activities that harm only the individual engaged in them—like gambling.
Polls show 70 percent of you support the current ban on Internet gambling.
Why? It's true, for some people, gambling becomes addictive. Some wreck their lives. But for most people, gambling is entertainment, practice in using strategy and an excuse to socialize. A little risk is fun. And the laws don't stop the activity. They drive it underground, where it's run by criminals.
If we banned every activity that had the potential to become addictive, we'd have to ban fatty foods, sex, alcohol and investing in the stock market. Life means risk.
Sometimes puritans want to ban things without any evidence that the activity is harmful. After every mass shooting, someone wants to tax, or ban, violent video games.
Yet violent offenses by youth fell by more than half over the past two decades, while video game sales doubled. If there's a causal relationship, maybe playing video games prevents kids from behaving violently.
Japan spends much more on violent video games than the U.S., but its crime rate is much lower. Maybe the Japanese get it out of their system through make-believe? I don't know. But I do know that a lack of evidence rarely stops the puritans.
The puritanical panics of today may look silly someday. In the 1950s, a psychiatrist testified that Superman comic books inspire juvenile delinquency.
After hearing about those moral panics, you might feel like relaxing with a cold beer. But don't try buying one from a convenience store in Indiana. The state requires that the beer be sold warm.
In theory, warm beer will discourage drinking on the road.
I doubt that such laws help. Perhaps puritanical laws don't have to make sense. They just have to leave us feeling righteous because we've done something to crack down on bad behavior.


text:
Silvio Calabi: Bullish on the Taurus
There are still herds of ancient Ford Tauri from the 1980s and '90s roaming the American hinterlands, their once-daring, worn-bar-of-soap styling looking more and more like the automotive Lava Lamp. That original Taurus took Ford into front-wheel drive and better, more fuel-efficient aerodynamics and became a best-seller. But by the naughts Ford — perhaps distracted by the profit margins of pickup trucks and SUVs — was alternately ignoring its bread & butter sedan or brutally slashing its costs, content and, ultimately, value. The Taurus became a rental car and then went all but extinct.
Today's Taurus is a different beast. Maybe the old name provides comfort and familiarity, but underneath the badge is a highly credible biggish car — comfortable, roomy, modestly chic, and not even unrewarding to drive. Today's Taurus could serve as the default American sedan, the price-value yardstick against which others are measured. So if your new autobahn-bred import costs twice as much, it had better be twice as good.
There are four Taurus variants. The standard engine in three of them — SE, SEL, Limited — is a V-6 now tuned up to 288 horsepower and 254 lb-ft of torque. Optional is a smaller turbocharged EcoBoost 4-cylinder engine rated for 240HP and 270 torques (on premium gas). EcoBoost 4 drivers won't feel undergunned off the line, yet they should gain about three more miles per gallon, to 22 mpg in city driving and 32 on the highway. This with front-wheel drive only; AWD is not available with the 4-cylinders.
The enthusiast's Taurus, the $40,000 SHO (Super High Output), gets the EcoBoost V-6 — 365HP, 350-lb-ft — plus up-rated suspension and brakes and a lot of toys. This is more power than Ford wants to route through the front wheels alone, so the SHO is all-wheel-drive only.
Ford has tweaked its stability-control electronics to what it now calls Curve Control, and made this standard on all Tauruses: If the car decides its speed is too great for a particular corner, Curve Control automatically cuts the throttle and, if necessary, squeezes the brakes. All Tauruses also get the latest in fuel-economy wizardry: shutters behind the grille that automatically open, to allow cooling air to the engine, or close for better aerodynamics at speed.
Our example was a mid-range SEL with the standard V6, all-wheel drive and a sticker price of $34,445. It was equipped with a good but basic suite of features that included projector-beam headlights and bright, fast-reacting LED taillights, dual automatic heating and cooling zones, a compass and trip computer, wide-angle inserts in the (heated) side mirrors, pushbutton ignition, and radio and cruise-control switches on the steering wheel.
Unlike most press cars — usually stuffed with pricey gadgets — it was equipped the way a thoughtful and cost-conscious buyer might do it. The sole add-ons were heated leather seats for $1,495 and Equipment Group 202A ($3,795), which adds Sync voice-activation for music, telephone, climate control, navigation, news and incoming text messages; a rear-view camera and backup sensors; and adjustable pedals, a computer touchscreen and pushbutton remote starting.
I would have ordered two more options that I've come to appreciate: blind-spot monitors — Ford's now can also detect traffic crossing behind the car as it backs out of a driveway or parking slot — and interactive cruise control. (Basic cruise control won't automatically adjust its speed in traffic.)
The standard 6-speed automatic transmission has a Sport setting and a manual shift button, but they're hardly necessary. This particular SEL fairly shouts "company car!" As such, it is a quiet, relaxing place to do business and the miles pass by almost unnoticed.
For many years, much Detroit iron left the clear impression that the makers were trying to enhance the corporate bottom line by delivering as little value as possible for the buyer's dollar. We know how that worked out. For this 6th-generation Taurus, however, it seems the design and engineering teams got together and decided to build something they were proud of and we'd be pleased to own. Every car (and nearly every SUV) now wearing the blue oval feels like a solid check mark in the plus column.
Silvio Calabi reviews the latest from Detroit, Munich, Yokohama, Gothenburg, Crewe, Seoul and wherever else interesting cars are born. Silvio is a member of the International Motor Press Association whose automotive reviews date back to the Reagan administration. He is the former publisher of Speedway Illustrated magazine and an author. Contact him at email@example.com.


text:
Development of Open Source tools
|Libpano has migrated to a Mercurial Repository on SourceForge. If you find outdated references to Subversion, please update.
|Hugin's tracker has moved from SourceForge to Launchpad, and so have the trackers for Enblend and Panotools. If you still find references to the SourceForge tracker in these pages, it may be outdated. Please fix if you can. Most pages have been fixed for Hugin's move from a Subversion to a Mercurial repository (2010-May-16) but if you find a reference to SVN, it may be outdated or it may be related to Panotools that has not moved. Please fix if you can.
Panorama Related Open Source tools
Why contribute?
The above tools are free for you (and every other user), because volunteers have contributed their skills and time. They provide immense value to the whole community. They provide value to you, don't they? If they do, please consider contributing something back.
How to contribute?
Join the hugin-ptx mailing list to find out what is going on at the moment and how you can help.
If you don't have time, you are most likely a busy professional. You can donate money to Hugin, Enblend/Enfuse on their project pages through Sourceforge.
At the time of updating this text (6-Mar-2011) the building process of Hugin is robust and there are more and more people mastering it on the different platform. The 2011.0 release cycle is well underway. Beyond that, a few exciting features such as a python scripting interface are in line for future releases.
Don't be afraid of failures in the building process
- You may encounter errors when following the build processes linked below is high. Don't worry such errors will not compromise your computer.
- The failure of the building process is actually your success! Every time you report such a failure, with as much detail as possible to how it came about, you are contributing to the progress toward a stable release.
- See also If you encounter errors, Fixing The Hugin Build.
If you are fluent in other languages than English, you can help translate Hugin. There's a Hugin translation guide to help you get started or help when you run into translation problems.
The release process introduced in 2009 has decoupled the development processes from the release process, avoiding artificial slow downs (trunk freezes).
Hugin uses an asynchronous development process based on Mercurial, which means that:
- the default branch never freezes, and committers can continuously add improvements to it.
- anybody can branch out development codelines on their local copy of the repository, and even publish that repository.
- usually developers will branch out to implement major changes or changes that will not be completed very soon; and builders will branch out to clean up releases; without disrupting the continuous flow of contributions.
- unlike in the previous Subversion repository, branches are no longer stored in different folders. Give them a meaningful name to distinguish release branches (version number) from development branches (feature being implemented / worked on).
- developers have write access to the official repository on Sourceforge and can push changes and branches to it. The project is very liberal in giving such write access - if you have something to contribute, mention it on hugin-ptx and chances are one of the admins will give you the necessary write rights.
- once a months, developers are polled as to whether it is worth issuing a release. if there is enough support and one person volunteers as release manager, that person branches out a release codeline from the default codeline. That release codeline is equivalent to a trunk freeze in traditional synchronous development. only bug fixes and translations should go into that codeline. Tarballs are to be released from release codelines only.
- If you are working on something big that requires multiple changes to complete, you're encouraged to start your own branch:
hg pull hg branch <YOUR_UNIQUE_BRANCH_NAME>
- If you are working on incremental improvements to the default branch, feel free to push them any time. There is no trunk freeze.
- You're encouraged to continue with your usual pace of bug fixing and development.
- To do things perfectly: commit all your changes to the default branch; and apply those that are bug fixes also to the current release codeline if the project is in the midst of a release cycle.
- The new thing about Mercurial (coming from Subversion): commit is to your local repository only. To avoid multiple heads, pull/update before committing; and remember to push your change from time to time so that others can test them / benefit from them / add value to them.
hg pull hg up hg ci hg push
- If you forget about it and commit only to one codeline, do not worry. The release manager takes responsibility to sync between the default branch and the release branch.
- Try not to add new features, particularly new strings, to the release codeline later in the release cycle.
- Generally same as development. For specifics see the translation guide.
Working through Hugin Trackers.
Clearing the tickets in the tracker is an iterative process critical to the release cycle. Feedback from tester is essential for this process. Please take the time to check if the older reports apply to a current snapshot and add new findings to the ticket.
We'll be releasing frequent snapshots until a release candidate emerges. This is an iterative process:
- Volunteers check the release-critical bugs listed in the bug tracker against the most recent snapshot. The most recent snapshot for is usually posted on the Hugin-PTX mailing list.
- Install the latest snapshot.
- Try to reproduce the bug on your system.
- If you find that the bug no longer occurs, chances are that it has been fixed. Close it (assuming you have the required access), or simply leave a note that it has been fixed (together with the exact version number and the system used for testing).
- If you reproduce the bug, leave a note to confirm that it is still actual. Note the SHA1 ID and the system used for testing. Post detailed instructions how to reproduce the crash. Provide a test case if you can.
- Add any comments you have to the ticket in the bug tracker. Let the community know you have tested. The tracker is like a mailing list or forum thread, don't be afraid to post.
- If you don't want to open an account with Launchpad, post your observations on the hugin-ptx mailing list.
- The developers fix the bugs identified in the tracker.
- The builders build new snapshots including the fixes.
Development Codelines
It is recommended to work separately on major changes and integrate them in the main codeline when they are ready. The currently open development branches are listed in the repository along the release branches.
hg pull hg branches
If you want to work on a major new feature, open yourself a branch.
hg branch <NEW_UNIQUE_BRANCH_NAME>
If you want to publish that branch on Sourceforge, ask for write right and push your changes to Sourceforge.
hg push
The branch owners are strongly encouraged to regularly sync their branch with default, i.e. merge the changes that have occurred since the last sync (or branching) into their branch.
hg pull hg up -C <YOUR_BRANCH> hg merge default hg ci -m "merged from default" hg push
If an unresolved conflict arises, see below the Merging section.
When development is complete or has reached a milestone, it may be integrated into default. Before integrating into default it is recommended to:
- Merge all of default's changes since the last sync into the branch.
- Test that the branch builds on the major supported platforms.
- Test that the branch does not break existing functionality (unless the break is intended, e.g. when a new functionality replaces an existing one).
When the development branch has fulfilled its purpose; is superseded or has been abandoned, close it.
hg up -C <OBSOLETE_BRANCH> hg commit --close-branch -m 'close badbranch, this approach never worked' hg up -C default # switch back to "good" branch
Most of the time Mercurial is quite good at merging different codelines. However sometimes there are conflicting version and even Mercurial does not know what to do. It will prompt for you to solve the conflicts.
The preferred tool to solve conflicts is [KDiff3 http://mercurial.selenic.com/wiki/KDiff3]. According to Mercurial's wiki it is 'the "best" merge tools' and included with the Windows installer of TortoiseHg. Handbook. On Ubuntu install it with `sudo apt-get install kdiff3`. To work comfortably with KDiff3, add the following lines to ~/.hgrc:
[extensions] hgext.extdiff = [extdiff] cmd.kdiff3 = [merge-tools] kdiff3.args = $base $local $other -o $output
First close the codeline to be merged with a last commit. Then switch to the default branch and start the merge.
hg up -C feature-x hg ci -m 'Closed branch feature-x' --close-branch hg up -C default hg merge feature-x
During the merge operation, Mercurial will trigger KDiff3 automatically in case of an unresolved conflict. Kdiff3 will show three versions side by side in the top half of the window:
- in the middle is the current one
- on the right is the new one
- on the left is the base (common ancestor? not sure?)
- In the bottom half of the window is the resulting merge, with conflicts highlighted.
- Using the buttons bar:
- Use the symbol with the three arrows up/down to jump to the previous/next unsolved conflict.
- When a <Merge Conflict> area is highlighted in the bottom pane, hit the A/B/C buttons to select which version(s) to use/merge in.
- Once all conflicts are solved, save and quit. Mercurial will continue the merge operation.
Once the merge operation is finished, commit and push.
hg ci -m 'Merged branch feature-x' hg push
Maturity Criteria
A development codeline - whether under revision control or presented as a patch - is considered mature when:
- a: the functionality it is intended to implement works on the developer's machine ("works for me" condition)
- b: it has been tested to build on the major supported platforms ("does not leave them behind" condition) by at least one contributor for each: Windows, OSX, Linux
- c: it does not unintentionally break existing functionality ("no regression" condition)
When a development codeline reaches maturity, it enters the integration queue.
Integration Queue
The integration queue is the ordered list of new features / development codelines waiting to be integrated in trunk. The prioritization is a collective decision by consensus of the developers. Silence = consent. The discussion, and the latest version of the list, are on the mailing list.
The integration queue is not set in stone: a change in the maturity status of a feature in waiting is good reason to review/change the ordered list. In any case it is reviewed after every release branching.
Once a month the developers are polled if there is reason to issue a release. If there is enough support for releasing, one developer takes on the role of release manager and undertakes the following steps:
The conditions to declare a release final are:
- the code builds on the major supported platforms (Ubuntu, Fedora, OSX, Windows)
- there is no (known) regression, unless intentional. This means: what worked with the previous release should work with the current one.
Release Plan
Planning the release helps contributors pace and schedule their contributions. On Launchpad there is a simple and adequate tool for planning and communicating releases.
Register a New Hugin Releases Series in Launchpad
When starting a new release cycle, register first a new Releases Series in Launchpad.
- Prerequisites: must be logged in to Launchpad and be a member of the Hugin-Devs team.
- Point your web browser to: https://launchpad.net/hugin/+addseries
- Enter the Version in the Release Name field: V_MAJOR.V_MINOR
- As Summary enter a bullet points list of the most relevant new features that will be introduced by the release.
- Hit Register Release Series.
- On the next page edit the Release Manager.
Edit Status of Previous Series
As a policy:
- Only the default branch, the latest release, and the active development branches are in active development.
- Only the previous two releases are supported.
- Older releases are obsolete.
To change the status as a consequence of the new release cycle, point your browser to https://launchpad.net/hugin/<V_MAJOR.V_MINOR>/+edit, e.g. https://launchpad.net/hugin/2010.4/+edit for the relevant series.
- Change the status of the previous release from Active Development to Supported.
- Change the status of the oldest supported release to Obsolete.
Register Milestones for the release
Planning milestones in advance and registering them with targeted dates will make the process more predictable and help builders plan for the binaries releases.
As a rule of thumb plan for two betas spaced by 2 weeks; for one release candidate two weeks after the last planned beta; and for the first RC to be declared final two weeks after release. Adapt to the circumstances. Things will change during the cycle and you can also add extra betas and rcs. Toward the end of the cycle, spacing can be one week.
- Point your browser to https://launchpad.net/hugin/<V_MAJOR.V_MINOR>/+addmilestone of the new releases series, e.g. https://launchpad.net/hugin/2011.0/+addmilestone
- Enter a name following these conventions:
- Betas: <V_MAJOR>.<V_MINOR>beta<INCREMENT> with INCREMENT starting from 1, "beta" in small caps and no spaces or underscores, no leading zeros. Example 2011.0beta1
- Release Candidates: <V_MAJOR>.<V_MINOR>rc<INCREMENT> with INCREMENT starting from 1, "rc" in small caps and no spaces or underscores, no leading zeros. Example 2010.4rc2
- Final Release: <V_MAJOR>.<V_MINOR>.<V_PATCH>, no leading zeros. Example: 2009.2.0
- No need to enter a Code name.
- Enter the date targeted for the tarball release.
- No need to enter a Summary.
- Hit Register Milestone.
Release Notes
The Release Notes are an important document accompanying the release. Although it is just a list of new features, it gets distributed widely. Most readers are unlikely to have used Hugin before. When drafting them, think that the target audience is somebody who has an idea of what a panorama stitcher might be, has never heard of Hugin, but is interested in discovering cool new software.
Start drafting them early in the process to allow for translators to translate the Release Notes on the website. Moreover, you will send them as simple text with each released tarball.
Important: store the release notes in the repository, as a text file inside doc/releases/. Use those texts as inspiration example.
Set Up
Set yourself up to edit the release notes on the website. You will need write access to the SourceForge project.
hg clone ssh://${firstname.lastname@example.com/p/hugin/hugin-web hugin-web
The Editing Cycle
cd hugin-web hg pull hg up mkdir releases/2014.0 nano releases/2014.0/en.shtml hg add releases/2014.0 hg ci -m "skeleton|draft|updated|final release notes" hg push
The website updates automatically about every hour. Wait enough time and point your web browser to http://hugin.sourceforge.net/releases/2010.4/ to verify the result of your edits.
Release Notes for the First Beta Release in a New Release Cycle
Before posting the beta1 of the release cycle, you want to have at least a working draft of the Release Notes. Edit them directly on the website. List the relevant new features. Use the release notes from past releases as a template. Copy them in text form for the email announcing the beta1 release. Don't link them from the homepage. Translators will want to start working on the text as soon as possible. Try to finish it early in the process. Add a comment at the beginning of the text to detail its current status. Not all translators follow the Changelog of the website and so are not aware if you committed the document as skeleton / draft / update / final.
Release Notes for Follow Up Releases in the Same Release Cycle
It is important to show the changes relative to the previous tarball, however only in the email announcing the new tarball. The HTML page on the website will most likely stay untouched (unless an important new feature has been added so late in the cycle). Add a section "Changes since previous beta release" (or "Changes since previous release candidate" if we're already at the RC stage) to the text mail you sent announcing the beta1 release. Copy and edit the relevant Changelog entries in there.
Branching Out For Release
1. Identify and add the new strings for translation.
Before running the script, make sure you have wxrc installed. On older Ubuntu, run
sudo apt-get install wxrc. On Ubuntu 10.4LTS it is
sudo apt-get install wx-common.
hg pull hg up cd src/translations ./extract-messages.sh hg diff hg ci -m "Add new and update existing strings for translation" hg push
2. Update the Changes.txt file
3. Identify the last time a release branch was branched from the default branch. This is usually tagged with a beta1 tag, so just use `hg view` and note down the revision number associated with the last beta1 tag. Extract the relevant changelog information for the release notes and save them in a file for later use:
hg log -r <REV#>: -b default --style Changelog.style > ../temp_change_log.txt
4. Branch out a new release-codeline (replace 2010.4 below with the appropriate version number. 2010 stands for the current year and 4 stands for the next even number in sequence, starting with 0 if the year has changed and this is the first release of the year).
hg branch 2010.4
5. Bump up the version number:
nano ./CMakeLists.txt nano ./mac/Version.xcconfig hg ci -m "bumping version number"
In the top level ./CMakeLists.txt edit the lines
# version set(V_MAJOR 2010) set(V_MINOR 4) set(V_PATCH 0)
In mac/Version.xcconfig edit the lines
6. Update the @api-min and @api-max setting of the Python scripts in src/hugin_script_interface/plugins. For this it needs to check if they work with the current API or if there was an incompatible API change. In the latter case the scripts should updated or removed from the release.
This is not required for the scripts in src/hugin_script_interface/plugins-dev. These files contains only the rough framework for script developer.
7. Set the red splash screen to indicate that the artwork embellishing the release has not been selected yet (only to be done, if there is artwork selected for the release).
hg revert -r 5008 src/hugin1/hugin/xrc/data/splash.png hg ci -m "red splash screen to indicate release cycle with no artwork selected yet"
(April 2015: currently not needed)
8. Switch back to the default branch and bump up to the next odd version number, e.g. 2010.5 in this example.
hg up default nano ./CMakeLists.txt nano ./mac/Version.xcconfig hg ci -m "bumping version number"
Edit the same lines as above in the top level ./CMakeLists.txt file and in ./mac/Version.xconfig
The same applies to the @api-min and @api-max settings in the scripts.
9. Verify that the branches are ok and push them to the official repository. Since we intentionally create a new remote branch, we use the -f switch in the push command.
hg view hg push -f
Keeping the Release Branch in Sync with Default
Committers have no obligation to help maintaining the release branch. In fact, it is best if they keep working in default on both code and translations. As a release manager, you want to stay on top of the changes in default and synchronize them into your branch prior to release if relevant.
The Hgk Mercurial extensions will help you with this. Edit your ~/.hgrc file to activate it. In [extensions] section add:
hgext.hgk =
If `hg view` does not work / returns an error, you may be missing a dependency. In Ubuntu type `sudo apt-get install tk8.5`.
In Hgk the changesets are displayed chronologically per branch with the newest one on top. Branches are indicated visually by a tree on the left. Tags have a yellow background and te top of branches are indicated by a box with green background and the name of the branch, except the default branch. Tags are displayed on yellow background.
Syncing Code from Default to Release Branch
This is for code only. For translations, see below.
- Make sure your repo is up to date and get an overview of the two branches with Hgk:
hg pull && hg up <RELEASE_BRANCH> && hg view default && hg view <RELEASE_BRANCH> &
- Find the first changeset on the default branch after the last time you synchronized and work yourself up to the present.
- Select one changeset at a time. You will see details of the change set in the lower part of the window.
- In the lower left panel, read the changeset log and its revision number.
- Decide if you want to apply it to the Release branch (i.e. if it is a bug fix)
- If you decided that the changeset should apply to the Release branch, check if it has not been applied already by the developer.
- If it has not been applied, apply it, using the <REVISION_NUMBER>:
hg graft --log --rev <REVISION_NUMBER>
- If you deem this to have been a major change, go through a build/test cycle
- Repeat until all new changes have been applied
- Go through a build/test cycle
- Push your changes to the public repository
hg push
Syncing Code from the Release Branch to Default
This is for code only. For translations, see below.
The procedure is the same, just make sure you're working in default:
hg pull && hg up default && hg <RELEASE_BRANCH> && hg view default & hg export --git <REVISION_NUMBER> | hg import - ... hg push
Updating Translations
Translations must always be imported using `msgmerge`.
- copy the file with the new contributed translation to src/translations/<LANG>.contributed.po
- check how many strings will be added/removed
- merge the new translation with the existing translation into a new file src/translations/<LANG>.merged.po
- examine the old and the new po files with msgfmt.
- if the statistics look good, overwrite the old file with the new file, commit, push, and ask native language speakers to check.
- repeat separately for each affected branch.
hg pull hg up -c 2010.4 cp ~/Downloads/${UPLANG}.po ~/src/hugin.hg/src/translations/${UPLANG}.contributed.po cd ~/src/hugin.hg/src/translations/ ./diff_po.pl ${UPLANG}.po ${UPLANG}.contributed.po msgmerge -o ${UPLANG}.merged.po ${UPLANG}.contributed.po ${UPLANG}.po msgfmt -c --statistics ${UPLANG}.merged.po msgfmt -c --statistics ${UPLANG}.po mv ${UPLANG}.merged.po ${UPLANG}.po rm ${UPLANG}.contributed.po hg ci -m "Updated ${UPLANG} translation (${TRANSLATOR})" hg push
To check the status of the translations you could do something like:
for i in *.po; do echo $i; msgfmt -c -v $i; done
This will give you something like:
<snip> bg.po 509 translated messages, 505 fuzzy translations, 369 untranslated messages. ca_ES.po 300 translated messages, 576 fuzzy translations, 507 untranslated messages. </snip>
1. Start with a clean checkout.
hg clone http://hg.code.sf.net/p/hugin/hugin hugin.hg
2. Switch to the branch you are going to release (example 2013.0 release; and when you don't know do a "hg branches")
cd hugin.hg hg update -C 2013.0
3. Update the Changelog (make sure LC_ALL is set to UTF-8 when doing this). In Ubuntu you may have to do something like `export LANG="en_CA.UTF-8" && export LC_ALL="en_CA.UTF-8"`
4. commit the Changelog
cd .. mkdir hugin.hg-build cd hugin.hg-build cmake -DUPDATE_CHANGELOG=1 ../hugin.hg cd ../hugin.hg hg ci -m "Updated ChangeLog"
5. Update the appdata files in platforms/linux/appdata. Add a line with the date and release number like
<release date="2020-12-12" version="2020.0.0" />
in the <releases> block to calibrate_lens_gui.appdata.xml, hugin.appdata.xml and PTBatcherGUI.appdata.xml.
6. tag the release (list the tags first to see how releases are named and ensure consistency.
- Betas: <V_MAJOR>.<V_MINOR>beta<INCREMENT> with INCREMENT starting from 1, "beta" in small caps and no spaces or underscores, no leading zeros. Example 2011.0beta1
- Release Candidates: <V_MAJOR>.<V_MINOR>rc<INCREMENT> with INCREMENT starting from 1, "rc" in small caps and no spaces or underscores, no leading zeros. Example 2010.4rc2
- Final Release: <V_MAJOR>.<V_MINOR>.<V_PATCH>, no leading zeros. Example: 2009.2.0
To fix/clean up tags:
- remove a tag with `hg tag --remove <TAG_NAME>`
- add a tag by going to a specific revision and tagging it: `hg up -q -r <REV> && hg tag <TAGNAME>`
- if a tag exists already and you want to move it, just use `hg tag -f <TAGNAME>` at the new revision to be tagged
7. note down the revision/hash for the release
hg tags hg tag <RELEASE> hg log -l 2 hg push
7. Create tarball
cd .. mkdir hugin-tarball cd hugin-tarball cmake ../hugin.hg -DENABLE_LAPACK=YES -DCPACK_BINARY_DEB:BOOL=OFF -DCPACK_BINARY_NSIS:BOOL=OFF \ -DCPACK_BINARY_RPM:BOOL=OFF -DCPACK_BINARY_STGZ:BOOL=OFF -DCPACK_BINARY_TBZ2:BOOL=OFF \ -DCPACK_BINARY_TGZ:BOOL=ON -DCPACK_BINARY_TZ:BOOL=OFF make package_source
8. Build an rpm or deb (depending on your distro) from the tarball as a sanity check. Test what you can test.
tar xvfj hugin-2010.4.0.tar.bz2 mkdir hugin-tarball-build cd hugin-tarball-build cmake ../hugin-2010.4.0 -DENABLE_LAPACK=YES -DCPACK_BINARY_DEB:BOOL=ON -DCPACK_BINARY_NSIS:BOOL=OFF \ -DCPACK_BINARY_RPM:BOOL=OFF -DCPACK_BINARY_STGZ:BOOL=OFF -DCPACK_BINARY_TBZ2:BOOL=OFF \ -DCPACK_BINARY_TGZ:BOOL=OFF -DCPACK_BINARY_TZ:BOOL=OFF \ -DBUILD_HSI:BOOL=ON -DSWIG_EXECUTABLE=/usr/bin/swig2.0 make package sudo dpkg -i hugin-2010.4.0-Linux.deb
9. Rename the tarball. For snapsnots, append _snapshotYYMMDD (replace YYMMDD with Year/Month/Day). For betas, append _betaX with X being an incremental number starting with 1. For release candidates, append _rcX with X being an incremental number starting with 1. Eventually the last candidate will be made final (by removing the appendix) after a few more tests prove that no further candidate is needed.
cd .. mv hugin-2010.4.0.tar.bz2 hugin-2010.4.0_beta1.tar.bz2
10. Determine the tarball's checksum for the announcement notice
sha1sum hugin-2010.4.0_beta1.tar.bz2
11. Upload the tarball to SourceForge.
- Must to be a 'Release tech'.
- Preferred: with rsync (best with SSH Key set up, else need to enter password):
rsync --partial --progress -e ssh hugin-2010.4.0beta2.tar.bz2 yuv,email@example.com:/home/frs/project/h/hu/hugin/hugin/hugin-2010.4_beta/
- Web based alternative (not reliable, outdated instructions may not work since SourceForge has made major changes in February 2010)
- log on to the SF file manager
- left-click to navigate to the appropriate subfolder (e.g. hugin -> hugin-2009.2)
- click on the icon next to the appropriate subfolder and in the context menu select "Uploads here" (or "New folder") if you need a new folder.
- click on "upload file"
- browse to the local file and let the upload begin.
- prepare a release notes text file (e.g. "hugin-2009.2.0.release_notes.txt") and upload it as well, to the same subfolder
- left-click on the release notes text file and click the checkbox "Release Note"
- left-click on the released file. If you want it to be the default download for a specific platform, click the appropriate checkbox
- in the "Release Notes" dropdown list, select the appropriate ones for this file
- note the SHA1 sum calculated by SF. Compare it with the one determined in step 8. If it is different, delete the uploaded file and try again.
12. Upload the tarball to Launchpad.
- Must be a member of the Hugin Developers Team on Launchpad.
- Strongly recommended: a GPG Key set up on Launchpad.
- Must have a pre-registered Series (see Release Plan above).
- Sign the tarball (if you have a GPG Key)
gpg -u ${GPGKEY} --armor --sign --detach-sig hugin-2011.0.0.tar.bz2
- Point your browser to https://launchpad.net/hugin/<SERIES>/+addrelease, e.g. https://launchpad.net/hugin/2011.0/+addrelease
- Select the milestone against which you are uploading in the drop down menu, or if there was no milestone yet create one on the fly
- Set the release date
- Copy the Release Notes and ChangeLog into the fields
- Hit "Register the release"
- Hit "Add download file" (max file size is 200MB)
- Enter short Description: Hugin 2010.0.0 release tarball
- Browse to the .tar.bz2 file
- Browse to the .tar.bz2.asc signature
- Set Content Type: code release tarball
- Hit "Upload"
13. Draft the release announcement.
- Extract the relevant ChangeLog section since the last release (look up the last release by tag or by revision number in `hg view`, then issue a command `hg log -r <REV_OF_PREV_RELEASE>: -b default --follow --style=changelog > relchange.txt
- Use the Mercurial Tag noted earlier.
- Use the SHA1SUM noted earlier.
14. Mail the announcement to hugin-ptx.
15. Clear the bug tracker. Go over the reports identified as fix committed and change their status to fix released.
16. Wait for feedback and fixes. Volunteers may fix critical bugs. Test that the codeline builds on the major supported platforms. Test that no major functionality is broken. Repeats steps 1-13 as often as necessary.
17. Once the codeline is final, port relevant "polish" commits that have not been ported yet to default.
18. Later on if patches are required, apply them to the branch. Bump up V_PATCH in ./CMakeLists.txt and HUGIN_VERSION_PATCH in ./mac/Version.xcconfig, tag, and release.
Declare a Release Final
- No tarball is to be released as final without being a release candidate (RC) first. If fixes are committed to the release codeline after the last RC, you have two options: either declare the current RC final and the issue a known issue; or release a new RC and wait again for it to be deemed of final quality. Make the decision by consensus on the mailing list.
- Once you've decided that the current release candidate is final, polish the release notes in /doc/releases/ and on the website in /releases/ (this should be a process along with the polishing of the release itself). This will be mostly just text shuffling as information important during the release cycle such as calls for translation is pushed down in the document in favor of information that is more important for daily use.
Mercurial Repository
- identify the revision number that was tagged as the last RC (the number before the semicolon in the list of tags produced by the first command below) and tag it with the final version number:
hg tags hg tag -r 5243 2011.0.0 hg push
- commit the release notes into doc/releases/ if you have not done so yet.
The following procedure can be done on the web or more conveniently in a shell.
Web interface:
- Log on to SourceForge's web interface.
- In the download folder for the current release cycle, delete all betas and rc except the last one (hit the hash sign button if on the web interface)
- Rename the last RC files, e.g. hugin-2010.4.0.tar.bz2
- Rename the folder for the current release cycle to a final folder name
ssh -t USER,email@example.com create cd /home/frs/project/h/hu/hugin/hugin mv hugin-2011.0_beta hugin-2011.0 cd hugin-2011.0 mv hugin-2011.0.0_rc2.tar.bz2 hugin-2011.0.0.tar.bz2 rm *beta* rm *rc* # beware of this command, it may also delete some rc binaries you don't want to delete exit
Rename a text document with the release notes README and upload it
cd doc/releases/ cp hugin-2011.0.0.txt README rsync -e ssh README yuv,firstname.lastname@example.com:/home/frs/project/h/hu/hugin/hugin/hugin-2011.0/ rm README
Must be done on the web interface:
- Hit the circle symbol with the i on the line listing the download to show details
- for the README file, tick the Exclude Stats box
- for the tarball tick the Default Download boxes for all systems except Windows and Mac
- for Windows or Mac binaries, tick the appropriate Default Download box. (Issue: no discrimination of 32/64 bits -> use the 32 bits)
- Paste the announcement into the SourceForge news system. You need to be a 'News Editor' to do this. Log on to https://sourceforge.net/news/submit.php?group_id=77506 and paste the announcement. Note: we have not been using SF's news for at least a year.
- If you have not kept a copy of the last release candidate and its signature that were uploaded to Launchpad on release of the last release candidate:
- Point your browser to the last release candidate on Launchpad, e.g. https://launchpad.net/hugin/+milestone/2011.0rc1
- Download the last release candidate e.g. http://launchpad.net/hugin/2011.0/2011.0rc1/+download/hugin-2011.0.0_rc1.tar.bz2
- Download the last signature e.g. http://launchpad.net/hugin/2011.0/2011.0rc1/+download/hugin-2011.0.0_rc1.tar.bz2.asc
- Point your browser to https://launchpad.net/hugin/<SERIES>/+addrelease, e.g. https://launchpad.net/hugin/2011.0/+addrelease
- Select the milestone against which you are uploading in the drop down menu, or if there was no milestone yet create one on the fly
- Set the release date
- Copy the Release Notes and ChangeLog into the fields
- Hit "Register the release"
- Hit "Add download file" (max file size is 200MB)
- Enter short Description: Hugin 2011.0.0 release tarball
- Browse to the .tar.bz2 file
- Browse to the .tar.bz2.asc signature
- Set Content Type: code release tarball
- Hit "Upload"
Public Announcement
- update Hugin homepage with link to the new release notes
- mail the announcement to Hugin-PTX (subscription required).
- mail the announcement to CREATE (subscription required).
- There is only so much testing that can be done with our limited resources.
- Final releases are expected to build and work on the major supported platforms, however it is possible that a bug slips in due to lack of resources / systematic testing
- We may issue patch releases in case of security issues or other major issues reported after final release.
- The Hugin project releases source code that is tested to build on the main supported platforms: Fedora, Ubuntu, Windows, OSX. It works on the developers machines. YMMV.
- Building and distributing binaries is left to the users communities. Once there are binaries of appropriate quality level for platforms that do not have a package manager (Windows and OSX) we add them as a courtesy to the SourceForge download archive - as usual "WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE." See the GNU General Public License for more details.
Download Test Build
Users publish test builds in different places of their choosing. Refer to hugin-ptx for the latest information.
- Ubuntu: when there are changes in the repository and when the latest revision builds, an automated nightly is produced every 24 hours for the Hugin PPA. Add it to your system with:
sudo add-apt-repository ppa:hugin/hugin-builds sudo add-apt-repository ppa:hugin/nightly sudo apt-get update sudo apt-get install hugin enblend
- OSX: from time to time bleeding edge bundles are updated on Harry van der Wolf's site.
Build your Own Test Builds
If you are ready to go through the building process, here are the instructions.
|These builds are for your computer. If you decide to share them with others, be aware that you are subject to the GPL, and that the general public may need guidance regarding what you distribute. Read the information in the packaging and distribution section below. If you are unsure, ask on the hugin-ptx mailing list for advice before posting a file for download.
An infrastructure for on-demand build and distribution of usable test-binaries for the most popular platforms. Ideally on demand, and synchronized with the project's major milestones and releases. But also builds for personal use.
- The build process for Hugin and related tools is documented for each of the supported platform.
- Users reproduce the documented process and report success or failure.
- Experienced users and/or developers follow up on the reports and keep the documentation current.
- Power users script and automate the building process.
- Users with packaging skills package the builds for distribution (installers).
- The produced binaries/installers will be made available via the package distribution tools of well managed O/S; and/or on the web.
Specific revisions
When building from the repository, some revisions may be broken. This process is meant to build the latest revision so that if the latest revision has bugs these can be identified, reported and corrected. However sometimes these bugs can be more critical than other times. If you need a more or less working version of Hugin, try applying the process to an earlier revision or to a released branch. To stay on top of all changes, consult the revision logs and the discussions on the hugin-ptx mailing list.
Supported Platforms
- If you don't find your preferred platform listed below and you are willing to contribute your time and skills to build Hugin on it, feel free to add it to the table. We will accommodate any well supported platform in the regular release process.
- Redundancy is good. If you have access to one of the listed platforms, please try to run the documented process below and report success to hugin-ptx.
Supported Versions
The Hugin Packagers Team for Debian can be reached at hugin at packages.debian.org. Liaise with them if there are issues with the binaries in Debian (and downstream distributions like Ubuntu) and on backports.org.
Gentoo Linux
all platforms
a big thank you to Pablo d'Angelo for supporting all of those building efforts.
Build Chain
- tbd: looking for responsible
- OK: mostly automated build process ready on request
- unavailable: temporarily unavailable (e.g. responsible on holiday)
- HW-broken: the hardware is temporarily unavailable
- SW-broken: temporarily dysfunctional, working on a fix
- broken: nobody is working on a fix
- unsupported: has been dropped for lack of support
- tbd: status unknown
- auto: work as documented and has been automated to a reasonable extent
- OK: works as documented, could use automation / scripting
- draft: documented, needs validation / testing / cleaning
- incomplete: parts are missing (e.g. enblend, libpano)
- outdated: worked in the past but needs an update
- obsolete: nobody has the time to update
Hugin is work in progress and dependencies can be added any time. If your build does not work, see Fixing The Hugin Build.
Hugin depends on the following packages. The list may be incomplete, and there may be some platform-specific dependencies. Details for specific platforms are in the platform documents linked above.
Build-Time Dependencies
Users compiling Hugin (version 2016.1 and later) from source will need:
- A C++ compiler which supports OpenMP and C++11
- OpenMP support is not required. But when compiling without OpenMP nona and cpfind (and some other algorithm) are running only with one thread, which is slower.
- The wxWidgets GUI toolkit version >=2.7.0. the 3.x series is supported.
- std::filesystem from C++17 or boost::filesystem (Boost >= 1.47)
- libzlib the zlib compression library.
- libtiff the TIFF library with LZW support.
- libpano13 version >=2.9.19
- libjpg the JPEG library
- libpng the PNG library
- libopenexr the OpenEXR library
- vigra the VIGRA Computer Vision Library >=1.9
- Exiv2 Image metadata library
- GLEW the OpenGL Extension Wrangler Library or libepoxy library for handling OpenGL function pointer management (since 2023.0, see file INSTALL_cmake for more details)
- gettext
- optionally, libfftw3
- On Unix/Linux you need also
- On Windows you need also
- HTML Help Workshop for generating compiled HTML help file
- optional WiX toolset to create the installer
- On MacOS you need also
- for the optional Python Scripting Interface (currently functional and tested only on Linux and Windows)
- Hugin can be compiled with gcc, as well as with MSVC.
- The build process requires CMake version >=3.1
Run-Time Dependencies
At runtime
- enblend >= 3.2 is required.
- Exiftool >=9.09 is required.
- Starting with Hugin 2010.3 and newer, Hugin ships with its own control points generator cpfind. Prior to 2010.3 another optional but recommended runtime dependency was a control points generator.
- Optionally Python argparse command-line parsing library for the Python scripts.
Packaging and Distribution
Instructions for packaging binaries for distribution will follow. Some important points:
- comply with the GPL
- join a text of the GPL in the distribution
- give access to the source code
- credit the authors
- label clearly the snapshot as such, with a reference to the build date and/or the SVN revision number
- edit the text / readme files that come with the snapshot
- indicate clearly that it is unstable, experimental software
- indicate where to find the latest version
- indicate that the advertised features might or might not work
- comply with the GPL
- join a text of the GPL in the distribution
- give access to the source code
- credit the authors
When running through the building process documented above chances are that something goes wrong. While it is disappointing when the process ends in a flurry of cryptic error messages it is not harmful. This is the nature of software development and you are now part of it. There is a lot of value in your experience and you can help improve the process and get closer to the hoped for software package. Don't be ashamed that it did not work. This happens even to the most expert coders. Give the developers feedback on the hugin-ptx mailing list. Only with your feedback they can know that something goes wrong, and a well crafted feedback is the most important step to help identify what went wrong and devise a solution. Be a part of the solution, not a part of the problem!
To give good feedback, note down carefully all of this information while you are going through the instructions.
- Details about your computer. CPU, operating system, other particularities
- The revision number of the code checked out with Mercurial (`hg sum`). If you don't find a revision number, the date and time when you checked out the code.
- The last step / command you entered into the command line.
- A copy of the last few lines displayed, from where you think the error messages started. Don't worry if you copy a couple of lines too many, it is better to give more lines than less lines.
Even the standard feedback is good feedback. For those wishing to dig deeper, you can try
- to use "make VERBOSE=1" when building hugin.
- to do a debug build "cmake -DCMAKE_BUILD_TYPE=DEBUG" and use oprofile for profiling.


text:
Morning Walk Movie Review
This is a movie (directed by Arup Dutta) which should have been half an hour shorter. It isn't just the song and dance in this film which is irrelevant, quite a few of the dialogues seem fake…and the acting is mostly bad.
The film is about two lovers who meet when they are much older and how their love is re-kindled. However, if Anupam Kher and Sharmila Tagore give stellar performances in this movie, the acting of the others is jarring. It is quite impossible to recommend this film. The characters in this film are unrealistic and stereotypical and so is the way the events unfold. The theme of the movie, which is about how a man is torn between his present family and his old love, held some promise but its execution left much to be desired. The plot meanders far too much and we are left with a disjointed film…
To read a more detailed (and continuation) of the review go here.
Kambakht Ishq review
New York review
Read other movie reviews here.
July 11, 2009 9:29 am
Seems like an interesting plot, good candidate for going for a pirated download copy. hehehe 🙂
(PS: Hey did you write this post in a hurry?)
July 18, 2009 2:45 pm
thanks..i wud like to watch it..nice blog..good variety..


text:
The Washington Nationals celebrated Presidents Day weekend by holding their annual racing president auditions Saturday at Nationals Park.
The team drew a record number of applicants from the DC area, and invited a select group to the ball park to run the bases and show off their entertainment skills.
The recent record snowfall provided a hitch for this year's applicants, as they were asked to run the full length of the presidents race in snow that reached 2 feet deep at the finish line. The conditions posed problems for more than a few racers who needed help up after falling in the snow.
For the fourth consecutive year, Teddy Roosevelt was absent from the auditions. Applicants donned the 12-foot costumes of George Washington, Thomas Jefferson, and Abe Lincoln, as they ran an indoor 40-yard dash, competed against each other on the snow-covered presidents race course, demonstrated their dancing and celebrating skills, and faced individual interviews with the entertainment staff.
We enjoyed meeting so many of the applicants as part of our first-ever video interviews (one of whom details his experience on his personal blog.
Update: Contestant Gwen Purdom details her experience in Washingtonian Magazine.
Audition photos by Ethan Ableman


text:
Gardiner Harris and Benedict Carey wrote an article in last week's New York Times includes, titled "Researchers Fail to Reveal Full Drug Pay." In it , they describe yet another instance of industry influence over what research and manipulation of the marketplace of ideas. We've included a few excerpts from the story below.
* * *
A world-renowned Harvard child psychiatrist whose work has helped fuel an explosion in the use of powerful antipsychotic medicines in children earned at least $1.6 million in consulting fees from drug makers from 2000 to 2007 but for years did not report much of this income to university officials, according to information given Congressional investigators.
By failing to report income, the psychiatrist, Dr. Joseph Biederman, and a colleague in the psychiatry department at Harvard Medical School, Dr. Timothy E. Wilens, may have violated federal and university research rules designed to police potential conflicts of interest, according to Senator Charles E. Grassley, Republican of Iowa. Some of their research is financed by government grants.
Like Dr. Biederman, Dr. Wilens belatedly reported earning at least $1.6 million from 2000 to 2007, and another Harvard colleague, Dr. Thomas Spencer, reported earning at least $1 million after being pressed by Mr. Grassley's investigators. But even these amended disclosures may understate the researchers' outside income because some entries contradict payment information from drug makers, Mr. Grassley found.
In one example, Dr. Biederman reported no income from Johnson & Johnson for 2001 in a disclosure report filed with the university. When asked to check again, he said he received $3,500. But Johnson & Johnson told Mr. Grassley that it paid him $58,169 in 2001 . . . .
The Harvard group's consulting arrangements with drug makers were already controversial because of the researchers' advocacy of unapproved uses of psychiatric medicines in children.
In an e-mailed statement, Dr. Biederman said, "My interests are solely in the advancement of medical treatment through rigorous and objective study," and he said he took conflict-of-interest policies "very seriously." Drs. Wilens and Spencer said in e-mailed statements that they thought they had complied with conflict-of-interest rules.
John Burklow, a spokesman for the National Institutes of Health, said: "If there have been violations of N.I.H. policy — and if research integrity has been compromised — we will take all the appropriate action within our power to hold those responsible accountable. This would be completely unacceptable behavior, and N.I.H. will not tolerate it."
* * *
Alyssa Kneller, a Harvard spokeswoman, said in an e-mailed statement: "The information released by Senator Grassley suggests that, in certain instances, each doctor may have failed to disclose outside income from pharmaceutical companies and other entities that should have been disclosed."
* * *
Dr. Biederman is one of the most influential researchers in child psychiatry and is widely admired for focusing the field's attention on its most troubled young patients. Although many of his studies are small and often financed by drug makers, his work helped to fuel a controversial 40-fold increase from 1994 to 2003 in the diagnosis of pediatric bipolar disorder, which is characterized by severe mood swings, and a rapid rise in the use of antipsychotic medicines in children. The Grassley investigation did not address research quality.
Doctors have known for years that antipsychotic drugs, sometimes called major tranquilizers, can quickly subdue children. But youngsters appear to be especially susceptible to the weight gain and metabolic problems caused by the drugs, and it is far from clear that the medications improve children's lives over time, experts say.
In the last 25 years, drug and device makers have displaced the federal government as the primary source of research financing, and industry support is vital to many university research programs. But as corporate research executives recruit the brightest scientists, their brethren in marketing departments have discovered that some of these same scientists can be terrific pitchmen.
To protect research integrity, the National Institutes of Health require researchers to report to universities earnings of $10,000 or more per year, for instance, in consulting money from makers of drugs also studied by the researchers in federally financed trials. Universities manage financial conflicts by requiring that the money be disclosed to research subjects, among other measures.
* * *
Universities ask professors to report their conflicts but do almost nothing to verify the accuracy of these voluntary disclosures.
"It's really been an honor system thing," said Dr. Robert Alpern, dean of Yale School of Medicine. "If somebody tells us that a pharmaceutical company pays them $80,000 a year, I don't even know how to check on that."
* * *
In the past decade, Dr. Biederman and his colleagues have promoted the aggressive diagnosis and drug treatment of childhood bipolar disorder, a mood problem once thought confined to adults. They have maintained that the disorder was underdiagnosed in children and could be treated with antipsychotic drugs, medications invented to treat schizophrenia.
Other researchers have made similar assertions. As a result, pediatric bipolar diagnoses and antipsychotic drug use in children have soared. Some 500,000 children and teenagers were given at least one prescription for an antipsychotic in 2007, including 20,500 under 6 years of age, according to Medco Health Solutions, a pharmacy benefit manager.
Few psychiatrists today doubt that bipolar disorder can strike in the early teenage years, or that many of the children being given the diagnosis are deeply distressed.
"I consider Dr. Biederman a true visionary in recognizing this illness in children," said Susan Resko, director of the Child and Adolescent Bipolar Foundation, "and he's not only saved many lives but restored hope to thousands of families across the country."
Longtime critics of the group see its influence differently. "They have given the Harvard imprimatur to this commercial experimentation on children," said Vera Sharav, president and founder of the Alliance for Human Research Protection, a patient advocacy group.
* * *
Controlling for bias is especially important in such work, given that the scale is subjective, and raters often depend on reports from parents and children, several top psychiatrists said.
* * *
"The price we pay for these kinds of revelations is credibility, and we just can't afford to lose any more of that in this field," said Dr. E. Fuller Torrey, executive director of the Stanley Medical Research Institute, which finances psychiatric studies. "In the area of child psychiatry in particular, we know much less than we should, and we desperately need research that is not influenced by industry money."
* * *
The entire article is here.
For a sample of related Situationist posts, see "The Situation of University Research," "The company 'had no control or influence over the research' . . . .," "Deep Capture – Part VII," "Promoting Smoking through Situation," "Industry-Funded Research," "Industry-Funded Research – Part II," and "Captured Science."


text:
John Shawe-Taylor
Delmiro Fernandez-Reyes
Juho Rousu
Viivi Uurtio
João M. Monteiro
Are you a researcher?Expose your workto one of the largestA.I. communities in the world
Get the week's mostpopular data scienceresearch in your inbox -every Saturday
HyperConformer: Multi-head HyperMixer for Efficient Speech Recognition
05/29/2023 ∙ by Florian Mai ∙
FigGen: Text to Scientific Figure Generation
06/01/2023 ∙ by Juan A. Rodriguez ∙
MultiFusion: Fusing Pre-Trained Models for Multi-Lingual, Multi-Modal
Image Generation
05/24/2023 ∙ by Marco Bellagente ∙
PyTorch Hyperparameter Tuning - A Tutorial for spotPython
05/19/2023 ∙ by Thomas Bartz-Beielstein ∙
Scalable Performance Analysis for Vision-Language Models
05/30/2023 ∙ by Santiago Castro ∙
Spider GAN: Leveraging Friendly Neighbors to Accelerate GAN Training
05/12/2023 ∙ by Siddarth Asokan ∙
Scan and Snap: Understanding Training Dynamics and Token Composition in
1-layer Transformer
05/25/2023 ∙ by Yuandong Tian ∙
Hey Jaz Kandola!
Claim your profile and join one of the world's largest A.I. communities
Sign up for DeepAI
Already have an account? Login here
Login to DeepAI
Forgot password? Click here
Don't have an account? Signup here
Become a DeepAI PRO
Pay as you go


text:
What's Up, Doc? Genetic diseases affect patients differently
Q: A 40-year-old lady just moved in next door, and she is in a wheelchair. She told me she had SMA, which is a kind of muscular dystrophy. I thought only boys got muscular dystrophy. What is SMA?
A: You must be thinking of Duchenne muscular dystrophy, which is an X-linked recessive disease. Recessive means you only get the disorder if you do not have any ``normal'' (unaffected) copies of the gene; so you either need to get two copies of an affected gene or one affected sex-linked gene for boys (since boys have only one X and one Y gene).
Girls have two X chromosomes so they can be carriers of Duchenne's but will not get the disorder; they will get a non-affected copy of the X chromosome from their dad along with a 50 percent chance of being carriers from getting an affected X chromosome from their mom (I will not discuss cases where a baby girl has some other genetic disorder). Boys get the Y chromosome from their dad, so if their mom is a carrier they have a 50 percent chance of getting the affected X chromosome from their mom.
SMA, which your new neighbor has, stands for spinal muscular atrophy. Like Duchenne muscular dystrophy it is also a recessive-inherited disorder that affects the muscles, but unlike Duchenne muscular dystrophy it is not linked to the sex genes (X or Y genes). (Actually one subtype of SMA - spinal-bulbar muscular atrophy - is X-linked, but I will not discuss this in today's column.)
Doctors Guido Werdnig and Johann Hoffman first described SMA in the 1890s. It is an uncommon disease, affecting 1 in 6,000 to 15,000 people. Note that this is not much different than the incidence of many more familiar diseases such as cystic fibrosis (1 in 1,700 to 6,500 Caucasian babies), Duchenne muscular dystrophy (1 in 4,000 males) or sickle cell (1 in 500 African American births). Although this is not the most common inherited disorder, it can be rapidly fatal in some cases (see discussion below) and it is the No. 1 genetic disorder that causes death before age 2.
As noted, SMA is inherited in a recessive manner so to get the disease both parents must be carriers of an affected gene (then there is a 25 percent chance the baby will have the disease); it is estimated that 1 in 40 people are carriers of this disease.
SMA occurs because the baby is born with a missing or mutated SMN1 (survival motor neuron 1) gene. People without this gene cannot make a protein that enables the nerve cells that control the muscles to work and survive normally. Without these nerves to stimulate the muscles they weaken and then atrophy.
SMA manifests not only in muscle weakness, but often also in deformities of some of the bones since the push and pull balance the muscles exert on the bones is altered by the disease. When the muscles that help you breath become compromised, there is an increased risk of pneumonia. Sensation is not affected by this condition since only the motor nerves are affected and SMA does not affect intellect.
The more severely the baby is affected, the earlier they develop symptoms and the worse their prognosis. Since the developmental milestones the baby fails to reach as they grow define the four subtypes of SMA, it is useful to quickly review normal baby development. It is important to realize that these milestones are guidelines, and every child is different. This is why it is so important for a baby to get all those checkups from their healthcare provider.
Normal milestones
- Birth to 2 months: babies move their head from side to side, bring their hands to their face and make jerky movements with their arms
- 1 to 3 months: briefly lift their head while on their tummy
- 2 to 3 months: lift their head 45 degrees and support their bodies with their arms while on their tummy
- 2 to 5 months: roll over from tummy to back, grab with their hands
- 4 to 6 months: lift their heads up, arch their backs, lift their chests off the ground
- 4 to 7 months: bear some weight on their legs while you hold them up
- 5 to 7 months: roll over back to tummy and tummy to back, play peek-a-boo
- 4 to 10 months: sit up without your support
- 6 to 12 months: crawl
- 8 to 12 months: pull themselves up and walk while holding onto furniture (cruises)
- 10 to 18 months: walk
- 2 years: kick a large ball
- 3 years: walk up stairs, feed themselves, stand briefly on one foot, ride a tricycle
- 4 years: hop in place, throw a ball over head
- 5 years: walk backward heel-toe
With this knowledge we can now discuss the subtypes of SMA. Type 1 SMA is also called Werdnig-Hoffman disease. These babies are affected before they are 6 months of age and miss the milestones for this age. They usually do not develop appropriate head control and, typically, are never able to sit up on their own or walk. These babies will usually have trouble swallowing and eventually develop trouble breathing due to weakness of the breathing muscles. This is the most severe form of SMA and half of these babies will die before age 2.
Type 2 SMA affects babies between age 6 and 18 months. They may be late on some of the milestones for these ages, but are able to sit on their own and some can even stand without support. They get pneumonia more easily since their breathing muscles are somewhat weakened. They may also have pronounced curvature of the spine from the weakness and imbalance of the muscles of the back.
Type 3 is also called Kugelberg-Welander disease and is the mildest of the childhood-onset SMAs. It begins to cause symptoms between ages 18 months and adolescence. Although these children can walk, they clearly become weak and they may fall more often than other kids and not be able to run. Some may need to use their arms to push on their legs to help them rise from a chair. Most of these kids eventually need a wheelchair.
Type 4 is the mildest form of SMA and symptoms begin in adulthood, usually in a patient's 30s. It is thought to be the least common type of SMA, although its insidious onset and slow progression may make this type of SMA under-diagnosed. As with the other types of SMA the proximal muscles - those closer to the trunk; the shoulder and hip muscles - are usually affected first.
There is no cure for SMA, but there are treatments to minimize complications from this inherited disorder. This includes respiratory support for those babies whose breathing is compromised, as well as nutritional support (such as a tube to their stomachs) for those babies that cannot swallow sufficiently to get adequate nutrition. For those with milder symptoms from the disease (later onset) but whose spines become curved, surgery to help straighten the spine may be needed (a severely curved spine can make breathing even more difficult).
Patients with SMA may benefit from physical therapy to minimize joint stiffness and to maintain flexibility. This may include exercise programs (possibly while in a warm tub), as well as occupational therapy to teach them techniques to continue with routine daily requirements despite their disability.
The suspicion of SMA will arise from the patient's symptoms of weakness and/or missed developmental milestones, and the disorder will be confirmed by tests that can be done. Genetic testing for this condition is done from a blood test to check for the absence of the SMN1 gene. Other testing may be done to evaluate for other disorders that can cause similar symptoms. Your healthcare provider will discuss what tests may be needed. For those families that have a child with SMA, genetic counseling should be done so they understand the risks of future children inheriting the condition. For those parents that feel it is appropriate, prenatal testing is also available.
There is active and ongoing research for SMA, and there are a couple of clinical trials underway looking to see if certain medications and treatments can help patients with this disorder. Patients and families affected by SMA should discuss these with their healthcare provider. For more information, visit www.ProjectCureSMA.org or the Families of SMA Web site at www.fsma.org.
Jeff Hersh, Ph.D., M.D., F.A.A.P., F.A.C.P., F.A.A.E.P., can be reached at email@example.com.


text:
Esther Cepeda: Driving to distraction
Illinois again finds itself at the center of the controversy over immigration. Gov. Pat Quinn has said he will be signing into law a bill that provides driver's licenses to illegal immigrants -- to bolster road safety.
The appeal that won the day noted the current law, which requires an applicant to present a Social Security number, keeps 250,000 people from getting licensed and therefore leaves them untrained and uninsured if they proceed to drive illegally.
According to the Illinois Highway Safety Coalition, the lobbying group to which this legislative victory is owed, unlicensed and uninsured drivers in Illinois are involved in 79,600 accidents each year, costing $660 million dollars in damages.
What the coalition doesn't say, however, is that no one can determine how many non-legal residents who drive without permission are involved in accidents.
In reality, the state's universe of unlicensed drivers goes far beyond those without green cards to include those whose licenses were suspended, revoked, expired or canceled, as well as drivers who never applied for a license.
Licensed drivers don't exactly put fears to rest, either. The Insurance Research Council estimates that 15 percent of the state's 8 million licensed drivers are uninsured -- that's 1.2 million licensed but uninsured drivers.
And about that insurance. Another premise in the safety argument is that once a previously ineligible driver obtains this license -- it is called a "temporary visitor's license" that is not designed to be used as proof of the holder's identity -- the next step is to get liability auto insurance, as required by law.
Well, based on the statistics I've cited, there's clearly no mechanism for making sure that any driver gets insurance. And there's no evidence, from either industry groups or other authoritative sources, that giving driver's licenses to illegal immigrant drivers increases rates of insured drivers.
Look at New Mexico. In 2003, the state began allowing non-citizens to obtain driver's licenses with the hope that it would reduce the high number of uninsured drivers.
No dice.
According to the Insurance Research Council, 26.3 percent of New Mexico drivers were uninsured in 2000. By 2008, this number had gone up to 29.5 percent and the border state won the distinction of being No. 1 in the nation for uninsured drivers.
Oh, and people started flocking there to fraudulently obtain licenses.
And about fraudulent documents in Illinois. Just to show you how far the lobbying progressed, back in 2007, the proposed bill called for submitting fingerprints to the State Police so they could check for any previous driving records and outstanding warrants. And, the immigrants would have been required to turn in all false licenses and state IDs.
This time, the turn-in provision wasn't included. And, though debated, the proposed fingerprinting requirement was dropped because it was deemed to be too costly and could potentially keep some people from applying out of fear that their fingerprints could wind up in the hands of federal authorities.
Instead, the requirements are pretty lax: Applicants would have to prove that they've lived in Illinois for at least a year by providing copies of a lease, utility bills and such.
Call me a cynic, but as the resident of a town that has repeatedly made national headlines for its sophisticated fake-ID rings, it's difficult to imagine that counterfeit electricity bills and rental agreements aren't spitting out of laser jet printers across the state as I type this sentence.
Let's be real -- anyone with eyes can see that though this move is cloaked in the promise of safer roads, it's really just a political move to bolster Illinois Democrats' pro-immigrant bona fides and, as a happy aside, empower the illegal immigrant population.
Hours after the legislation passed the state's House of Representatives, Chicago Mayor Rahm Emanuel, who formerly was considered timid on immigration reform, was celebrating its passage while certain immigrant advocacy groups were crowing about what a "huge victory" this was and how the move adds much-needed "momentum" to an issue on and off the back burner.
I doubt it -- but who knows?
In the meantime, take it from someone who's been crashed into by a driver with no license or insurance: Don't get a false sense of security about driving in the Land of Lincoln. It's not particularly foolproof now and there's little reason to believe it'll get that way anytime soon.
Esther Cepeda's email address is firstname.lastname@example.com.
Washington Post Writers Group


text:
Price: $ 465.00 USD..
or 3 equal layaway payments in store, with a credit card of $155.00 over 60 days.
payments are automatically deducted from your credit card.
Within The Continental USA Only
As an option you may also pay for Lladro SITTING BATHER - Porcelain Figurine
using Paypal or with your Amazon Account(*select items). Please note that all orders must be delivered to a physical address verified by Paypal or Amazon. These options are not applicable for orders to be delivered to Military or International destinations.
For Military APO/FPO orders please use our standard checkout. For International Delivery, please click on the International Shipping Icon to see the landed cost to your country. No Sales Tax Except In The State Of Florida.
SITTING BATHER Porcelain Figurine by Lladro
image Copyright © 2023 by Lladro
Lladro was founded in 1953 when Juan, Jose, and Vicente, three brothers born of local farmers and endowed with great artistic talent, formed a small family company in the Valencian village of Almacera, Spain. Since then, Lladro has undergone an amazing metamorphosis from an artisan workshop to a huge firm of international scope enjoying continual growth. The company management has remained in the hands of the Lladro family, the owners of the firm, since its inception. The creative team started out by adapting styles from past eras, but it was not long before certain characteristics appeared that would soon shape what was to become the unique Lladro style.


text: Forbes National Events We're making change for men's health in Forbes. Give us a hand. Display Details Each year in Australia Ovarian Cancer Awareness Month is held in February to raise awareness of Ovarian Cancer Display Details Promote your Event in Forbes National Events Directory todayCreate a Search and Social Media friendly listing with Phone, Email, Website, Logo, Message, Video and Map to direct Customers, Members or Sales to your Event 24 x 7 with no expensive PPC! Automatically include Facebook and over 300 business and social networking backlink services with Local Community or Australia Wide Advertising through your flexible Smart Event listing in Forbes or broadcast to Over 1000Australian Town, City and Region Websites To build your Event in Forbes Create an Account or LOGIN here to access all Australian Town and City web sites and unleash your Easy and Value Community Marketing Platform Get your Event in Early for the best results, Facebook Friendly Banner Design Tool + More Inside!If you want us to build an Event for you first create an accountVisit LIST YOUR BUSINESS for more info Help your favorite business owner find Forbes National Events Directory.If you know them personally Click Here to send this page to your friend. All logos and trademarks in this site are property of their respective owners


text: Scotch & Soda strives to provide you with relevant and personal information in a user-friendly way. For this we use different cookies and similar techniques ('cookies') on our websites and apps. We use functional and analytical cookies to provide for the best user experience. We, as well as third parties, also use tracking cookies on our websites and apps to show you customised advertisements and offers on our websites and apps, as well as on third party websites and apps. By clicking the 'Agree' button you agree to the use of these cookies. You can find more information in our Cookie Statement or our Privacy Policy. You can adjust your preferences .


text:
Houston Tx Backpage Com
A libertine girl from Houston wants to quickly have a naughty guy for a one night stand
Houston Tx Backpage Com
First name: Anna-belle, Age: 37 yo, City: Houston (AK)
I love foreplay in the ass because it gets me really wet. I need a man who is good at eating my pussy. I'm quite good at taking your cock in my mouth. However, I want a good doggy style fuck as I love hot guys with big dicks. I'm a slut who's looking to moan. We can meet up in Houston and its surroundings. I can usually give you an interview in the early evening. I am only interested in dating younger men because I am a cougar. I want a night of crazy fun first and foremost. I am mostly a very demanding woman when it comes to sex. I love showing you how to get me really excited. In conclusion, I am eager to discover your meeting proposals. I can't wait to see you again. I think we'll get along great during this hookup. See you soon! The Kiss.
My girlfriend is in need of some sexual healing, so I'm going to serenade her with this little trio
Houston Tx Backpage Com
First name: Tillia, Age: 23 yo, City: Houston (AK)
We are free especially on weekends. My boyfriend and I can host you at our place. Age is not important to us, however respect is always fundamental in order to make love with our company. We are only looking for a naughty man to engage in some swinging. My boyfriend and I love going to swingers clubs in Houston in order to find open-minded people. I'm a little bit to blame because I always demand more from the guys and I have very few limits. To contact us, you need to leave a comment. We only want to have fun between amateur pleasure-seekers.
Single girl looking to experiment with sm on Houston
Houston Tx Backpage Com
First name: Tahia, Age: 18 yo, City: Houston (AK)
I just want to fuck well. I'm attracted to very cute bad boys. I also want a guy with a big dick because otherwise I don't cum. For this hot encounter, I can join you in a bar. If you want, I'm willing to give a date in a hotel. I have no taboos when it comes to naughty games like swinging or anything else. I therefore want to try out several of these practices with a guy who has some experience. In short, if you want to be sexually spoiled, it's better not to be a novice. Know that if you meet my criteria, you'll remember it.
My 42-year-old girlfriend is addicted to candaulism and she's looking for some fun on Houston
Houston Tx Backpage Com
First name: Lamiya, Age: 42 yo, City: Houston (AK)
Welcome everyone, I am a quite charming and exciting woman who is 42 years old. My name is Lamiya. We make a naughty ad with the intention of playing with a hot guy during an evening of unrestrained fucking. I'm a hot girl and I'm good at making penises stand up. We love SM. The best for me is when I am handcuffed so that my man can watch you make love to me and I moan in ecstasy. We can schedule an appointment for Saturday, but we prefer that it takes place at our house. We have a lot of outfits to choose from. I hope to see you very soon. Kisses.
Looking for a hookup in Houston? This young lady is very forward and up for anything!
Houston Tx Backpage Com
First name: Marie-anise, Age: 32 yo, City: Houston (AK)
Hello everyone, my name is Marie-anise and I'm just 32 years old. I'm quite naughty, and it seems that according to my ex-boyfriends, I would be a real nymphomaniac! I want an affair with a lover who enjoys erotic games. I need someone who is available and creative to moan loudly. Since I am a beginner in libertinism, I require a true libertine who knows how to proceed. I want to let you take control during this fuck session and be your object of amusement so that you can have an orgasm through me. We can make a date at your place for this future fuck. Otherwise I'm available mostly at the end of the day and rather on Sundays. I leave you in the meantime to find your messages to satisfy my most unspeakable sexual urges. I don't want anything else so if you can't give me what I want then just leave. Don't offer me anything. Notify me! I kiss you!
Looking for a hard fuck this afternoon Houston
Houston Tx Backpage Com
First name: Madinina, Age: 21 yo, City: Houston (AK)
Hi guys, I felt like posting my naughty desires on this hookup site to have some fun. My name is Madinina and I'm 21 years old. I am a girl who likes to watch and I want to attract boys for a webcam session. Ideally, I would like the gentlemen who write to me to be blond and rather burly. I'm looking for a boy who will be up to the task, because I expect a lot from him sexually. I can stay in bed all day if my partner satisfies me. We can make a date, I suggest evenings. I'll let you choose the place but only in Houston. I just want to have a guy for a one night stand because I love making love without limits with a stranger. I like to do a lot of different kinds of foreplay, so I want a guy with some experience. Therefore, if you want to get to know me better, let me know. I hope you understand me and will be able to satisfy me. See you soon.
A naughty couple would like to fuck with a stranger on Houston
Houston Tx Backpage Com
First name: Minel, Age: 31 yo, City: Houston (AK)
Hi guys, I'm Minel and I'm 31 years old. I am in a relationship with a 27-year-old man. We are true sex addicts. We are available to meet with you on Sunday. Can I fuck at your place? I don't think I have any physical criteria because it's just for a meeting... But on the other hand I want a hot type, my companion really has to be able to see another male make me cum. I enjoy practicing candaulism because it allows me to have fun with another lover while still being supervised by my partner. I'm very greedy when I get laid and I especially love it when someone nibbles on me with delicacy. You have the right to leave us a message if you want to meet up with us for some sex. We kiss you.
Looking for a hot night with a woman in Houston?
Houston Tx Backpage Com
First name: Nida, Age: 35 yo, City: Houston (AK)
Hello everyone, I am a nymphomaniac woman who is 35 years old and whose name is Nida. I work in a lingerie store. I'm divorced because I want to be free with a lot of guys. Since I'm a cougar, I want a very young boy. I want a night of debauchery first and foremost. I'm also a naughty girl who loves sex. I'm here to show you how you should go about giving me an orgasm. You can set up a casual sex encounter, I'm available every afternoon. I'll let you choose the address but only on Houston. I want to have a man for sex because I love making love without limits with a new guy. I like trying new things, so I need a guy who is imaginative and can handle himself. I'm quickly waiting for a no-hassle appointment on Houston. I'm sure I'll have a blast with you. I'm already super hot at the idea of discovering you. Kisses.
I'm a young libertine in Houston who wants to have some fun
Houston Tx Backpage Com
First name: Yasmeen, Age: 24 yo, City: Houston (AK)
Hi guys, I'm Yasmeen and I'm single, I'm only 24 years old. I am very sexy. And I'm especially hot. Since I'm new to swinging, I want a good lay who knows how to do it. I want to be taken care of and be your thing so you can have fun with me and therefore have a lot of pleasure. I don't mind if we meet up at your place or somewhere else, as long as it's clean. I can move around easily in Houston and its surroundings. I am usually available during the day. A one-night stand should make me have an orgasm. I want a guy who is good with his tongue. Otherwise, I'm a fan of sodomy but in a gentle way. I'm for a plan cul in the woods if you're an exhibitionist. I want a naughty guy who loves to guide me during our naughty evening. I'm only here to get laid. I leave you in the meantime to discover your proposals to satisfy my most secret sexual impulses. I'm not looking for another plan so if you can't make me happy. Don't offer me anything. Keep me updated! Big, naughty kisses!
Looking for a hot date with my babe Houston
Houston Tx Backpage Com
First name: Aelia, Age: 29 yo, City: Houston (AK)
We are a mature couple and my name is Aelia. We love going on libertine dating sites to have fun between couples. I'm an amateur of candaulism because I love to have fun with another naughty guy but always being watched by my boyfriend. I'm very hot when I make love and I particularly like it when someone licks me languorously. I prefer men who are tbm and tall, but it is only a wish. I, on the other hand, require a man who is as assertive as my teddy bear. I want to moan like never before. We prefer to give you a date on Saturday and at our place or in a nearby libertine club Houston. If you want to leave a little note, we will be happy to look at it. I hope to meet you for a lovely libertine encounter. Kisses. Bye Bye.
- Oswego, IL Transex Escorts
- West Glens Falls, NY Transex Escorts
- Tijuana Trans
- Monticello, AR Transex Escorts
- Newarkescorts
- Saks, AL Transex Escorts
- Los Angeles Escorts Review
- Prostitution In Monterrey Mexico
- Ridgefield, NJ Transex Escorts
- Salem, MA Transex Escorts
- Chattanooga Tn Escort
- Orange Park Escorts
- Arab Transexual
- Escorts In Lahore
- Johnson City, NY Transex Escorts
- Boyes Hot Springs, CA Transex Escorts
- Port Isabel, TX Transex Escorts
- Escorts In Vancouver Bc
- Somersworth, NH Transex Escorts
- Conway, SC Transex Escorts


text:
Printer repair questions? Ask IT technicians for answers ASAP
Connect one-on-one with {0} who will answer your question
Wonderful service, prompt, efficient, and accurate. Couldn't have asked for more. I cannot thank you enough for your help.Freshfield, Liverpool, UK
This expert is wonderful. They truly know what they are talking about, and they actually care about you. They really helped put my nerves at ease. Thank you so much!!!!Los Angeles, CA
Thank you for all your help. It is nice to know that this service is here for people like myself, who need answers fast and are not sure who to consult.Hesperia, CA
I couldn't be more satisfied! This is the site I will always come to when I need a second opinion.Kernersville, NC
Just let me say that this encounter has been entirely professional and most helpful. I liked that I could ask additional questions and get answered in a very short turn around.Woodstock, NY
Thank you so much for taking your time and knowledge to support my concerns. Not only did you answer my questions, you even took it a step further with replying with more pertinent information I needed to know.Elkton, Maryland
He answered my question promptly and gave me accurate, detailed information. If all of your experts are half as good, you have a great thing going here.Dallas, TX
< Previous | Next >
Printer and Office Equip. Specialist
6,750 satisfied customers
Working as tech support specialist with a worldwide computer manufacturer.
1,844 satisfied customers
DIploma in Computer Hardware
MD Sadique
1,836 satisfied customers
Engineer in Applied Electronics & Instrumentation with 10 yrs+ experience in troubleshooting/repairing Printers.
962 satisfied customers
700 satisfied customers
IT Specialist, Print Server Administrator, MFP expert
370 satisfied customers
27 years of experience, with the last 20 being exclusively with printers.
316 satisfied customers
Copier and Printer Service Technician
< Previous | Next >
Disclaimer: Information in questions, answers, and other posts on this site ("Posts") comes from individual users, not JustAnswer; JustAnswer is not responsible for Posts. Posts are for general information, are not intended to substitute for informed professional advice (medical, legal, veterinary, financial, etc.), or to establish a professional-client relationship. The site and services are provided "as is" with no warranty or representations by JustAnswer regarding the qualifications of Experts. To see what credentials have been verified by a third-party service, please click on the "Verified" symbol in some Experts' profiles. JustAnswer is not intended or designed for EMERGENCY questions which should be directed immediately by telephone or in-person to qualified professionals.