View allAll Photos Tagged whitepoint
White Point, NS_RP1757710
When I told my friend, Del, that I was going to do the Cabot Trail, he gave me the name of a place in White Point and said stay there--you'll like it. And so, way up in the South Eastern corner of the Cape Breton Highlands north of Ingonish, I took a side road that took me 5 miles from nowhere. An overlook above the "town" looked down on a tiny harbor protected on three sides, and a spit of green beyond, broken off and dwindling out to sea--land's end. Del was wrong--I didn't like it, I Loved it. The town was dozen or so houses, and the B&B we stayed in was...rustic. No matter, this wasn't just remote, this was a vortex. There were vibrations here, a combination buzz of wind, sea, earth, and time. It was as if you could feel the people who had settled here, lived here, went to sea here, and from even far away, washed up here (there's an Unknown Sailor cross and graveyard out on the spit, bodies the sea currents carried here). The mountains came down and plunged into the sea, so bright, cold and wind-whipped, attacking the harbor with it's anchored boats, just below this little hillock. From here, sitting on a red chair, built for two--because this is not a place a man would make his life alone on purpose--you could look out and know what has brought you here.
This is a synthetic test image that tends to show if there are problems in your display or printed color. You probably want to use the original download in tests.
From top to bottom, on a vertical line, the color (hue) should stay the same. From left to right we cycle through hue rainbow. From the middle to the top we decrease the saturation. From the middle to the bottom we decrease the 'value', e.g. fade the 'base paint' to black. The color space is untagged, but it is supposed to render as sRGB, and uses 16bit per color channel.
Some history: The Granger Rainbow - by Doug Kerr
As an example of non-linearities that you can find. On certain modern screens when using a linear ICC profile, that transfers the RGB data unmodified to the screen, you will see that the display panel internally does a CIELab transform with a Look-up Table (LUT). For the 12" MacBook 2015 it is apparently a 17x17x17 Lab LUT. Between the items in the lookup table it will interpolate linearly. So with a test image that has the same luminance (L of Lab) horizontally, it is pretty clear that there is an angle every so many pixels of the image. My code uses floating point until it is converted to 65k5 color channel steps of RGB, so I'm reasonably sure these bands are not in there already.
Another example is with a 'Single curve + Matrix' ICC profile that works directly on the RGB channels. The matrix will mix the color curves in a linear fashion. Sort of rotating the curves at a fixed angle. You will see this back as curved horizontal banding in the center, and as forking bands to the top and bottom of the image. Sadly this is the only type of profile that is fully compatible with all apps on OS X 10.9 (2013) and later, due to bugs.
An example of a linear ICC profile is the "DisplayCal Visual Whitepoint Editor Temporary Profile". X-Rite's "DisplayProfile_Linear.icc" profile does not appear to be that linear (might be due to macOS bugs).
The image is sized for the original MacBook series screen resolution.
The image is generated using Python with pypng and colorsys.
Update: FireFox 3.1 added color management support. Chrome doesn't have it yet. See this article (under Off-color Remarks section).
01.27.10
Update: This article on Utata that does a good job of explaining color spaces.
09.08.06
::::
I've been bit by the color management bug. I've always noticed that the color of my photos vary quite a bit during their journey from photoshop to flickr... colors that are rich & saturated will sometimes appear washed out, faded, or desaturated.
It turns out there's a few factors involved (for my specific set-up):
—I've been capturing and editing in the Adobe RGB (1998) color space
—No web browsers (except Safari) support color management at this point.**
Which basically means the browsers don't read the embedded color profile; they just automatically assume all images are in the sRGB color space (more about that later).
—I'm editing photos on a 20" G5 imac (now using MBP + cinema display), which, besides having a very bright, high-contrast LCD screen, has (up to now) been using the Apple ColorSync monitor profile, which uses a 1.8 gamma (produces lighter images, versus the PC 2.2 gamma standard, which is darker).
In an ideal world, all web browsers would offer color management support, all end-users of flickr would embed color profiles in their photos (or have their editing software do it by default), and no one would spill soda pop on the seats of the bus, right? But it ain't so. Firefox (or IE, Camino, Opera, etc) doesn't care if your photo is in the Adobe RGB color space, and doesn't care if it converts it properly to sRGB. So what's the big deal— what's so bad about sRGB? There isn't anything wrong with sRGB... it does its job fairly well, all things considered. But it does have some limitations— it's a profile that's basically an average of the all low-end CRTs from the mid-nineties, so its primary purpose is lowest-common denominator compatibility, not accurate color reproduction of a wide color gamut. So it has a much smaller color gamut than, say, Adobe RGB (1998). In other words, it displays less color, but insures broader compatibility. More about sRGB here on wikipedia.
So I've made some changes in my photo processing workflow to compensate. The workflow goes something like this:
1) RAW images captured in camera
2) RAW images imported into LightRoom, processed, and exported to Photoshop
3) Photoshop is set to embed Adobe RGB profile in all images
4) Final product is soft-proofed (Windows Gamma 2.2 sRGB) then converted to sRGB via a programmed action (but original is saved in Adobe RGB for printing purposes)
5) .jpg embedded with sRGB profile is uploaded to flickr
I'm sure I'll be tweaking things around over the next couple weeks as I learn more. But it's a start.
For more in-depth info, check out Real World Color Management (Bruce Fraser, Chris Murphy, Fred Bunting).
(**= correction, pointed out by dcJohn: OmniWeb (for the Mac) also supports CM)
::::
I tagged this as White Point but that may be wrong. This cape can be seen in the background of an earlier image (NAL_3854-5_cr) featuring a small harbor.
NAL_3863
I was at Whitepoint Beach Lodge in NS - a rustic collection of cottages and a shambling main building with a relaxed feel about the place - eating breakfast with my daughter Lucy, who was yipping in the background, and reassuringly gorging on the second plate of bacon her vegetarian mother would never allow, and trying to make conversation after 30 years with Ian White, an Alsaw alumni.
I'd been reading Steven Heighton's The Shadow Boxer and the grey clouds reminded me of Lake Superior and I was yearning to be there. Amidst the open rolling sky country, or paddling on some river, or getting burnt paddling on the flat swells of Superior.
Something dragged me back ... I was here, where I needed to be, replete with yipping kid; cold, scudding clounds on a June summer day, beside the Atlantic Ocean. If I were in TBay or somewhere along Superior, I'd probably be wanting to be in NS.
How does this stuff work - the desire to be elsewhere?
New Nikon D70s with the ISO set, accidentally, to 1600 - hence the grainy feel, which I don't all together dislike.
White-point moth, Mythimna albipuncta. 1 June 2024. Ealing, London, England, UK.
Please contact me to arrange the use of any of my images. They are copyright, all rights reserved.
nikon fm2 + mc helios-81h 50/2 + expired kodak gold 200.
near white point (that big landslide), san pedro, calif.
I tagged this as White Point but that may be wrong. This cape can be seen in the background of an earlier image (NAL_3854-5_cr) featuring a small harbor.
NAL_3867
nikon fm2 + mc helios-81h 50/2 + expired kodak gold 200.
near white point (that big landslide), san pedro, calif.
Visit to the White Point Nature Preserve in San Pedro, California on Saturday October 24, 2015. This is part of the Palos Verdes Peninsula Land Conservancy. Really striking to see this Coyote crossing my pass - maybe 30-40 yards away.
nikon fm2 + mc helios-81h 50/2 + expired kodak gold 200.
near white point (that big landslide), san pedro, calif.
nikon fm2 + mc helios-81h 50/2 + expired kodak gold 200.
near white point (that big landslide), san pedro, calif.
A daylight long exposure of a small portion of a rocky shoreline. I used a Lee Big Stopper (ND) to block enough light to get into a longer exposure time.
Photo taken at White Point in Palos Verdes, CA (USA).
The influenza pandemic of 1918-19 was caused by what is considered one of the deadliest viruses in history, comparable to the "Black Plague" that swept through western Europe in the Middle Ages and killed millions. Influenza—or the flu, grippe, Spanish Lady, Flanders Fever, or Three-day Fever, as the disease was called variously—was even more devastating. It was a worldwide holocaust: more than 20 million people died (a conservative estimate, as records are incomplete and statistics unreliable). It affected every continent, nation, stratum of society, and ethnic and age group.
There is no discernible reason for its strange history; there was no geographical pattern or obvious path of transmission. It rampaged through the British Grand Fleet in the spring of 1918, but did not seriously menace the U.S. battleships attached to the fleet for months. German soldiers on the Western Front were afflicted seriously, but British tommies were not. American doughboys crossing the Atlantic to France on transports had a much higher mortality rate than the crews of the ships that carried them. Ships returning to the United States from the war zone had far fewer cases than those going over did.
There are various theories about the flu's origins: some say it started in Spain, others say in Asia, and still others say in the United States. Recent pathological research has concluded the flu may have originated with swine and percolated for an undetermined number of years, perhaps even trading back and forth between pigs and people before growing strong enough to become virulent.1 Some writers have determined there were two or three waves, but from 1916 to 1919 the epidemic ebbed and flowed for more than three years, finally becoming a pandemic. It gradually got worse in scope and severity, climaxing in the fall of 1918 before slowly subsiding in the winter.
The pandemic in the United States was a medical disaster of massive proportions. One authority suggests as much as one quarter of the population, 25 million, had the flu in 1918-19.2 As many as 700,000 may have died; this was more than the total U.S. combat losses in both world wars, the Korean War, and the Vietnam War combined.3
The flu struck the military services earlier and more severely than the civilian population. The Army may have had more than a quarter of its number down with the contagion at one time or another. Military camps in the United States became huge virtual hospitals, with entire barracks taken over as wards. Bases were so crippled that the Army's Chief of Staff urgently cabled General John Pershing in November 1918, "Influenza not only stopped all drafts calls in October but practically stopped all training."4 The American Expeditionary Force in Europe was not hit quite so hard. The hospital admission rate in the war zone was approximately 64% that of the rate of soldiers in the states; 167 out of every thousand fell ill with the disease. Altogether, 12,423 U.S. soldiers in Europe died.5
A much larger number died on the troop transports. "The worst place to have an epidemic, like a fire," writes one authority, "is in close quarters far from help, such as a ship on the high seas."6 Troops literally were packed in the compartments of the transports, making it likely that if one person caught the disease, all in his immediate proximity soon would come down with it. In the last six months of the war, while the pandemic was spreading rapidly throughout the world, 1.5 million doughboys crossed the Atlantic to British and French ports. Transports often were crowded with the sick and the dead. One convoy commander radioed London that more than "1,300 cases of virulent pneumonia and influenza in convoy, 49 deaths." Admiral William S. Sims, Commander-in-Chief of the U.S. naval forces in Europe, threatened a quarantine, but it proved to be "politically impossible."7
Though few in the crews of troop transports fell ill, this was not true of the Navy as a whole. The cruiser Minneapolis (C-13), while moored at the Philadelphia Navy Yard in January 1918, saw the first noticeable outbreak of flu. In a two-week period, 21 members of her crew came down with the disease. Within a month, the Bureau of Medicine and Surgery was receiving reports of numerous cases in ships and bases scattered along the Atlantic seaboard.8
The epidemic soon spread to the naval forces deployed in the war zone. In March, a comparatively mild epidemic of influenza and pneumonia showed up among the naval personnel stationed at Brest and the U.S. naval air stations in Gujan and Fromentine. The disease spread quickly to the crews of escorts operating out of Brest. One of the surgeons at the U.S. naval hospital there wrote in early July that 30 members of a destroyer's crew became incapacitated with the illness. "We were thinking of taking them ashore," he wrote, "so as to fumigate the ship when came the call of a torpedoed ship. Every man slid into place, fever, headache, bone ache and all, and away she beat it to sea [to] pick up the survivors."9
Influenza also spread among the U.S. sailors based in Great Britain. Even the London Headquarters staff of the U.S. naval force in European waters was affected. On 30 June, Commander T. A. Thomson, Admiral Sims's chief medical officer, reported that, "My entire office is out of commission with influenza, including myself." Nonetheless, he predicted optimistically to Surgeon General William Braisted at the end of July that there were only about 1,500 cases in the entire naval force, and that the epidemic was about over.10 Commander Thomson tragically was mistaken; a far deadlier strain had been sweeping through Asia, and even as he wrote to the Surgeon General, British civilians were dying by the hundreds.11
Washington officials were not especially alarmed over the flu in August. Medical officers still reported evidence of the disease at home and abroad, but the number of cases appeared to be decreasing. This changed toward the end of the month. Cables arrived from Brest with the news of a massive and deadly outbreak among French military personnel. Meanwhile, the Navy Department was notified of an eruption of the malady in Boston, which initially targeted the bluejackets crowded on a receiving ship moored at the city's Commonwealth Pier. On the last day of August, as the city focused on Babe Ruth pitching the Red Sox to the American League pennant, 106 sailors on the receiving ship came down with the flu. By the first week of September more than 2,000 officers and sailors in the Boston area were stricken. There were so many patients at Chelsea Naval Hospital that tents had to be erected on the lawn to handle the overflow. Before it was over, 26 sailors in the Boston area died from the disease.12
The new epidemic reached the Atlantic Fleet and other shore installations in September. By the end of the month the Great Lakes Training Station near Chicago had nearly 10,000 down with the illness—so many that one sailor estimated half the barracks had been converted into temporary hospital wards. By the beginning of October, some 31,000 sailors, most of them on shore facilities in the states, had been stricken, and more than 1,100 had died.13
In the war zone, the new and more deadly strain appeared first among the U.S. naval forces in French waters. Inevitably, Brest was battered by the disease. Flu already had ravaged French sailors and civilians in the district. To compound the situation, troopships from Norfolk, Boston, and other U.S. ports debarked thousands of doughboys weekly, many of whom brought the pestilence with them. A sailor on the President Grant (SP-3014) claimed years later that so many died on the transport that members of the crew, when not on watch, were required to prepare the deceased for burial. "I stood my watch in the radio room," he wrote, "and when off watch I turned to and helped sew up some of the dead soldiers till my fingers bled. We used a palm and needle rig to cross-stitch thru the canvas."14 Marine Brigadier General Smedley Butler wrote his family after arriving at Brest: "We had a hell of a trip over, an epidemic of Spanish influenza breaking out among us…We had at one time fully 500 cases of influenza…I suppose it is one of the awful results of this devilish war…terribly hard to bear, this loss of your men when you can't help them."15
During the three-month period from 15 September to 15 December, the patient load at the U.S. naval hospital in Brest averaged 800. In the end, more than 2,000 U.S. servicemen died in Brest from influenza.16
The autumn Spanish Flu epidemic was widespread in Great Britain. In September, 14,000 died. The weekly death tolls mounted steadily, reaching their peak in the last week of October, when the total was 4,000. More than 18,000 died in London alone from September to December. Even the Prime Minister, David Lloyd George, came down with the flu in September.17
Other than London, the cities hardest hit were the port cities, particularly Liverpool and Southampton. Luckily for the U.S. Navy, few of its personnel were in those cities. The ports that did have large numbers of sailors, however, were not so lucky. The southern Irish town of Queenstown, which had become the largest U.S. naval installation in the British Isles, saw a large number of cases. Throughout October, the number of new cases averaged 25 to 35 daily. When the new naval hospital at Whitepoint opened in late October, 150 patients were admitted immediately, all with the flu.18
The sailors stationed on the battleships and other naval vessels concentrated near Berehaven in Bantry Bay in southwestern Ireland suffered the most from the epidemic. By the middle of October, a third of the Utah's (BB-31) and Oklahoma's (BB-37) crews were down with the disease. One of the Utah's officers recalled in his oral history that one Sunday in October he went hiking with several officers from the Oklahoma, including the ship's gunnery officer, and a few days later the gunnery officer was dead from the flu.19 The Nevada (BB-36) experienced few cases until the second week in October, when the number began to escalate. As the ship's history recorded, "The end of the month found us riddled of the disease." A member of the ship's company wrote in his diary on 21 October, "a large percentage of the ship's crew is sick with Spanish Influenza." A few days later he remarked, "The general spirit is gloomy, everyone sees many of his shipmates groping around looking like hooded ghosts…One can tell by the expression on each face that they are battling to their utmost to keep going, for this is the surest way to down the dicease [sic]." He also mentioned in his diary that the sick bay line was sometimes 50 or 60 feet long." Altogether, 11 of the Nevada's sailors died.20
Personnel on the U.S. dreadnoughts attached to the British Grand Fleet, which suffered heavily from the flu, also were affected seriously. There were more than 600 cases on HMS Revenge. The battlecruiser HMS Princess Royal was so devastated that tugs were moored alongside to provide essential services. Some ships had to borrow personnel from sister ships to go on patrol.21 In the U.S. squadron, according to one former officer, the Arkansas (BB-33) had "in excess of 1,200 cases" of the flu; this was in a total complement of about 1,500 men. "Everybody sick with the flu," a bluejacket on the Arkansas wrote dejectedly in his diary. Admiral Harry W. Hill, in h is oral history, recalled that, "On both the Texas (BB-35) and Wyoming (BB-32), we had more than half our [crews] incapacitated at one time or another. They were so numerous they couldn't be handled in sick bay, and had to be taken care of in special areas set up in various places in the ship."22 Admiral John McCrea, who was on the New York (BB-34) at the time, said in his oral history that, "We had a hell of a time with it. We lost something around 14 or 15 people, including a couple of officers…There were 10 officers…whose rooms were forward of the wardroom. I was one of the 10…and I was the only one in that part of the ship [who] didn't have the flu."
When the Grand Fleet had to sortie once during the epidemic, several British warships did not have enough healthy men to get under way. All of the U.S. battleships, however, managed to join the fleet as it steamed out of the Firth of Forth. Fortunately, it was a false alarm; morale in the German High Seas Fleet had deteriorated to the point that it was unable to go to sea. Admiral McCrea recalled that if the German fleet had come out at that time, "the result could have been disastrous for the Grand Fleet…[The epidemic] was bad, bad, I can tell you."23
Despite the large number of personnel in the squadron stricken with the flu, there were very few fatalities on the U.S. dreadnoughts—fewer than 30.
Of all the U.S. naval vessels affected by the epidemic, the one most savaged by it—the cruiser Pittsburgh (CAA)—was not in the war zone. While visiting Rio de Janeiro, her crew became so crippled by the disease that the ship could not sail. About 80% of her crew was affected, and 58 died, the most in any Navy ship.24
Admiral Sims, the European naval force commander, became increasingly concerned about the severity of the fall outbreak of influenza. In early October he cabled the Navy Department that "there is no doubt that this [epidemic] is now a greater danger to people on ship-board than the Submarine is." He appealed to Chief of Naval Operations Admiral William S. Benson to send two hospital ships to European waters immediately. He also strongly urged Washington officials to reduce significantly the number of troops—up to 50%—per transport. "Many deaths," Admiral Sims wrote, "have occurred and many more expected. Immediate drastic measures should be adopted to avoid serious loss of life…[and] official public outcry and possible investigation by Congress."25
By and large, it was left to individual commanding officers and medical personnel to handle the crisis. Unfortunately, there were few guidelines and even fewer effective medicines. Vaccines were virtually unknown in the days before antibiotics. In general, doctors relied on fresh air, bed rest, simplified diet, and quarantine. Quinine, aspirin, and whiskey were the most common drugs used to treat victims. Preventatives from coffee to throat and nose sprays were tried on most ships. One ship's surgeon, however, advised the Bureau of Medicine and Surgery that "the less medicine given by mouth," the better the chance of recovery. After the epidemic, the bureau concluded that quarantine was the most effective preventative.26
The pandemic lingered on into 1919 before finally disappearing. The Navy, one authority claimed, kept more accurate records than did the U.S. Public Health Service concerning civilian cases. He concluded that at least 40% of the Navy's personnel had the flu. This may well have been a conservative estimate, since an undetermined number of ill sailors evidently did not report to sick bay. According to records, 5,027 Navy personnel died from influenza or complications. This was more than twice as many as those who died from enemy action.27
The Navy was heavily affected by the pandemic. Crews were decimated, ships were delayed in sailing, and medical facilities were taxed, but as one surgeon wrote, "We can't stop this War on account of Spanish or any other kind of influenza."28 Navy veterans of the Great War never forgot the pandemic. In memoirs and oral histories, they recalled the suffering and dying. "What do you recall thinking and experiencing at the time?" asked one historian. "Mostly flu," the sailor replied. "Men were dying every day."
www.usni.org/magazines/naval-history-magazine/2002/april/...
Photomatix settings:
HDR Settings:
Align (3 RAW) source images
Attempt to reduce ghosting artifacts (very windy day)
Moving objects/people... Detection = High
White Balance: As shot
Tone Mapping:
Strength = 46
Color Saturation=63
Lightsmoothing=Very High
Luminosity=0
Whitepoint=.559%
Blackpoint=0%
Gamma=1.00
Microcontrast=10
Micro-smoothing=15
Using Details Enhancer
Full spectrum D70 with S8612 + BW403 stack. 30", f22.
WavelengthPro actions:
1) Dual Process (200%)
2) Colour-Space map (interpret YUV as YIQ)
3) Whitepoint scaling (in RGB)
The images on the left lack contrast.
The images to the right have been adjusted to increase contrast, so that they have richer blacks and truer whites.
Post Processing Tutorial:
Using Curves: adobe.ly/X9WrSP
The starting point of AROTIN & SERGHEI’s art installation WHITE POINT for the Deep Space 8K is the smallest possible visible image: a single shining white light pixel of the matrix of 66 million of the 16 m x 18 m projection space is shown pulsing in the rhythm of a heartbeat. It moves gradually to the viewer and takes the whole space of the building. In the radical enlargement one can discover the structure of this white light point, a cube made of red, blue and green light cells dissolved by the brightness contrast of pulsation into visible and invisible phases.
Credit: AROTIN & SERGHEI
Shortly after takeoff on a Delta Air Lines Boeing 717 from the Destin - Fort Walton Beach Airport to Hartsfield-Jackson Atlanta International Airport. Choctawhatchee Bay and White Point can be seen out the left window.
A g'Akh terraformer as witnessed by me. Their technology emits only in the high UV-range, why it is not visible to the human eye (especially not when the sun shines). Only at night and after removal of the ultrahigh pass filter you can take a photo of them. They are preparing earth to suit the climate of their homeworld by blowing huge amounts of CO2-gas into our atmosphere. Except for our mastermind G.W. Bush we still think that global warming is our fault.
Wait for the day of their unfriendly takeover and you will realize what sort of dumbasses we have been...
P.S.: No photoshopping involved except for setting the whitepoint (hint!)