text:
Humors, Hormones, and Neurosecretions
Chandler McC. Brooks - Editor
ISBN10: 0-87395-006-2
ISBN13: 978-0-87395-006-0
The concept of humoral control—the direction of bodily processes by complex organic fluids—has gained ascendancy in recent decades, and enlisted the interest of more than humoral specialists. The present summary of current humoral research accordingly pays particular attention to its bearing on physiological theory, and its contribution to our general knowledge of the integrative forces which maintain the unity of the individual.
The ancient theory of the four hundred, which dominated medicine from the time of Hippocrates to the beginning of the seventeenth century, contained in rudimentary form the notion that chemical agents transported in the blood controlled biological and emotional states. This notion was apparently discredited forever in the eighteenth century when it was supplanted by the galvanic theory that control was exercised through electrically transmitted neural impulses. Near the beginning of the present century, however, experimental evidence in turn discredited the electrical theory, and laid the groundwork for the modern humoral concepts discussed in these pages.
Specifically covered are the development of endocrinology, the discovery of digestive hormones, hormonal regulation of metabolism, the action of trophic hormones, interactions within the endocrine system, chemical transmission of neuronal impulses in the central and peripheral nervous systems, and the control exercised by the central nervous system, particularly the hypothalamus, over endocrine and other secretory processes.
Chandler McC. Brooks, Ph.D. is Professor and Chairman, Department of Physiology, and Director of the Graduate Educational Program, Downstate Medical Center, State University of New York.
Jerome L. Gilbert, M.D. and Harold A. Levy, Ph.D. are Associate Professor and Assistant Professor of Physiology, respectively, at the Downstate Medical Center, State University of New York.
David R. Curtis, M.D. is Visiting Professor from the Department of Physiology, Australian National University, Canberra, Australia.
Section I. Introduction
1. The Concept of Humoral Control of Body Function and Its Significiance to the Development of Physiology
C. McC. Brooks
Section II. The Development of Endocrinology
2. The Beginnings of Endocrinology and the Discovery of Digestive System Hormones
3. Hormones and the Metabolic Processes of the Body
The Pancreas, Adrenals, Thyroid, Parathyroids, Thymus, and Pineal
J.L. Gilbert
4. Trophic Hormones and Interactions Within the Endocrine System
The Hypophysis and the Gonads
H.A. Levey
Section III. Chemical Transmission of Neuronal Activity
5. Chemical Mediation of the Neural Control of Peripheral Organs and the Humoral Transmission of Mediators
6. Central Action of Transmitters and the Question of Chemical Transmission at the Central Synapse
D. R. Curtis
Section IV. The Central Nervous System and Humoral Control of Body Function
7. Central Nervous System Control of Endocrine and Other Secretory Processes by Peripheral Nerves
8. Hypothalamic and Central Nervous System Control of the Endocrine Glands
22468/(//)
Hegel's Theory of Madness
Moral Personhood
Indeterminacy and Intelligibility
The Hermeneutic Tradition
Art, Alienation, and the Humanities
The Difference Between Fichte's and Schelling's System of Philosophy
Merleau-Ponty, Hermeneutics, and Postmodernism
The Necessary Angel
Ethical Vegetarianism
Averroes and the Metaphysics of Causation


Fifteen talented Outskirts Press self-publishing authors took home 1st-, 2nd- and 3rd-Place awards at the prestigious annual independent book awards competition.
Outskirts Press hand-selects only the highest quality books for EVVY Award nomination, generally only 2 to 5 percent of the books published in any given year.
Outskirts Press Inc., a Denver-based self-publishing company, has had 15 authors awarded in the annual CIPA EVVY Awards ceremony Aug. 19, 2017, in Denver, Colorado. The company, rated the No. 1 self-publishing company according to Top Consumer Reviews, nominated 47 authors for the prestigious independent book awards and garnered 21 nominations.
Now in their 23rd year, the CIPA EVVY Awards are sponsored by the Colorado Independent Publishers Association (CIPA) and the CIPA Education and Literacy Foundation (ELF), and recognize the finest works of independent authors in dozens of book categories.
Outskirts Press hand-selects only the highest quality books for EVVY Award nomination, generally only 2 to 5 percent of the books published in any given year. These winners will now be eligible to compete in the annual Outskirts Press Best Book of the Year Award , which is determined by a vote of readers of Outskirts Press' Self-Publishing News blog. The winner will receive a $1,500 grand prize.


Jacob was only 13, but he had a history of arson, marijuana use, solvent abuse and shoplifting. He associated with anti-social peers, was medicated daily for ADHD and was only attending school for two hours each morning—during which he was frequently sent home due to disruptive behavior. He had been to the board of trustees twice already. A third serious incident of disruptive or unsafe behaviour would likely end in exclusion (expulsion). That's when he was referred to Multisystemic Therapy (MST).
It is funny how the universe finds ways to answer the desires of the heart. Almost 20 years ago, I was a young missionary in the community of La Florida in Santiago, Chile. I came to love the Chilean people and was fortunate to have many close friendships with the Chilean women I met. They took care of me and made me part of their families.
As a surrogate family member, I was privy to the many heartaches and trials these women faced in rearing their children.


text:
One Night at Sea
November 29, 2014 ZekeTheSailor 8 Comments
It's never just one thing going wrong that gets you in trouble…
Sailing along the Florida coast south from St Augustine, we had one of the most delightful sailing days ever, and the forecast was for continued clear skies and 15-20 knot favorable winds. As the sun set we took down our spinnaker and sailed with the more easily controlled "screecher" (a big forward sail, that can be rolled up with minimal fuss if the wind gets too heavy).
After sunset the wind shifted aft, until it was almost directly behind us. In that situation the mainsail "blankets" the forward sail, causing the latter to lose its wind, collapse, and then fill with a jarring crash. So we rolled up the screecher and sailed with just the mainsail. As the wind continued to build on Bill's watch, he put in a reef (decreasing the exposed sail area), and he gybed the boat to head offshore to clear Cape Canaveral.
At 11pm I started my four hour watch, after not much sleep due to the now rough conditions. Bill briefed me that in the course of gybing, our apparent wind indicator (a sensor at the top of the mast transmits the wind direction to a display on our instrument panel) apparently was partially damaged. It still "worked," in the sense that it was consistent, but it showed the wind from astern as though it was from ahead! So he was ignoring the instrument display, and looking at the vane on the masthead to determine the wind direction (tough on the neck!).
Not long after Bill turned in, it seemed to me that we had made enough distance off from Cape Canaveral, and we should gybe back to run parallel to the coast. It's a bit of a process to gybe, especially when you're not entirely clear-headed. I first checked the instrument that reads the true wind speed. It read 15 knots. This seemed much lighter than what we had been experiencing, so I decided it was a good time for the maneuver. Out in the cockpit the wind seemed much stronger than that, but I still figured that if it went down to 15 even for a moment that was a good sign to proceed. I sheeted the main traveler in to amidships. With the mainsail pulled in that way I could tighten the "lazy" starboard running backstay, to support the mast when the sail/boom comes crashing over to the new/port side. I left the running backstay tight on the port side also, figuring I would release it after the sail came across. Then I switched the autopilot to "standby" and turned the wheel to starboard. The big mainsail did its expected crash over to port, and in the big seas I did 30 seconds of erratic steering to find the right new course, and set the autopilot back to "Auto." Then I eased the starboard side traveler line to let the sail out on the new side, and went back into the pilot house to see if our new course would allow us to sail parallel to the Florida coastline.
Then there was a JOLT and a BANG in the rigging!
Hurrying back outside, I initially couldn't find anything wrong, but a quick survey revealed that the port side running backstay had disappeared. I had neglected to ease it before I eased the traveler out on the new side. Thus the entire force of the wind in the big sail was pushing against that runner, until something gave way. The good news: on the new gybe we didn't need the port side runner. The bad news: if we needed to gybe back later, and the wind was still blowing hard, the mast wouldn't have the protection provided by the runner, and we could potentially be at risk of losing the entire rig!
Let's review what has gone wrong so far… We expected the more moderate winds as stated in the weather forecast, and weren't really prepared for a rough night. Bill's first gybe had somehow damaged the apparent wind indicator, making it difficult to set/hold our course relative to the wind. I had believed the true wind speed indicator when it showed 15 knots, without putting two and two together — that in order for the instrument to compute the true wind speed it factors in the apparent wind angle. The damage to the apparent wind indicator was causing it to "think" the wind was coming from ahead (and thus it subtracted out our boat speed) when in fact it was coming from behind (so it should have added our boat speed). When it read 15 knots, it was really blowing close to 30, and my thought that there was a lull had no basis. Then I omitted a step in the second gybe, resulting in breaking the port side running backstay.
So what to do next…?
In order to sail parallel to the coast, the wind and seas were now coming from almost dead astern. The seas were building, and we were surfing at speeds that we hadn't experienced before. At one point the knot meter indicated a boat speed of 17 knots! Fourteen knots or more was becoming common whenever a big wave lifted our sterns and the boat accelerated downhill. But this was not fun; it was hairy. The seas push the stern of the boat this way and that, and the autopilot can't respond quickly enough to keep the boat on a steady course. If the boat "yaws" to starboard, it doesn't much matter, except that our course goes closer to shore. If it yaws to port we risk an "accidental gybe," where the wind gets on the wrong side of the big mainsail, and it and its heavy boom come flying across the stern of the boat out of control, potentially breaking something more serious than the runner!
In most situations we would reduce this risk by setting a course a little closer to the wind, so the boat would have to turn further before it would gybe, thereby giving the autopilot time to respond. But such a course would point us in to the Florida coast, and before long would force us to gybe out to sea again — a dangerous prospect without the port side runner. But if we didn't change course that way, we risk the even greater risk of an accidental gybe. The heavy weather spinnaker would have allowed us to sail our desired course with no risk, but rigging the spinnaker is too complex to do in the dark. Some line would become tangled and create a new set of problems. The working jib alone would have provided enough power to keep us moving fast, but I had two concerns about that solution. First, it is not easy to get the mainsail down when sailing downwind. I certainly could not do it alone; I was very reluctant to waken Tim or Bill in the middle of my watch; and I wasn't even sure that two of us could safely do it in these conditions. Probably we could, perhaps with some assistance from the engines, but the second concern was that we really should have both runners in this wind when flying just the jib.
Although "hope" is a poor strategy, it was my hope that we could hold the course parallel to the coast at least until the wind eased. I rigged a "preventer" line, holding the boom out to port, so that if we did gybe accidentally it would not fly across the stern with damaging force. We sailed very close to the desired course for the next hour and a half.
During this time I learned to interpret the apparent wind angle shown by our instrument. Although it was wrong, it was possible to compute the correct angle from it, and doing the mental adjustment was easier than constantly looking up at the masthead vane. But then a "funny" thing happened. The instrument showed that I could bear off a little further away from the wind, and thus away from the coast, which was good. And then it indicated that I could STILL bear off a little further. I believed that the wind was changing, allowing us to more easily sail the course we wanted. It seemed that my hope was realized, and I felt deep relief. And just then the boat gybed! At the time I couldn't understand why this happened, but now the wind was on the wrong side of the mainsail, with the boom/sail held there by the preventer, which had prevented any dire consequences. The boat was effectively "hove to," with the wind blowing over the side, and the boat drifting sideways. It was relatively peaceful, except for the waves, and my mental wrestling with not understanding what caused the gybe. Maybe we were getting a new wind in my hoped-for direction, as I had thought, but were still getting gusts from the old wind. In any case, what to do now? Normally one would ease the sail over to the other side, which would start the boat sailing again, and then make whatever adjustments needed. But I didn't want to do that without the port side runner, and with no forward movement through the water, we couldn't steer to tack or gybe. I decided it was time to wake Tim and have a second brain pondering the situation.
In fact our solution was simple. Start an engine and get enough way on so we could steer downwind and gybe back. Could have done that myself. Oh well, it was a relief to have Tim say he would start his watch early and I should get some sleep. Tim managed to sail along the coast with just one time of rounding up into the wind and again having to start an engine to get going again. The "hope" strategy did in fact work out.
In the morning it became clear why we had gybed. The apparent wind indicator had frozen up entirely. So I was making mental wind angle calculations based on a display that no longer had anything to do with the wind! Also in the daylight we retrieved the running backstay, and found that it was a shackle that had broken. Easily replaced.
So in the end, no problem — just another night at sea.
nightsailing
SC to FL
I thoroughly enjoyed our relatively long stay in Charleston. I could even imagine living there.
Bill's daughter Nora joined us.
We left at dawn in the rain, and headed down the ICW. One engine overheated. Tim determined that the belt for the cooling water system was loose. He tried to tighten it (it's very difficult to access, especially when the engine is hot), but it still overheated. No problem, we only need one engine for tootling along the ICW. Then the second engine overheated, and we had an emergency anchoring drill (in the rain, and strong wind, and strong current).
We checked the filters on the cooling system, and found they were full of gunk. In retrospect, that's not surprising, since the place we stayed in Charleston was so shallow that our props stirred up lots of muck. After cleaning them, things have worked. Except when we tried to get the anchor back up we got the rope jammed in the windlass.
We went through some fascinating creeks (up one, through a cut, down the next, current first with us, then against us). Without GPS and a good chart, one could go in circles here!
We decided to anchor mid-afternoon in a middle-of-nowhere creek. The wind and rain came up hard just as we got in. Everything on the boat was wet. But in spite of the problems, I was happy to be moving again. It even occurred to me while we were dealing with our issues that it was kind of funny that I was enjoying it all!
Next stop: Beaufort, SC, at a delightful marina across the bridge from downtown. Showers. Laundry (more importantly a dryer). More wicked good food. Fun walking around town.
We need to move on in the morning. Stocked up with treats from the bakery, and headed out once again in the rain. Though it was calm as we motored down the Beaufort River, strong northerlies were predicted, so we decided to head offshore and reel off some miles. Indeed, last night was challenging, with rain squalls and gusts up to 40 knots, and sustained winds of 30. Occasional bone-jarring crashes of waves against the side of the boat.
Selfie after a tough night
Nora after a tough night
But by noon today we were on a mooring in St Augustine, eating the rest of the treats from the bakery. And the sun is now out and we get to dry our stuff!
I'm excited that we have made it to Florida. But only a brief visit to town this evening, as we plan to head back outside in the morning to take advantage of the north wind, this time expected to come with sunny skies. That could make for a happy Thanksgiving, in spite of being away from family and the traditional feast.
engine problemsICW
To Charleston, SC
Video November 20, 2014 ZekeTheSailor 7 Comments
A nice spot to anchor along the ICW:
Heading offshore:
New heavy-weather spinnaker:
As the wind eased we tried our other new spinnaker:
Dolphins (look carefully!):
Charleston Harbor:
Five delightful days in downtown Charleston!
ICWMarine lifesailing

redpajama_set_name: RedPajamaCommonCrawl


Betting Tip: Valencia kept themselves in their customary Champions League spot with a narrow win over Zaragoza in midweek and they will be confident of adding another three points to the tally against struggling Getafe. But Unai Emery's men have only scored one goal in each of their last six so Valencia with under 2.5 goals in it looks tasty at 13/5.
Betting Tip: Villarreal are in freefall after no wins in seven and preparations for Rayo's visit won't be helped by the impending Champions League clash with Manchester City in midweek. Vallecano are on the up after successive wins over Betis and Malaga and the gulf in confidence between the two sides will be reflected by a Rayo win at 27/10.
Betting Tip: Barcelona have slipped from top spot after being held by Sevilla last weekend and that was followed up by a slim win over whipping boys Granada. The previously free-scoring Barca have struck just once in their last two games but remarkably they've kept seven clean sheets on the bounce. Mallorca are averaging less than a goal per game in occupying 13th so expect another routine victory for the champions. A multiple score of 1-0, 2-0 or 3-0 Barcelona is 8/5.
Betting Tip: Real Sociedad have lost four out of their last five with the only anomaly being a 0-0 draw with Getafe, so the last team they want to see is free-scoring Real Madrid. Los Galacticos have plundered a remarkable 28 goals in winning their last seven games so expect something similar to occur in San Sebastian on Saturday. It's difficult to look past a Madrid win with over 3.5 goals in the game at 13/10, although backing Cristiano Ronaldo at 9/4 or Gonzalo Higuain at 5/2 to score two or more may be worth a few quid.
Betting Tip: Sporting have won two in a row after a horrible sequence of seven defeats from eight but they will face stiff opposition in making it a hat-trick from a Bilbao side who are unbeaten in their last seven, winning four. The Basque men are stubbornly difficult to beat and they will have enough to edge this one in a low scoring encounter. Bilbao to win with under 3.5 goals at 5/2 is a licence to print your own.
Betting Tip: Little Levante just keep on going. An injury time winner against Sociedad in midweek meant the 'Granote' – or frogs, to give them their rather unflattering translation – head La Liga on merit by a point. After drawing their first two games they have won an amazing seven in a row to thus far make a mockery of suggestions this league was nothing more than a two horse race. They've made a fool of many a man so far this season but I think they could finally have met their match in Osasuna. The Pamplonans are strong at home and have won two and drawn two this term. All good things must come to an end, although Levante should make do with sharing the points at 9/4. I hope they prove me wrong.
Betting Tip: Betis have fallen away woefully after briefly topping the table after four rounds. They've lost their last five and lost their way to goal too over that period, notching just once at the Bernabeu. Santander are the only side in the division yet to record a win, and likewise with just six goals scored all season they're about as threatening as a Greenpeace activist. Neither are making too strong a claim for the three points so get on the draw at 9/4.
Betting Tip: Atletico were threatening to put something together at the end of September but that notion has disappeared in a winless streak of seven games. Despite a wealth of offensive talent they are struggling to score and they combine that with the unenviable trait of leaking like a sieve. Having said that, Zaragoza are hardly in the rudest of health and are without a win away from home all season and have lost the last two. The head says Atletico must get it together at some point but the head also says stay away from the win at 2/5. Atletico to nick it 2-1 is a well priced 15/2.
Betting Tip: Malaga have recently hit the expected travails which come when you hurriedly cobble a team together. They've lost their last three without scoring and have shipped in nine goals in the process. Espanyol are up in sixth place and have won four of their last six 1-0 so both sides seem well placed to split the honours at 5/2.
Betting Tip: A last minute penalty save in the Camp Nou kept Sevilla's unbeaten start to the season going and they will be looking to strengthen their Champions League credentials with a win over bottom club Granada. A narrow defeat to Barcelona in midweek showed Granada's durability and even if they rarely get hammered they are extremely limited going forward having found the target only twice in nine games. Expect the status quo to continue with a multiple score of 1-0, 2-0 or 3-0 to Sevilla available at 13/10.


A confusion is eating his mind from the inside. The world that he grew up in and the world he is living in right now are at loggerheads with each other. He needs to save the former from the latter. John Clayton III has been living the life of a civilized man for quite some time now. With his beloved wife Jane by his side and a bunch of adorable cherubs, John is settled in Victorian London. His life is as happy as it could be; but he still years for the jungle- the jungle where he grew up, the jungle which was once his home, the jungle where he was popularly known as Tarzan.
As if the universe head his thoughts out aloud, John has been invited back to the Jungle. Unaware of the fact that he is a pawn in a deadly convergence of greed and revenge, for John Clayton it's an offer his heart can't seem to refuse. With all the makings of a summer blockbuster, the trailer seems to have caught the fancy of the audiences across the world. Having been embroiled in a production controversy during the film's making, the first look at the footage makes it look as if the hard work and the anxiety was worth it all along. With all of the vine swinging, gorilla fighting, machine gun toting activity within the two and a half minute of the trailer, it's definitely safe to say that David Yates ' Tarzan won't be seeing the lights of your drawing room anytime soon.
As per popular discussions, the most remarkable decision that the makers of The Tarzan have taken is to not base the film on any of the novels. The focus rather is on the infant boy who was raised in the jungle, who went on to live as a common man and has now returned back to fall into a trap he knows nothing of. In short, the focus of the story is on Tarzan just the way we know him, just the way we connect to him.
Being the only major action-adventure release for the first weekend in July, the filmmakers have definitely managed to make a movie that a large audience will be able to see without too much trouble. Yes, it is touted to be intense but then again, it would not really be a Tarzan movie unless we see our muscle-bound hero amongst the green and gorilla's right?


text:
from os.path import dirname, join, abspath
import sys

def addPath(dir):
    if dir not in sys.path:
        sys.path.insert(0, dir)

thisFile    = abspath(__file__)
thisDir     = dirname(thisFile)
appPath     = abspath(join(thisDir, '..', '..'))
consolePath = join(appPath, 'console', 'app')
gaePath     = abspath(join(appPath, '..', 'google_appengine'))
gaeLibPath  = join(gaePath, 'lib')
yamlPath    = join(gaeLibPath, 'yaml', 'lib')
webobPath   = join(gaeLibPath, 'webob')
djangoPath  = join(gaeLibPath, 'django')

# Go in reverse priority order due to to the insertion mechanism.
for dir in (consolePath, appPath, gaePath, yamlPath, webobPath, djangoPath):
    addPath(dir)

redpajama_set_name: RedPajamaGithub


text:
Fates on paper:
New documents in the online archive
The Arolsen Archives have added around a million new documents to their online archive. These latest additions include pictures of prisoners and transport lists from Auschwitz concentration camp as well as thousands of letters written by Soviet forced laborers to their families. A comprehensive collection of documents from the British and French occupation zones can now also be searched for the names of victims of Nazi persecution.
"Be good to me, little sister, I have not forgotten you and I will never forget you. You are angry with me for not sending postcards. I have already written three postcards, but I don't know why you don't get them," wrote Maria Borodinja to her sister Anna in April 1943. Her postcard is one of thousands of documents from a new collection in the online archive of the Arolsen Archives that contains letters from Soviet citizens who were deported to Germany as forced laborers and wanted to write to their families back home.
*Names cannot be equated with people. Some of the names of people persecuted by the Nazis appeared on several documents and were therefore counted more than once.
Sometimes the forced laborers also attached photos to their letters and postcards.
But their relatives very probably never received these messages. Today, they are stored in Ukrainian state archives, which are now trying to return undelivered letters to the descendants of these so-called Eastern workers. The Arolsen Archives have received copies of the documents and have added them to their archives with the aim of making more information about forced laborers available.
See the collection of letters in the online archive
Digital information at your fingertips
To make it possible to search the documents in the online archive of the Arolsen Archives for keywords, not only are a large number of staff involved in digitizing the documents, they are also busy indexing them. Important pieces of information such as names, locations, and dates must be typed out and linked to each individual document. State-of-the-art technology for fast data retrieval provided by our partner, the World Holocaust Remembrance Center Yad Vashem, also helps to make the documents more searchable.
Watch this video to get the best tips for your search in our online archive:
New documents on Auschwitz
The Arolsen Archives have been working with the Auschwitz-Birkenau State Museum for two years now to provide access to more information on the names and fates of the people who were imprisoned there. As a result of this partnership, the well-known Photos of male prisoners taken in Auschwitz can now be accessed in the online archive. In addition, students taking part in our "Every Name Counts" project have been working on Transport lists (to and from Auschwitz and other camps), which can now be searched for individual names.
Deportation lists from Vienna
By entering into a new cooperation with the Documentation Center of Austrian Resistance in Vienna, we have been able to add deportation lists of Jews from Austria to the online archive. These documents were already available beforehand, but only as old copies that were barely legible and hardly searchable. "Vienna was home to one of the largest Jewish communities in the former German Reich," explains the Deputy Head of Archives Giora Zwilling (Arolsen Archives). "Thanks to our cooperation with the Documentation Archive, we received photos and metadata for the deportation lists in October and integrated them into our online archive."
See the lists from Austria
Documents produced by the Allies
Lists and other documents from the British and French occupation zones with information on more than five million names* of Nazi victims are now also available in the online archive. These documents were created on the orders of the Allies after the end of the war to document Nazi persecution. This collection has been indexed and made available to the Arolsen Archives by the genealogy portal Ancestry as part of a cooperative project.
See the documents from the occupation zones


text:
<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE TS>
<TS version="2.1" language="ru_RU">
<context>
    <name>D2Form</name>
    <message>
        <source>2D Robot Model</source>
        <translation type="vanished">Двумерная модель</translation>
    </message>
    <message>
        <source>Multiselection mode</source>
        <translation type="vanished">Режим выделения</translation>
    </message>
    <message>
        <source>Camera following robot</source>
        <translation type="vanished">Следовать за роботом</translation>
    </message>
    <message>
        <source>Tools</source>
        <translation type="vanished">Инструменты</translation>
    </message>
    <message>
        <source>Pen</source>
        <translation type="vanished">Перо</translation>
    </message>
    <message>
        <source>Width</source>
        <translation type="vanished">Ширина</translation>
    </message>
    <message>
        <source>Color</source>
        <translation type="vanished">Цвет</translation>
    </message>
    <message>
        <source>Pencil (P)</source>
        <translation type="vanished">Карандаш (P)</translation>
    </message>
    <message>
        <source>P</source>
        <translation type="vanished">P</translation>
    </message>
    <message>
        <source>Line (L)</source>
        <translation type="vanished">Линия (L)</translation>
    </message>
    <message>
        <source>L</source>
        <translation type="vanished">L</translation>
    </message>
    <message>
        <source>Clear</source>
        <translation type="vanished">Очистить все</translation>
    </message>
    <message>
        <source>None (N)</source>
        <translation type="vanished">Курсор (N)</translation>
    </message>
    <message>
        <source>N</source>
        <translation type="vanished">N</translation>
    </message>
    <message>
        <source>Ellipse (E)</source>
        <translation type="vanished">Эллипс (E)</translation>
    </message>
    <message>
        <source>E</source>
        <translation type="vanished">E</translation>
    </message>
    <message>
        <source>Wall (W)</source>
        <translation type="vanished">Стена (W)</translation>
    </message>
    <message>
        <source>W</source>
        <translation type="vanished">W</translation>
    </message>
    <message>
        <source>Clear floor</source>
        <translation type="vanished">Очистить пол от следов робота</translation>
    </message>
    <message>
        <source>Ports</source>
        <translation type="vanished">Порты</translation>
    </message>
    <message>
        <source>Motors</source>
        <translation type="vanished">Моторы</translation>
    </message>
    <message>
        <source>Left wheel:</source>
        <translation type="vanished">Левое колесо:</translation>
    </message>
    <message>
        <source>Right wheel:</source>
        <translation type="vanished">Правое колесо:</translation>
    </message>
    <message>
        <source>Ports configuration</source>
        <translation type="vanished">Порты</translation>
    </message>
    <message>
        <source>Model settings</source>
        <translation type="vanished">Настройки модели</translation>
    </message>
    <message>
        <source>Speed</source>
        <oldsource>Set speed</oldsource>
        <translation type="vanished">Скорость</translation>
    </message>
    <message>
        <source>Low</source>
        <translation type="vanished">Низкая</translation>
    </message>
    <message>
        <source>Medium</source>
        <translation type="vanished">Средняя</translation>
    </message>
    <message>
        <source>High</source>
        <translation type="vanished">Высокая</translation>
    </message>
    <message>
        <source>Physics</source>
        <translation type="vanished">Физика</translation>
    </message>
    <message>
        <source>Realistic physics</source>
        <translation type="vanished">Реалистичная физика</translation>
    </message>
    <message>
        <source>Realistic sensors</source>
        <translation type="vanished">Реалистичные сенсоры</translation>
    </message>
    <message>
        <source>Realistic engines</source>
        <translation type="vanished">Реалистичные моторы</translation>
    </message>
    <message>
        <source>Save World Model (Ctrl+S)</source>
        <translation type="vanished">Сохранить модель мира (Ctrl+S)</translation>
    </message>
    <message>
        <source>Ctrl+S</source>
        <translation type="vanished">Ctrl+S</translation>
    </message>
    <message>
        <source>Load World Model (Ctrl+O)</source>
        <translation type="vanished">Загрузить модель мира (Ctrl+O)</translation>
    </message>
    <message>
        <source>Ctrl+O</source>
        <translation type="vanished">Ctrl+O</translation>
    </message>
    <message>
        <source>Hand dragging mode</source>
        <translation type="vanished">Режим таскания сцены</translation>
    </message>
    <message>
        <source>Stop program (Esc)</source>
        <translation type="vanished">Остановить программу (Esc)</translation>
    </message>
    <message>
        <source>Run program (Enter)</source>
        <translation type="vanished">Запустить программу (Enter)</translation>
    </message>
    <message>
        <source>Return a robot to initial position</source>
        <translation type="vanished">Вернуть робота в исходное положение</translation>
    </message>
    <message>
        <source>Time in 2D model</source>
        <translation type="vanished">Время в 2D модели</translation>
    </message>
    <message>
        <source> sec.</source>
        <translation type="vanished"> сек.</translation>
    </message>
</context>
<context>
    <name>Model</name>
    <message>
        <source>The task is accomplished!</source>
        <translation type="vanished">Задание выполнено!</translation>
    </message>
    <message>
        <source>Error in checker: %1</source>
        <translation type="vanished">Ошибка в проверяющей программе: %1</translation>
    </message>
</context>
<context>
    <name>NxtDisplay</name>
    <message>
        <source>tr(NxtDisplay)</source>
        <translation type="obsolete">Дисплей NXT</translation>
    </message>
</context>
<context>
    <name>QObject</name>
    <message>
        <source>2d model</source>
        <translation type="vanished">2D модель</translation>
    </message>
    <message>
        <location filename="../../../../plugins/robots/common/twoDModel/src/engine/constraints/details/constraintsParser.cpp" line="60"/>
        <source>Root element must be "constraints" tag</source>
        <translation>Корневой элемент должен быть тэгом "constraints"</translation>
    </message>
    <message>
        <location filename="../../../../plugins/robots/common/twoDModel/src/engine/constraints/details/constraintsParser.cpp" line="94"/>
        <source>There must be a "timelimit" constraint.</source>
        <translation>Должен иметься тэг "timelimit".</translation>
    </message>
    <message>
        <location filename="../../../../plugins/robots/common/twoDModel/src/engine/constraints/details/constraintsParser.cpp" line="99"/>
        <source>There must be only one "timelimit" tag.</source>
        <translation>Тэг "timelimit" может быть только один.</translation>
    </message>
    <message>
        <location filename="../../../../plugins/robots/common/twoDModel/src/engine/constraints/details/constraintsParser.cpp" line="148"/>
        <source>Event tag must have "condition" or "conditions" child tag. "%1" found instead.</source>
        <translation>Тег "event" должен иметь дочерний тэг "condition" или "conditions". Вместо этого найдено "%1".</translation>
    </message>
    <message>
        <location filename="../../../../plugins/robots/common/twoDModel/src/engine/constraints/details/constraintsParser.cpp" line="154"/>
        <source>Event tag must have "trigger" or "triggers" child tag. "%1" found instead.</source>
        <translation>Тег "event" должен иметь дочерний тэг "trigger" или "triggers". Вместо этого найдено "%1".</translation>
    </message>
    <message>
        <location filename="../../../../plugins/robots/common/twoDModel/src/engine/constraints/details/constraintsParser.cpp" line="220"/>
        <source>Program worked for too long time</source>
        <translation>Программа работала слишком долго</translation>
    </message>
    <message>
        <location filename="../../../../plugins/robots/common/twoDModel/src/engine/constraints/details/constraintsParser.cpp" line="263"/>
        <source>"Glue" attribute must have value "and" or "or".</source>
        <translation>Аттрибут "glue" должен иметь значение "and" или "or".</translation>
    </message>
    <message>
        <location filename="../../../../plugins/robots/common/twoDModel/src/engine/constraints/details/constraintsParser.cpp" line="318"/>
        <location filename="../../../../plugins/robots/common/twoDModel/src/engine/constraints/details/constraintsParser.cpp" line="492"/>
        <source>Unknown tag "%1".</source>
        <translation>Неизвестный тэг "%1".</translation>
    </message>
    <message>
        <location filename="../../../../plugins/robots/common/twoDModel/src/engine/constraints/details/constraintsParser.cpp" line="413"/>
        <source>There must be only one tag "return" in "using" expression.</source>
        <translation>Тэг "return" может быть только один.</translation>
    </message>
    <message>
        <location filename="../../../../plugins/robots/common/twoDModel/src/engine/constraints/details/constraintsParser.cpp" line="425"/>
        <source>There must be "return" tag in "using" expression.</source>
        <translation>В выражении "using" должен иметься тэг "return".</translation>
    </message>
    <message>
        <location filename="../../../../plugins/robots/common/twoDModel/src/engine/constraints/details/constraintsParser.cpp" line="649"/>
        <source>Unknown value "%1".</source>
        <translation>Неизвестное значение "%1".</translation>
    </message>
    <message>
        <location filename="../../../../plugins/robots/common/twoDModel/src/engine/constraints/details/constraintsParser.cpp" line="730"/>
        <source>Invalid integer value "%1"</source>
        <translation>"%1" - не целое число</translation>
    </message>
    <message>
        <location filename="../../../../plugins/robots/common/twoDModel/src/engine/constraints/details/constraintsParser.cpp" line="744"/>
        <source>Invalid floating point value "%1"</source>
        <translation>"%1" - не число</translation>
    </message>
    <message>
        <location filename="../../../../plugins/robots/common/twoDModel/src/engine/constraints/details/constraintsParser.cpp" line="757"/>
        <source>Invalid boolean value "%1" (expected "true" or "false")</source>
        <translation>"%1" - не логическое значение (ожидалось "true" или "false")</translation>
    </message>
    <message>
        <location filename="../../../../plugins/robots/common/twoDModel/src/engine/constraints/details/constraintsParser.cpp" line="773"/>
        <source>Duplicate id: "%1"</source>
        <translation>Переобъявление события "%1"</translation>
    </message>
    <message>
        <location filename="../../../../plugins/robots/common/twoDModel/src/engine/constraints/details/constraintsParser.cpp" line="784"/>
        <source>%1 tag must have exactly %2 child tag(s)</source>
        <translation>У тэга "%1" должно быть ровно %2 дочерних(ий) тэг(а)</translation>
    </message>
    <message>
        <location filename="../../../../plugins/robots/common/twoDModel/src/engine/constraints/details/constraintsParser.cpp" line="795"/>
        <source>%1 tag must have at least %2 child tag(s)</source>
        <translation>У тэга "%1" должно быть как минимум %2 дочерних(ий) тэг(а)</translation>
    </message>
    <message>
        <location filename="../../../../plugins/robots/common/twoDModel/src/engine/constraints/details/constraintsParser.cpp" line="805"/>
        <source>"%1" tag must have "%2" attribute.</source>
        <translation>У тэга "%1" должен быть аттрибут "%2".</translation>
    </message>
    <message>
        <location filename="../../../../plugins/robots/common/twoDModel/src/engine/constraints/details/constraintsParser.cpp" line="815"/>
        <source>Expected "%1" tag, got "%2".</source>
        <translation>Ожидался тэг "%1", найден - "%2".</translation>
    </message>
    <message>
        <location filename="../../../../plugins/robots/common/twoDModel/src/engine/constraints/details/constraintsParser.cpp" line="829"/>
        <source>Attribute "%1" of the tag "%2" must not be empty.</source>
        <translation>Атрибут "%1" тэга "%2" не может быть пустым.</translation>
    </message>
    <message>
        <location filename="../../../../plugins/robots/common/twoDModel/src/engine/constraints/details/conditionsFactory.cpp" line="107"/>
        <source>No such region: %1</source>
        <translation>Нет такого региона: %1</translation>
    </message>
    <message>
        <location filename="../../../../plugins/robots/common/twoDModel/src/engine/constraints/details/conditionsFactory.cpp" line="115"/>
        <source>%1 is not a region</source>
        <translation>%1 - не регион</translation>
    </message>
    <message>
        <location filename="../../../../plugins/robots/common/twoDModel/src/engine/constraints/details/conditionsFactory.cpp" line="153"/>
        <source>%1 has incorrect type for matching it with region</source>
        <translation>%1 не сопоставить с регионом (не тот тип)</translation>
    </message>
    <message>
        <source>%1 has incorrect type for mathing it with region</source>
        <translation type="vanished">%1 не сопоставить с регионом (не тот тип)</translation>
    </message>
    <message>
        <location filename="../../../../plugins/robots/common/twoDModel/src/engine/constraints/details/conditionsFactory.cpp" line="162"/>
        <location filename="../../../../plugins/robots/common/twoDModel/src/engine/constraints/details/conditionsFactory.cpp" line="174"/>
        <location filename="../../../../plugins/robots/common/twoDModel/src/engine/constraints/details/triggersFactory.cpp" line="80"/>
        <location filename="../../../../plugins/robots/common/twoDModel/src/engine/constraints/details/triggersFactory.cpp" line="92"/>
        <source>No such event: %1</source>
        <translation>Нет такого события: %1</translation>
    </message>
    <message>
        <location filename="../../../../plugins/robots/common/twoDModel/src/engine/constraints/details/conditionsFactory.cpp" line="102"/>
        <location filename="../../../../plugins/robots/common/twoDModel/src/engine/constraints/details/valuesFactory.cpp" line="102"/>
        <source>No such object: %1</source>
        <translation>Нет такого объекта: %1</translation>
    </message>
    <message>
        <source>Object "%1" has no property "%1"</source>
        <translation type="vanished">У объекта "%1" нет свойства "%1"</translation>
    </message>
    <message>
        <location filename="../../../../plugins/robots/common/twoDModel/src/engine/constraints/details/valuesFactory.cpp" line="64"/>
        <source>Requesting variable value with empty name</source>
        <translation>Запрашивается переменная с пустым именем</translation>
    </message>
    <message>
        <location filename="../../../../plugins/robots/common/twoDModel/src/engine/constraints/details/valuesFactory.cpp" line="96"/>
        <source>Object path is empty!</source>
        <translation>Путь до объекта пуст!</translation>
    </message>
    <message>
        <location filename="../../../../plugins/robots/common/twoDModel/src/engine/constraints/details/valuesFactory.cpp" line="216"/>
        <source>Unknown type of object "%1"</source>
        <translation>Неизвестный тип объекта "%1"</translation>
    </message>
    <message>
        <location filename="../../../../plugins/robots/common/twoDModel/src/engine/constraints/details/valuesFactory.cpp" line="221"/>
        <source>Object "%1" has no property "%2"</source>
        <translation>У объекта "%1" нет свойства "%2"</translation>
    </message>
    <message>
        <location filename="../../../../plugins/robots/common/twoDModel/src/engine/view/parts/speedPopup.cpp" line="25"/>
        <source>Speed:&nbsp;&nbsp;%1%</source>
        <translation>Скорость:&nbsp;&nbsp;%1%</translation>
    </message>
    <message>
        <location filename="../../../../plugins/robots/common/twoDModel/src/engine/constraints/details/triggersFactory.cpp" line="62"/>
        <source>Invalid <setState> object type %1</source>
        <translation>Неверный тип объекта %1 в элементе <setState></translation>
    </message>
    <message>
        <location filename="../../../../plugins/robots/common/twoDModel/src/engine/constraints/details/triggersFactory.cpp" line="68"/>
        <source>Object %1 has no property %2</source>
        <translation>Объект %1 не имеет свойства %2</translation>
    </message>
</context>
<context>
    <name>TwoDModelWidget</name>
    <message>
        <location filename="../../../../plugins/robots/common/twoDModel/src/engine/view/twoDModelWidget.ui" line="14"/>
        <source>2D Robot Model</source>
        <translation>Двумерная модель</translation>
    </message>
    <message>
        <location filename="../../../../plugins/robots/common/twoDModel/src/engine/view/twoDModelWidget.ui" line="92"/>
        <source>Run program (Enter)</source>
        <translation>Запустить программу (Enter)</translation>
    </message>
    <message>
        <location filename="../../../../plugins/robots/common/twoDModel/src/engine/view/twoDModelWidget.ui" line="133"/>
        <source>Stop program (Esc)</source>
        <translation>Остановить программу (Esc)</translation>
    </message>
    <message>
        <source>Return robot to the initial position</source>
        <translation type="vanished">Вернуть робота в исходное положение</translation>
    </message>
    <message>
        <location filename="../../../../plugins/robots/common/twoDModel/src/engine/view/twoDModelWidget.ui" line="261"/>
        <source>Decrease speed</source>
        <translation>Уменьшить скорость</translation>
    </message>
    <message>
        <location filename="../../../../plugins/robots/common/twoDModel/src/engine/view/twoDModelWidget.ui" line="302"/>
        <source>Time in 2D model</source>
        <translation>Время в 2D модели</translation>
    </message>
    <message>
        <location filename="../../../../plugins/robots/common/twoDModel/src/engine/view/twoDModelWidget.ui" line="311"/>
        <source> sec.</source>
        <translation> сек.</translation>
    </message>
    <message>
        <location filename="../../../../plugins/robots/common/twoDModel/src/engine/view/twoDModelWidget.ui" line="339"/>
        <source>Increase speed</source>
        <translation>Увеличить скорость</translation>
    </message>
    <message>
        <location filename="../../../../plugins/robots/common/twoDModel/src/engine/view/twoDModelWidget.ui" line="534"/>
        <source>Left wheel:</source>
        <translation>Левое колесо:</translation>
    </message>
    <message>
        <location filename="../../../../plugins/robots/common/twoDModel/src/engine/view/twoDModelWidget.ui" line="544"/>
        <source>Right wheel:</source>
        <translation>Правое колесо:</translation>
    </message>
    <message>
        <location filename="../../../../plugins/robots/common/twoDModel/src/engine/view/twoDModelWidget.ui" line="566"/>
        <source>Realistic physics</source>
        <translation>Реалистичная физика</translation>
    </message>
    <message>
        <location filename="../../../../plugins/robots/common/twoDModel/src/engine/view/twoDModelWidget.ui" line="573"/>
        <source>Realistic sensors</source>
        <translation>Реалистичные сенсоры</translation>
    </message>
    <message>
        <location filename="../../../../plugins/robots/common/twoDModel/src/engine/view/twoDModelWidget.ui" line="580"/>
        <source>Realistic engines</source>
        <translation>Реалистичные моторы</translation>
    </message>
    <message>
        <location filename="../../../../plugins/robots/common/twoDModel/src/engine/view/twoDModelWidget.ui" line="614"/>
        <source>Wheel diameter:</source>
        <translation>Диаметр колеса:</translation>
    </message>
    <message>
        <location filename="../../../../plugins/robots/common/twoDModel/src/engine/view/twoDModelWidget.ui" line="634"/>
        <source>Robot height:</source>
        <translation>Высота робота:</translation>
    </message>
    <message>
        <location filename="../../../../plugins/robots/common/twoDModel/src/engine/view/twoDModelWidget.ui" line="647"/>
        <source>
Robot mass:
</source>
        <translation>Масса робота:</translation>
    </message>
    <message>
        <location filename="../../../../plugins/robots/common/twoDModel/src/engine/view/twoDModelWidget.ui" line="660"/>
        <source>Robot width:</source>
        <translation>Ширина робота:</translation>
    </message>
</context>
<context>
    <name>twoDModel::D2ModelWidget</name>
    <message>
        <source>Black</source>
        <translation type="obsolete">Черный</translation>
    </message>
    <message>
        <source>Blue</source>
        <translation type="obsolete">Синий</translation>
    </message>
    <message>
        <source>Green</source>
        <translation type="obsolete">Зеленый</translation>
    </message>
    <message>
        <source>Yellow</source>
        <translation type="obsolete">Желтый</translation>
    </message>
    <message>
        <source>Red</source>
        <translation type="obsolete">Красный</translation>
    </message>
    <message>
        <source>None</source>
        <translation type="obsolete">Нет сенсора</translation>
    </message>
    <message>
        <source>Port </source>
        <translation type="obsolete">Порт</translation>
    </message>
    <message>
        <source>none</source>
        <translation type="obsolete">Нет сенсора</translation>
    </message>
    <message>
        <source>Saving world and robot model</source>
        <translation type="obsolete">Сохранение модели мира</translation>
    </message>
    <message>
        <source>2D model saves (*.xml)</source>
        <translation type="obsolete">Файлы 2D модели (*.xml)</translation>
    </message>
    <message>
        <source>Loading world and robot model</source>
        <translation type="obsolete">Загрузка модели мира</translation>
    </message>
    <message>
        <source>No wheel</source>
        <translation type="obsolete">Отсутствует</translation>
    </message>
    <message>
        <source>%1 (port %2)</source>
        <translation type="obsolete">%1 (порт %2)</translation>
    </message>
</context>
<context>
    <name>twoDModel::GridParameters</name>
    <message>
        <source>Grid</source>
        <translation type="obsolete">Сетка</translation>
    </message>
</context>
<context>
    <name>twoDModel::constraints::ConstraintsChecker</name>
    <message>
        <location filename="../../../../plugins/robots/common/twoDModel/src/engine/constraints/constraintsChecker.cpp" line="112"/>
        <source>Error while parsing constraints: %1</source>
        <translation>Ошибка чтения ограничений: %1</translation>
    </message>
    <message>
        <location filename="../../../../plugins/robots/common/twoDModel/src/engine/constraints/constraintsChecker.cpp" line="294"/>
        <source>Program has finished, but the task is not accomplished.</source>
        <translation>Программа отработала, но задание не выполнено.</translation>
    </message>
</context>
<context>
    <name>twoDModel::items::CurveItem</name>
    <message>
        <location filename="../../../../plugins/robots/common/twoDModel/src/engine/items/curveItem.cpp" line="64"/>
        <source>Bezier Curve (B)</source>
        <translation>Кривая Безье (B)</translation>
    </message>
</context>
<context>
    <name>twoDModel::items::EllipseItem</name>
    <message>
        <location filename="../../../../plugins/robots/common/twoDModel/src/engine/items/ellipseItem.cpp" line="43"/>
        <source>Ellipse (E)</source>
        <translation>Эллипс (E)</translation>
    </message>
</context>
<context>
    <name>twoDModel::items::ImageItem</name>
    <message>
        <location filename="../../../../plugins/robots/common/twoDModel/src/engine/items/imageItem.cpp" line="48"/>
        <source>Image (I)</source>
        <translation>Картинка (I)</translation>
    </message>
</context>
<context>
    <name>twoDModel::items::LineItem</name>
    <message>
        <location filename="../../../../plugins/robots/common/twoDModel/src/engine/items/lineItem.cpp" line="47"/>
        <source>Line (L)</source>
        <translation>Линия (L)</translation>
    </message>
</context>
<context>
    <name>twoDModel::items::RectangleItem</name>
    <message>
        <location filename="../../../../plugins/robots/common/twoDModel/src/engine/items/rectangleItem.cpp" line="43"/>
        <source>Rectangle (R)</source>
        <translation>Прямоугольник (R)</translation>
    </message>
</context>
<context>
    <name>twoDModel::items::StylusItem</name>
    <message>
        <location filename="../../../../plugins/robots/common/twoDModel/src/engine/items/stylusItem.cpp" line="55"/>
        <source>Stylus (S)</source>
        <translation>Стилус (S)</translation>
    </message>
</context>
<context>
    <name>twoDModel::items::WallItem</name>
    <message>
        <location filename="../../../../plugins/robots/common/twoDModel/src/engine/items/wallItem.cpp" line="67"/>
        <source>Wall (W)</source>
        <translation>Стена (W)</translation>
    </message>
</context>
<context>
    <name>twoDModel::model::Model</name>
    <message>
        <location filename="../../../../plugins/robots/common/twoDModel/src/engine/model/model.cpp" line="44"/>
        <source>The task is accomplished!</source>
        <translation>Задание выполнено!</translation>
    </message>
    <message>
        <location filename="../../../../plugins/robots/common/twoDModel/src/engine/model/model.cpp" line="57"/>
        <source>Error in checker: %1</source>
        <translation>Ошибка в проверяющей программе: %1</translation>
    </message>
</context>
<context>
    <name>twoDModel::model::WorldModel</name>
    <message>
        <location filename="../../../../plugins/robots/common/twoDModel/src/engine/model/worldModel.cpp" line="135"/>
        <location filename="../../../../plugins/robots/common/twoDModel/src/engine/model/worldModel.cpp" line="173"/>
        <location filename="../../../../plugins/robots/common/twoDModel/src/engine/model/worldModel.cpp" line="191"/>
        <source>Trying to add an item with a duplicate id: %1</source>
        <translation>Попытка добавить элемент с существующим идентификатором: %1</translation>
    </message>
</context>
<context>
    <name>twoDModel::robotModel::TwoDRobotModel</name>
    <message>
        <location filename="../../../../plugins/robots/common/twoDModel/src/robotModel/twoDRobotModel.cpp" line="73"/>
        <location filename="../../../../plugins/robots/common/twoDModel/src/robotModel/twoDRobotModel.cpp" line="76"/>
        <source>2D Model</source>
        <translation>2D модель</translation>
    </message>
</context>
<context>
    <name>twoDModel::robotModel::parts::ColorSensorBlue</name>
    <message>
        <location filename="../../../../plugins/robots/common/twoDModel/include/twoDModel/robotModel/parts/colorSensorBlue.h" line="36"/>
        <source>Color sensor (blue)</source>
        <translation>Сенсор цвета (синий)</translation>
    </message>
</context>
<context>
    <name>twoDModel::robotModel::parts::ColorSensorFull</name>
    <message>
        <location filename="../../../../plugins/robots/common/twoDModel/include/twoDModel/robotModel/parts/colorSensorFull.h" line="37"/>
        <source>Color sensor (full)</source>
        <translation>Сенсор цвета (распознавание цветов)</translation>
    </message>
</context>
<context>
    <name>twoDModel::robotModel::parts::ColorSensorGreen</name>
    <message>
        <location filename="../../../../plugins/robots/common/twoDModel/include/twoDModel/robotModel/parts/colorSensorGreen.h" line="36"/>
        <source>Color sensor (green)</source>
        <translation>Сенсор цвета (зеленый)</translation>
    </message>
</context>
<context>
    <name>twoDModel::robotModel::parts::ColorSensorPassive</name>
    <message>
        <location filename="../../../../plugins/robots/common/twoDModel/include/twoDModel/robotModel/parts/colorSensorPassive.h" line="37"/>
        <source>Color sensor (passive)</source>
        <translation>Сенсор цвета (пассивный)</translation>
    </message>
</context>
<context>
    <name>twoDModel::robotModel::parts::ColorSensorRed</name>
    <message>
        <location filename="../../../../plugins/robots/common/twoDModel/include/twoDModel/robotModel/parts/colorSensorRed.h" line="36"/>
        <source>Color sensor (red)</source>
        <translation>Сенсор цвета (красный)</translation>
    </message>
</context>
<context>
    <name>twoDModel::robotModel::parts::Marker</name>
    <message>
        <location filename="../../../../plugins/robots/common/twoDModel/include/twoDModel/robotModel/parts/marker.h" line="37"/>
        <source>Marker</source>
        <translation>Маркер</translation>
    </message>
</context>
<context>
    <name>twoDModel::view::ActionsBox</name>
    <message>
        <location filename="../../../../plugins/robots/common/twoDModel/src/engine/view/parts/actionsBox.cpp" line="22"/>
        <source>Hand dragging mode</source>
        <translation>Режим таскания сцены</translation>
    </message>
    <message>
        <location filename="../../../../plugins/robots/common/twoDModel/src/engine/view/parts/actionsBox.cpp" line="23"/>
        <source>Multiselection mode</source>
        <translation>Режим выделения</translation>
    </message>
    <message>
        <location filename="../../../../plugins/robots/common/twoDModel/src/engine/view/parts/actionsBox.cpp" line="25"/>
        <source>Save world model...</source>
        <translation>Сохранить модель мира...</translation>
    </message>
    <message>
        <location filename="../../../../plugins/robots/common/twoDModel/src/engine/view/parts/actionsBox.cpp" line="26"/>
        <source>Load world model...</source>
        <translation>Загрузить модель мира...</translation>
    </message>
    <message>
        <location filename="../../../../plugins/robots/common/twoDModel/src/engine/view/parts/actionsBox.cpp" line="28"/>
        <source>Set background...</source>
        <translation>Установить фон...</translation>
    </message>
    <message>
        <location filename="../../../../plugins/robots/common/twoDModel/src/engine/view/parts/actionsBox.cpp" line="30"/>
        <source>Clear items</source>
        <translation>Очистить всё</translation>
    </message>
    <message>
        <location filename="../../../../plugins/robots/common/twoDModel/src/engine/view/parts/actionsBox.cpp" line="31"/>
        <source>Clear floor</source>
        <translation>Очистить пол от следов робота</translation>
    </message>
</context>
<context>
    <name>twoDModel::view::ColorItemPopup</name>
    <message>
        <location filename="../../../../plugins/robots/common/twoDModel/src/engine/view/parts/colorItemPopup.cpp" line="95"/>
        <source>Color</source>
        <translation>Цвет</translation>
    </message>
    <message>
        <location filename="../../../../plugins/robots/common/twoDModel/src/engine/view/parts/colorItemPopup.cpp" line="120"/>
        <source>Disable filling</source>
        <translation>Не заливать</translation>
    </message>
    <message>
        <location filename="../../../../plugins/robots/common/twoDModel/src/engine/view/parts/colorItemPopup.cpp" line="120"/>
        <source>Enable filling</source>
        <translation>Заливать</translation>
    </message>
    <message>
        <location filename="../../../../plugins/robots/common/twoDModel/src/engine/view/parts/colorItemPopup.cpp" line="135"/>
        <source>Thickness</source>
        <translation>Толщина</translation>
    </message>
</context>
<context>
    <name>twoDModel::view::D2ModelWidget</name>
    <message>
        <source>Black</source>
        <translation type="vanished">Черный</translation>
    </message>
    <message>
        <source>Blue</source>
        <translation type="vanished">Синий</translation>
    </message>
    <message>
        <source>Green</source>
        <translation type="vanished">Зеленый</translation>
    </message>
    <message>
        <source>Yellow</source>
        <translation type="vanished">Желтый</translation>
    </message>
    <message>
        <source>Red</source>
        <translation type="vanished">Красный</translation>
    </message>
    <message>
        <source>Warning</source>
        <translation type="vanished">Предупреждение</translation>
    </message>
    <message>
        <source>Do you really want to clear scene?</source>
        <translation type="vanished">Вы действительно хотите очистить сцену?</translation>
    </message>
    <message>
        <source>Yes</source>
        <translation type="vanished">Да</translation>
    </message>
    <message>
        <source>Cancel</source>
        <translation type="vanished">Отмена</translation>
    </message>
    <message>
        <source>Saving world and robot model</source>
        <translation type="vanished">Сохранение модели мира</translation>
    </message>
    <message>
        <source>2D model saves (*.xml)</source>
        <translation type="vanished">Файлы 2D модели (*.xml)</translation>
    </message>
    <message>
        <source>Loading world and robot model</source>
        <translation type="vanished">Загрузка модели мира</translation>
    </message>
    <message>
        <source>No wheel</source>
        <translation type="vanished">Отсутствует</translation>
    </message>
    <message>
        <source>%1 (port %2)</source>
        <translation type="vanished">%1 (порт %2)</translation>
    </message>
</context>
<context>
    <name>twoDModel::view::DetailsTab</name>
    <message>
        <location filename="../../../../plugins/robots/common/twoDModel/src/engine/view/parts/detailsTab.cpp" line="42"/>
        <source>Display</source>
        <translation>Дисплей</translation>
    </message>
    <message>
        <location filename="../../../../plugins/robots/common/twoDModel/src/engine/view/parts/detailsTab.cpp" line="43"/>
        <source>Ports configuration</source>
        <translation>Порты</translation>
    </message>
    <message>
        <location filename="../../../../plugins/robots/common/twoDModel/src/engine/view/parts/detailsTab.cpp" line="44"/>
        <source>Motors</source>
        <translation>Моторы</translation>
    </message>
    <message>
        <location filename="../../../../plugins/robots/common/twoDModel/src/engine/view/parts/detailsTab.cpp" line="45"/>
        <source>Physics</source>
        <translation>Физика</translation>
    </message>
    <message>
        <location filename="../../../../plugins/robots/common/twoDModel/src/engine/view/parts/detailsTab.cpp" line="46"/>
        <source>Model parameters</source>
        <translation>Параметры модели</translation>
    </message>
</context>
<context>
    <name>twoDModel::view::GridParameters</name>
    <message>
        <location filename="../../../../plugins/robots/common/twoDModel/src/engine/view/parts/gridParameters.cpp" line="30"/>
        <source>Grid</source>
        <translation>Сетка</translation>
    </message>
</context>
<context>
    <name>twoDModel::view::ImageItemPopup</name>
    <message>
        <location filename="../../../../plugins/robots/common/twoDModel/src/engine/view/parts/imageItemPopup.cpp" line="52"/>
        <source>Image will be packed into save file. Warning: this will increase save file size.</source>
        <translation>Картинка будет запакована в проект. Внимание: это значительно увеличит размер файла сохранения.</translation>
    </message>
    <message>
        <location filename="../../../../plugins/robots/common/twoDModel/src/engine/view/parts/imageItemPopup.cpp" line="53"/>
        <source>Image will not be packed into a save file. Warning: if will use save file on other machine or rename file this image will disappear from 2D model.</source>
        <translation>Картинка не будет включена в файл сохранения. Внимание: при открытии текущего проекта на другой машине или переименовании файла с картинкой изображение в 2D модели пропадет.</translation>
    </message>
    <message>
        <location filename="../../../../plugins/robots/common/twoDModel/src/engine/view/parts/imageItemPopup.cpp" line="118"/>
        <source>Change image...</source>
        <translation>Изменить картинку...</translation>
    </message>
    <message>
        <location filename="../../../../plugins/robots/common/twoDModel/src/engine/view/parts/imageItemPopup.cpp" line="122"/>
        <source>Select image</source>
        <translation>Выберите картинку</translation>
    </message>
    <message>
        <location filename="../../../../plugins/robots/common/twoDModel/src/engine/view/parts/imageItemPopup.cpp" line="122"/>
        <source>Graphics (*.*)</source>
        <translation>Графика (*.*)</translation>
    </message>
</context>
<context>
    <name>twoDModel::view::Palette</name>
    <message>
        <location filename="../../../../plugins/robots/common/twoDModel/src/engine/view/parts/palette.cpp" line="25"/>
        <source>Cursor (N)</source>
        <translation>Курсор (N)</translation>
    </message>
</context>
<context>
    <name>twoDModel::view::RobotItemPopup</name>
    <message>
        <location filename="../../../../plugins/robots/common/twoDModel/src/engine/view/parts/robotItemPopup.cpp" line="74"/>
        <source>Camera folowing robot: %1</source>
        <translation>Следовать за роботом: %1</translation>
    </message>
    <message>
        <location filename="../../../../plugins/robots/common/twoDModel/src/engine/view/parts/robotItemPopup.cpp" line="75"/>
        <source>enabled</source>
        <translation>включено</translation>
    </message>
    <message>
        <location filename="../../../../plugins/robots/common/twoDModel/src/engine/view/parts/robotItemPopup.cpp" line="75"/>
        <source>disabled</source>
        <translation>отключено</translation>
    </message>
    <message>
        <location filename="../../../../plugins/robots/common/twoDModel/src/engine/view/parts/robotItemPopup.cpp" line="82"/>
        <source>Return robot to the initial position</source>
        <translation>Вернуть робота в исходное положение</translation>
    </message>
    <message>
        <location filename="../../../../plugins/robots/common/twoDModel/src/engine/view/parts/robotItemPopup.cpp" line="100"/>
        <source>Marker thickness</source>
        <translation>Толщина маркера</translation>
    </message>
</context>
<context>
    <name>twoDModel::view::SpeedPopup</name>
    <message>
        <location filename="../../../../plugins/robots/common/twoDModel/src/engine/view/parts/speedPopup.cpp" line="30"/>
        <source>Reset to default</source>
        <translation>По умолчанию</translation>
    </message>
</context>
<context>
    <name>twoDModel::view::TwoDModelScene</name>
    <message>
        <location filename="../../../../plugins/robots/common/twoDModel/src/engine/view/scene/twoDModelScene.cpp" line="557"/>
        <source>Select image</source>
        <translation>Выберите картинку</translation>
    </message>
    <message>
        <location filename="../../../../plugins/robots/common/twoDModel/src/engine/view/scene/twoDModelScene.cpp" line="557"/>
        <source>Graphics (*.*)</source>
        <translation>Графика (*.*)</translation>
    </message>
</context>
<context>
    <name>twoDModel::view::TwoDModelWidget</name>
    <message>
        <location filename="../../../../plugins/robots/common/twoDModel/src/engine/view/twoDModelWidget.cpp" line="256"/>
        <source>Warning</source>
        <translation>Предупреждение</translation>
    </message>
    <message>
        <location filename="../../../../plugins/robots/common/twoDModel/src/engine/view/twoDModelWidget.cpp" line="257"/>
        <source>Do you really want to clear scene?</source>
        <translation>Вы действительно хотите очистить сцену?</translation>
    </message>
    <message>
        <location filename="../../../../plugins/robots/common/twoDModel/src/engine/view/twoDModelWidget.cpp" line="259"/>
        <source>Yes</source>
        <translation>Да</translation>
    </message>
    <message>
        <location filename="../../../../plugins/robots/common/twoDModel/src/engine/view/twoDModelWidget.cpp" line="260"/>
        <source>Cancel</source>
        <translation>Отмена</translation>
    </message>
    <message>
        <location filename="../../../../plugins/robots/common/twoDModel/src/engine/view/twoDModelWidget.cpp" line="343"/>
        <source>Training mode: solution will not be checked</source>
        <translation>Режим тренировки: решение не будет проверяться</translation>
    </message>
    <message>
        <location filename="../../../../plugins/robots/common/twoDModel/src/engine/view/twoDModelWidget.cpp" line="344"/>
        <source>Checking mode: solution will be checked, errors will be reported</source>
        <translation>Режим проверки: проверка решения будет осуществляться, об ошибках будет сообщаться</translation>
    </message>
    <message>
        <location filename="../../../../plugins/robots/common/twoDModel/src/engine/view/twoDModelWidget.cpp" line="409"/>
        <source>Saving world and robot model</source>
        <translation>Сохранение модели мира</translation>
    </message>
    <message>
        <location filename="../../../../plugins/robots/common/twoDModel/src/engine/view/twoDModelWidget.cpp" line="409"/>
        <location filename="../../../../plugins/robots/common/twoDModel/src/engine/view/twoDModelWidget.cpp" line="429"/>
        <source>2D model saves (*.xml)</source>
        <translation>Файлы 2D модели (*.xml)</translation>
    </message>
    <message>
        <location filename="../../../../plugins/robots/common/twoDModel/src/engine/view/twoDModelWidget.cpp" line="429"/>
        <source>Loading world and robot model</source>
        <translation>Загрузка модели мира</translation>
    </message>
    <message>
        <location filename="../../../../plugins/robots/common/twoDModel/src/engine/view/twoDModelWidget.cpp" line="450"/>
        <source>Select background image</source>
        <translation>Выберите фоновое изображение</translation>
    </message>
    <message>
        <location filename="../../../../plugins/robots/common/twoDModel/src/engine/view/twoDModelWidget.cpp" line="450"/>
        <source>Graphics (*.*)</source>
        <translation>Графика (*.*)</translation>
    </message>
    <message>
        <location filename="../../../../plugins/robots/common/twoDModel/src/engine/view/twoDModelWidget.cpp" line="742"/>
        <source>Hide details</source>
        <translation>Скрыть детали</translation>
    </message>
    <message>
        <location filename="../../../../plugins/robots/common/twoDModel/src/engine/view/twoDModelWidget.cpp" line="742"/>
        <source>Show details</source>
        <translation>Показать детали</translation>
    </message>
    <message>
        <location filename="../../../../plugins/robots/common/twoDModel/src/engine/view/twoDModelWidget.cpp" line="881"/>
        <location filename="../../../../plugins/robots/common/twoDModel/src/engine/view/twoDModelWidget.cpp" line="882"/>
        <source>No wheel</source>
        <translation>Отсутствует</translation>
    </message>
    <message>
        <location filename="../../../../plugins/robots/common/twoDModel/src/engine/view/twoDModelWidget.cpp" line="887"/>
        <source>%1 (port %2)</source>
        <translation>%1 (порт %2)</translation>
    </message>
</context>
</TS>


Loving your attitude and perspective today! Have a wonderful day and weekend!
Oh! I was pondering the wonder of snow rather than cancer today!! It can make everything better can't it?
Enjoy just 'being' with the day! Adorable pups & I just adore snow as well!


THE MAYBELLINE STORY : Making Tom Lyle Proud...I hope!
Making Tom Lyle Proud...I hope!
Sharrie Williams with her great uncle Tom Lyle Williams and her sister Donna Williams, 1972.
Well, he sold the company two years later, and I never had the chance work for him, but in our conversation I told him I wanted to write a book about him and the Maybelline Company someday. He thought for a few seconds, than said "I really don't wan't anything written about me." I looked disappointed, not understanding why he wanted to be forgotten.
I hope he would be proud of the way I have portrayed him for posterity as the undisputed king of advertising, and a true pioneer in the cosmetics business.


This is one for all those denizens of good taste out there. All those of you who would really, really like to take some classic weapons and bling them out until they sparkle. Go on - you know you want to!
Golden AK47: Take a classic AK. Gold plate every visible piece of metal. Engrave the wood for good measure. Serious blingski. No tasteski. Dead cool, though.
Golden Katana: Stunning craftsmanship, taking decades to perfect. And then someone just has to go and gold plate it... Pretty, ain't it?
Golden M79: Gold plating. Gold filigree inlay on the woodwork. You probably want the rounds gold as well. Bosh! Consider it done!
Combat Shotgun: Drench the metal in gold, polish until it shines and twinkles. Just the thing for the serious Zed-slayer.


As usual, when the end of the financial year is approaching it's a good idea to make sure everything's in order.
Review planned dividend payments and the company's imputation credit account balance. We will be reviewing these in March. Be aware that some DWT may be payable in April for this!
Call us if you'd like a quick heads-up on what to look for in the details or options for how to treat any of the above.


Editor's note: Barbara Lee is the representative for California's 13th District and a founding co-chair of the Congressional HIV/AIDS Caucus. Kenneth Cole is CEO of Kenneth Cole Productions and chairman of the board of amfAR, the Foundation for AIDS Research. The views expressed are their own.
(CNN) -- Last year on World AIDS Day, President Barack Obama said that we can achieve an AIDS-free generation "if we stay focused, and if we keep fighting," and challenged the world to "come together to set new goals" in the war against AIDS. Three decades into the epidemic, important headway has been made thanks to ambitious efforts by the U.S. government to end AIDS here and abroad.
The National HIV/AIDS Strategy, released in 2010, is the nation's first comprehensive road map with clear and measurable targets to be achieved by 2015: reduce new HIV infections, increase access to care and improve health outcomes for people living with HIV and reduce HIV-related disparities. Over the past four years, it has prioritized funding where it will have the most impact.
This World AIDS Day on December 1, marked today, we can point to successes in combating HIV in the United States.
The overall number of Americans who know their HIV status increased to 84% approaching the Strategy goal of 90% by 2015. From 2008 to 2012, HIV diagnoses declined among blacks, Latinos and women nationally. The latest surveillance data show that new HIV infections have been declining among black women and injecting drug users. Importantly, AIDS diagnoses (or diagnosing people late in their disease progression) decreased among all racial and transmission groups during this time.
The Affordable Care Act has enabled millions of uninsured Americans to have access to health care and get free HIV testing.
The White House's HIV Care Continuum Initiative has boosted federal efforts to prevent and treat HIV. Meanwhile, a series of recent breakthroughs in HIV cure research have also brought us more clarity than we have ever had on the precise steps and tools needed to finally eradicate this disease.
The federal government has prioritized cure research and amfAR, The Foundation for AIDS Research, recently upped the ante on cure research as well, setting a goal to invest $100 million in developing the scientific basis for a cure by 2020.
Unfortunately, we still have work to do. About 50,000 Americans continue to become infected with HIV each year, with nearly 80% of infections among men and two-thirds of new infections nationally among gay and bisexual men.
We continue to see high rates of new infections in the South, especially amongst African-Americans. Astoundingly, one third of all black gay men nationally are HIV-positive -- and they remain the population with the greatest number of infections in the black community and the only population in the black community in which new infections are increasing. Though HIV diagnoses decreased among injecting drug users from 2008 to 2012, AIDS-related deaths remain the highest in this population.
And beyond our borders, we have also reached a turning point. According to the UNAIDS report that was released last week and the GAP report released in July 2014, we have five years to break the epidemic for good or risk it rebounding out of control. We have made many gains, but there is still much more work to do.
The annual number of new HIV infections has dropped by 33% since 2001. And more people than ever are receiving lifesaving antiretroviral treatment, leading to historic declines in AIDS-related deaths worldwide. This progress is encouraging, but we have a chance to rid the world of the epidemic now. The United States must be a leader in this effort.
The United States leads the world in its commitment to combating AIDS globally. American investments through the Global Fund to Fight AIDS, Tuberculosis and Malaria (Global Fund) as well as the President's Emergency Plan for AIDS Relief (PEPFAR) have been transformative in the global response to AIDS. PEPFAR is helping provide lifesaving HIV treatment to 6.7 million people, and has prevented countless infections among infants born to HIV-positive moters in some of the hardest hit regions.
An estimated 35 million people worldwide are living with HIV, 19 million of them do not know they are infected, and more than 2 million become infected each year. HIV medications remain out of reach for far too many globally -- more than 20 million are unable to access treatment -- and budget cuts threaten the advances that we have made and the possibility of ending the AIDS epidemic by 2030. We have an obligation to sustain and increase our contributions to the global HIV effort, especially since the U.S. contribution to foreign aid (including HIV prevention and other efforts) is less than 1 of our total budget.
Congress must do its part by providing level funding for PEPFAR and the Global Fund in fiscal year 2015, and increasing our contribution in subsequent years. Level funding for PEPFAR alone will allow an additional 272,000 people on treatment, keep an additional 17,000 infants from being born with HIV and avert an additional 62,000 AIDS-related deaths. Although we now have the tools and the knowledge needed to end the AIDS crisis, the looming question is will we?
We believe that we can and we will. We must reject budget cuts that threaten to paralyze proven lifesaving HIV interventions. Evidence continues to show that the scale-up of treatment for people living with HIV not only saves lives, but also greatly reduces the chances of an HIV-positive person transmitting the virus to others. UNAIDS recently declared that, "If the world does not rapidly scale-up [treatment] in the next five years, the epidemic will spring back with a higher rate of new HIV infections than today."
Momentum is on our side. Now is not the time to slow down our efforts, or be complacent in our attitudes toward a disease that has already claimed 40 million lives and continues to ravage families and economies around the globe.
Our country has led on this issue domestically and globally. We must overcome our differences, combine our strengths and our resources and unite in our quest to finally end AIDS and ensure the health and prosperity of future generations.


Here I come with another edition of the Weekly Round-up, hoping that you have read the previous round-up, else you missed some quality posts. This week there were some amazing tech news coming our way along with a great achievement achieved by a Legend. Though, I didn't write many posts but managed to write an article per day.
Hope you liked the posts posted this week, have any suggestion or any topic you particularly want me to blog in ? Write in your suggestions as comments!
Next PostBillion Hearts Beating : Bloggers take your Pledge Today!
Nice roundup. All those posts were nice read too.
Great roundup. Very informative posts.


At Baycon there were two things that were always in the air, wherever you went. One was music — well, they called it music; anyway, the old hotel was rattling with the sound of acid rock, all night long — and the other was a gift from the Berkeley campus, just down the hill. Those were the days of campus riots, and what we got from them was the faint and inescapable aroma of tear gas.
What I remember best is the banquet, partly because I got my third editorial Hugo there, even more because of Phil Farmer's Guest of Honor speech. He devoted a large part of it to denouncing John W. Campbell, Jr., who happened to be sitting at our table; so I had the chance of watching John's face all through the long address. John was a real gentleman about it all. He listened with full attention, and if he was boiling inside his expression was always polite. But then John Campbell was a class act from the beginning — most of the time.


text:
Q: Why is atomize not working with Gatsby JS (react)? I'm trying to use Atomize (https://atomizecode.com/) with Gatsby JS (https://www.gatsbyjs.org/) and while it is successfully installed, the atomize components are not being rendered to the page.
I am trying to import a button to start "Hey", and while it renders something it is not the standard button component. Also, even though the button component is imported, I get the warning that reads it is not being used.
I am wrapping atomize around gatsby app by the following way:
import React from "react"
import { StyleReset } from "atomize"

export const wrapRootElement = ({ element }) => (
  <>
    <StyleReset />
    {element}
  </>
)

A: Did you install styletron toolkit?
According to their docs it's a dependency and looking at their package.json it's defined under peerDependencies which means it won't get installed along with atomize.
Styletron's docs sugggets using gatsby-plugin-styletron for Gatsby.
Hope that helps.

redpajama_set_name: RedPajamaStackExchange


text:
Q: Converting DoubleBinding into double in javaFX DoubleBinding angle = new SimpleDoubleProperty(myIndex*Math.PI*2).divide(nrMoons);
moon.centerXProperty().bind(earth.centerXProperty().add(Math.cos(angle.doubleValue()).multiply(RADIUS_ORBIT)));

that is the part of my code, where I get an error that double angle.doubleValue() cannot be dereferenced, and Math.cos() requires a double not a DoubleBinding, any idea on how to convert it?

A: Assuming the quantity you want to add is the product of the cosine of the angle, and RADIUS_ORBIT, you just need to use the operator * instead of the function multiply:
moon.centerXProperty().bind(earth.centerXProperty().add(Math.cos(angle.doubleValue()) * RADIUS_ORBIT));

Note that this probably won't work the way you want: the value you pass to add(...) is not observable (it's just a plain double), so the value will only update if earth.centerXProperty() changes, but won't update if angle changes. This is not so much because of using * instead of multiply(), but because Math.cos() returns a plain double instead of some kind of ObservableDoubleValue. There's no direct API in JavaFX properties/bindings for "taking the cosine of a value".
If you want this to depend dynamically on angle, you should use a custom binding (which also has the advantage of making the computation easier to see in the code).
I think this is the value you want to compute:
moon.centerXProperty.bind(Bindings.createDoubleBinding(() -> {
    double earthCenter = earth.getCenterX();
    double offset = Math.cos(angle.get()) * RADIUS_ORBIT ;
    return earthCenter + offset ;
}, earth.centerXProperty(), angle);


text:
{{SEITENTITEL:Eu(dpm)3}}

Eu(dpm)3 ist eine chemische Verbindung mit der Halbstrukturformel Eu[OCC(CH3)3CHCOC(CH3)3]3. Diese Koordinationsverbindung wird hauptsächlich in der NMR-Spektroskopie eingesetzt, um Signale zu verschieben (shiften). Eu(dpm)3 ist eins der ersten Lanthanoid-Shift-Reagenzien und wurde erstmals von Hinckley 1969 bei der Untersuchung von Cholesterin verwendet.

Struktur und Reaktivität

Eu(dpm)3 besteht aus drei zweizähnigen dpm-Liganden, die an ein Eu-Zentrum binden. Das Dipivaloylmethanoat (dpm) ist strukturell verwandt mit dem Acetylacetonat (acac), dabei sind die zwei Methyl-Gruppen durch tert-Butyl-Gruppen substituiert. Das Metall besitzt eine Elektronenkonfiguration f6. Die sechs Elektronen sind ungepaart – jedes befindet sich in einem anderen einfach-besetzten f-Orbital – woraus ein ausgeprägter Paramagnetismus des Komplexes folgt. Der Komplex ist eine Lewis-Säure und kann seine Koordinationszahl von 6 auf 8 erhöhen. Die Verbindung besitzt eine hohe Affinität gegenüber harten Lewis-Basen, wie Sauerstoffatomen in Ethern und Stickstoffatomen in Aminen.

Verwendung
Eu(dpm)3 wird hauptsächlich in der NMR-Spektroskopie verwendet und hat dort ein breites Anwendungsgebiet als Lanthanoid-Shift-Reagenzien. Es kann unter anderm zur Molmassenbestimmung von Polypropylenglycol, sowie in der Strukturaufklärung verwendet werden. Außerdem wird es in vielen Untersuchungen zur Wirkungsweise von Shift-Reagenzien verwendet.

Einzelnachweise

Analytische Chemie
Europiumverbindung
Chelatkomplex

redpajama_set_name: RedPajamaWikipedia


The Blended Instructional Design (BID) is a course to personalize learning for ALL students. The course is organized to provide efficient professional development in three domains: 1) Identify, 2) Design, and 3) Implement. Teachers are provided with short 2-3 minutes instructional videos providing descriptions, and models to identify critical content, vocabulary, concepts, virtual and physical materials, assessments, as well as, identify specific student learning needs to personalize instruction and practice/application activities and projects. Once the information is gathered in the identify phase, teachers immediately apply the information to design their virtual, digital and physical instruction and activities/projects. Finally, the BID course provides descriptive models of how to transition to a blended learning classroom environment. Here teachers are informed on self-coaching, developing and maintaining partnerships with parents and support personnel. A variety of resources for locating pre-made instructional videos and tools for creating instructional videos, digital tools that support content practice, and supporting documents to use with the online course are provided to enhance the individual learning needs of teachers.


At Enginuity Advantage, we are dedicated to helping talented engineers like you find excellent industrial engineering jobs at top employers locally, nationally and globally. These employers need the kind of skills, training and expertise you can offer, and it is our goal to make the process of connecting with them as easy as possible.
Unlike general recruiters, the only thing we do is work with engineers and their employers. Because of this, Enginuity has been able to leverage our industry experience and our relationships to build a wide referral-based contact network that we can deploy to help you find the kind of top industrial engineering jobs you'd never see on an internet job board.
With over 25 years of experience matching engineers with employers, we have refined and optimized our methods to make the process of finding your dream job as easy as possible. We will get to know your values and expectations and then match you to an employer who meets and exceeds your criteria.
At Enginuity, we take the headache out of the industrial engineering job search. You won't have to worry about checking the job boards every day, and you can rest assured we'll only match you with employers who would be a great fit for your skills, experience and expectations. And we'll be with you at every step in the process, from your first contact with us until after you've been placed in your perfect job.
At Enginuity, we firmly believe in the Ripple Effect, meaning we take a pay-it-forward approach to our interactions with our candidates and business clients. We know that your choice of employer is an important decision with lasting effects for you and your loved ones, and we want to help you find the best options. You can count on Enginuity to treat you like more than just a business transaction.
Enginuity Advantage has helped thousands of engineers find their ideal positions with leading employers, and that success has helped us build our extensive and unmatched referral-based network of contacts across many industries and geographic locations. Let us put the power of that network to work for you to help you find your perfect industrial engineering jobs.
At Enginuity, we aren't in the business of putting you in the first industrial engineering job that comes along. We care about finding you the right position with good compensation, opportunities for advancement, shared values and the opportunity to work with a team that shares your passion. For us, it's about building lasting relationships with satisfied clients, and helping people find positions doing the work they love.


text:
Banff News
Canmore News
Lake Louise News
MD of Bighorn News
Kananaskis Country News
Stoney Nakoda News
Mountain Guide
Mountain Homes
Bites & Bevies
Rocky Mountain Outlook E-Edition
51° North Magazine
Immigration In The Bow Valley
2022 Best of the Bow
Garage and Yard Sales
Municipal Notices
Provincial Notices
Province looking to improve rest stops along Alberta highways
Proposed rest stops may include not only space for motorists to stretch their legs, but also fill up on gas, eat and recuperate safely during trips.
Rahma Dalmar Aug 17, 2022 8:10 AM
Expanding rest areas for motorists travelling along provincial highways in Alberta is a part of a new initiative put forward by the province.Metro Creative image
LAKELAND - Expanding rest areas for motorists travelling along provincial highways in Alberta is a part of a new initiative put forward by the province.
The proposed rest stops may include not only space for commercial and recreational motorists to stretch their legs, but also fill up on gas, eat, and recuperate safely during trips. The rest areas will be added to select areas across Alberta, said Alberta's Minister of Transportation, Prasad Panda in a statement released on Aug. 9.
"Alberta's highways connect businesses and travellers with trade and leisure opportunities. Developing new rest areas will enhance convenience and safety for the businesses and tourists who travel Alberta's highways," said Panda.
A plan to create new rest areas has been in the works since this winter, with construction set for the summer of 2024. Currently, commercial bids are open for future rest areas until December when contracts are expected to be awarded in late 2023, according to the statement.
For commercial users in the Lakeland, the proposed future additions are welcome for drivers that make regular trips throughout Alberta, said Gerald Wowk, President of Lac La Biche Transport. Operating and moving large materials relative to the oil field industry through the Fort McMurray corridor while travelling to Edmonton routinely from the region, Wowk says having more spaces available for his staff and other commercial drivers during long drives is positive.
"It gives them a break from sitting in the seat for five or six hours."
In recent years, Wowk says he's noticed more locations serviced with food, gas and washrooms open on major highways to the north and around the region.
"The last 15 years, they've added a number (or areas) all over on Highway 36," he said, adding, Highway 63 and Highway 28 also appear to have more stops, which are usual routes drivers take when transporting goods.
Safety for motorists
Ultimately, with more locations on the way, it's not only beneficial for commercial users who may experience fatigue during hauls, but also for recreational motorists who share the highway space and need a safe location to take breaks.
"When drivers are fatigued or have to stop and don't have a place to stop, sometimes stopping in the wrong place is going to be an issue," said Wowk. Moreover, it helps avoid situations where people are forced to pull over on emergency lanes, he added.
Developments needed
While Wowk finds the current rest areas throughout the three-hour trip north to Fort McMurray sufficient, he would like to see more rest areas created toward the south, from Lac La Biche to Edmonton, for example.
"We go to Edmonton too, but there isn't a place to stop," he says, hoping to see the provincial initiative create safe spaces along that route.
For some female truck drivers in Alberta, the rest stops don't just mean an opportunity to relax, but also a safer and more "ideal rest stop." Rest stops that are well lit, example, are important, according to Shannon Holicza, in-cab instructor at Bison Transport, based in Sherwood Park.
"I am delighted that the Alberta Government has launched an initiative to improve rest areas. Drivers are typically behind the wheel for up to 13 hours daily. Having a safe, clean place to refresh can make all the difference," said Holicza.
After Alberta Transportation evaluates proposals, it will select the highest scoring one and negotiate the scope for each of the selected sites, according to information from the provincial government.
"Sites currently identified for development and any future sites will only be developed following consultation and input from local stakeholders."
The province also noted that "Costs associated with commercial developments will be paid by the private sector and recovered through business revenue."
About the Author: Rahma Dalmar
This has been shared 0 times
This story was important to me or our community: view results >
Get your daily Bow Valley news briefing
More Beyond Local
Sunny days for Alberta farmers thanks to high commodity prices
Brighten up winter cooking with citrus, from juice to zest
UK's Princess Eugenie expecting second child this summer
See a typo/mistake?
Have a story/tip?
ONLINE POLL: Do you think more wildlife fencing is needed along the Trans-Canada Highway? view related story
Results > Archives >
About RMOToday.com
© 2023 RMOToday.com


The automatic choice for even greater quality of living.
Smart Home - "the comprehensive solution".
Smart Home centrally controls and monitors domestic installations such as lighting and heating technology as well as security installations. These are automatically adapted to satisfy current requirements. And if you so desire, this can be done independently and reliably to ensure optimum quality of living, energy efficiency and security for both you and your home.
Smart Home is self-regulating thanks to numerous sensors, which provide information about current light conditions, indoor temperatures and movements inside the house. Depending on the measurements taken, lights are switched on or off, blinds are opened or closed and the heating is turned up or down.
Make your home smart. Smart Home with Griesser – the automatic choice.