Barack Obama's invocation of "the destructive power of a warming planet" in his victory speech has stoked expectation that he will act on climate change in his second term.
Environmental campaigners are already mobilising to hold the president to that promise.
They argued Obama's re-election, amid the devastation of superstorm Sandy, was a clear mandate for action on climate change, in stark contrast to Mitt Romney, who turned sea-level rise into a laugh line in the biggest speech of his political career.
Campaigners put Obama on immediate notice, calling an 18 November demonstration at the White House to demand he scrap the controversial Keystone XL pipeline.
"In the wake of hurricane Sandy, as the warmest year in American history draws to a close, as the disastrous drought lingers on in the midwest, everyone is looking for ways to make a real difference in the fight to slow climate change," said an open letter from 350.org and the Sierra Club.
But a strategic decision by the White House in 2009 to downplay climate change, and Obama's avoidance of the issue during the campaign, makes it tricky for the president to now claim that he was elected to act on the issue.
The Republicans' continued control of the House of Representatives will also continue to limit Obama's scope for action.
However, environmental campaigners said Sandy – and an endorsement from New York city mayor, Michael Bloomberg, due to Obama's position on climate change – create public space for the president to act.
"Of course president Obama certainly did not take up the cause in the way we had hoped but he has indicated in numerous events and in the New Yorker and Rolling Stone that climate will be a top priority for his second term," said Betsy Taylor, president of the climate strategy firm Breakthrough Solutions. "There is reason to feel hope. We moved from silence to a growing mandate for action."
A number of newly elected Democrats in the Senate and the House of Representatives also owe their victories, in part, to support from environmental campaign groups, giving greens more allies in Congress.
The president has a chance early on to show he intends to deliver on climate change.
The first big decision will be on the Keystone XL pipeline, a project designed to expand production of the Alberta tar sands by pumping crude to Texas refineries. The administration is due to make its decision early next year and many believe that Obama will approve the pipeline.
Environmental groups will also be watching whether Obama continues to fight to keep tax credits for the wind industry during the lame duck session of Congress. Their expiry at the end of the year has hurt the industry, leading to lay-offs. Obama has said he will continue to fight $46bn in subsidies to the fossil fuel industry.
Then there are appointments. Obama came to the White House in 2009 with a green "dream team" including Nobel laureate, Steve Chu, as energy secretary. Obama will have to make new appointments in his second term.
He must also decide whether to resurrect the post of White House climate adviser, which has been empty since early 2011 when Carol Browner stepped down. That could help push policies blocked by Congress.
Now that Obama has a second term, the Environmental Protection Agency is also expected to move more aggressively on tightening rules on mercury and carbon dioxide emissions.
But the environmental community will be looking for Obama to deliver the big changes that will move America towards a low-carbon future – and protect the country from the extreme weather, rising seas and other consequences of future climate change.
At its most ambitious, that would involve some kind of carbon tax – an option that is now a topic of discussion at a number of Washington thinktanks, including the conservative American Enterprise Institute.
What does Obama's victory mean for action on global warming?


Summer Seventeen: Floral Nails with Essie's Summer Collection!
Wow, I can't believe we're eleven days into July! This summer is going by super quick, though there are moments of humidity that seem to last forever. I'm here to share with you a simple nail tutorial using Essie's Summer 2017 Collection! For years and years, I've definitely been caught up with each of Essie's seasonal collection launches, but I haven't seen one quite like this. Inspired by parisian pastries, this collection definitely feels light and feminine, with touches of sparkle!
Keep reading for a quick and simple nail tutorial!
As always, Essie never fails with the names of their polishes!
After prepping your nails and using base coat, apply two layers of "sweet souffle" for a base color.
Using a toothpick or dotting tool, gently apply five dots in a circle using "baguette me not", creating a flower shape.
Do the same with another accent finger using the color "eclair my love".
Complete your flower by dotting the centers with "fondant of you" and "s'il vous play".
To take a fancy step further, use "blue-la-la" to add leafy details! Don't forget to finish off with a top coat!
Hope you liked this tutorial! Stay tuned for more.


The frog cannot survive long outside its natural habitat and will die if you do not make it to the lake in time.
Eyeball Frog (technical name: eyeballfrog) is item number #282 on Kokaro and belongs to an item set with 81 other items in its full set. It has a rarity factor of 4.
70 of these items currently are owned and exist in Kokaro by a total of 39 players.
Eyeball Frog is from the game, The Legend of Zelda: Ocarina of Time.


text:
"I feel like I'm speaking to a friend- a professional, laid back attitude." - client
How House Bill 1693 May Affect Your Litigation
by Stacy Thompson
The Texas legislature recently passed (and governor Abbot signed) House Bill number 1693, which amended §18.001 of the Civil Practice and Remedies Code — the portion of the Civil Practice and Remedies Code that governs affidavits and counter-affidavits regarding the reasonableness and necessity of medical services. The amendments provide critical clarity to several key issues faced by defendants litigating personal injury matters — including the scope of counter-affidavits, applicable deadlines, and procedure.
I. Overview of Texas Civil Practice & Remedies Code § 18.001.
Texas Civil Practice & Remedies Code § 18.001 is a procedural statute prescribing the use of affidavits to simplify proof that medical expenses are reasonable and necessary. An affidavit satisfying the requirements contained in Section 18.001 serves as sufficient evidence to support a jury finding that the amount charged for the medical treatment was reasonable or that the service was necessary. The statute specifically indicates that these affidavits can be controverted which requires that plaintiff prove reasonableness and necessity by legally sufficient evidence at trial. Filing a proper controverting affidavit forces the offering party to prove reasonableness and necessity by expert testimony at trial.
II. Section 18.001 Counter-affidavits.
Prior to the passage of H.B. 1693 in 2019, the majority of Texas courts recognized that uncontroverted affidavits did not establish causation between the defendant's tortious conduct and the plaintiff's medical expenses. Therefore, regardless of whether an affidavit was filed, plaintiffs had to establish their medical expenses were necessitated by the negligent conduct of acts or omissions of defendant.
In drafting H.B. 1693, the Legislature added specific language clarifying that 18.001 affidavits are not evidence of and do not support a finding of causation. Similarly, the Legislature clarified that counter-affidavits cannot be used to controvert the causation element of a civil cause of action.
III. Relevant Deadline Changes.
In addition, H.B. 1693 alters the deadlines for both service of initial affidavits and service of counter-affidavits. "The party offering the affidavit in evidence must serve a copy of the affidavit on each other party to the case by the earlier of: (1) 90 days after the date the defendant files an answer; (2) the date the offering party must designate any expert witness under a court order; or (3) the date the offering party must designate any expert witness as required by the Texas Rules of Civil Procedure." Tex. Civ. Prac. & Rem. Code 18.001 (d). This change requires plaintiffs to serve 18.001 affidavits more than 30 days before trial.
Regarding counter-affidavits, the statute's amended language provides counter-affidavits must be served by the earlier of: (1) 120 days after the date the defendant files its answer; (2) the date the party offering the counter-affidavit must designate expert witnesses under a court order; or (3) the date the party offering the counter-affidavit must designate any expert witness as required by the Texas Rules of Civil Procedure. Tex. Civ. Prac. & Rem. Code 18.001 (e).
In sum, defendant must controvert within 30 days of being served with plaintiff's affidavit.
IV. Changes to Filing Requirements.
For the first time, the Legislature also addressed the relationship between the filing of affidavits and the beginning of medical treatment. Under the new amendments, if a plaintiff receives medical treatment from a medical provider for the first time after a defendant files its Answer, then the plaintiff must serve its 18.001 affidavit for that provider on the defendant by the plaintiff's expert designation deadline set out by Court Order or the Texas Rules of Civil Procedure. Tex. Civ. Prac. & Rem. Code 18.001 (d-1). If a defendant receives an affidavit from such a medical provider, then the defendant has either 30 days or until its expert designation deadline, whichever is later.
If a plaintiff continues to receive medical care from a medical provider after it has served an 18.001 affidavit, then the plaintiff can submit supplemental 18.001 affidavits, on or before the 60th day prior to the commencement of trial, and a defendant may file a counter to this supplemental affidavit on or before the 30th day before the commencement of trial.
V. Alterations to Procedure Providing Notice.
Plaintiffs routinely "served" medical cost affidavits inconspicuously attached to disclosures or other production or piecemealed them throughout the discovery process. The Legislature has seemingly put a stop to this practice by now requiring "[t]he party offering the affidavit to file notice with the clerk of the court when serving the affidavit that the party or the attorney served a copy of the affidavit…" In sum, plaintiff attorneys must file a notice via the electronic filing system that §18.001 affidavits were served. Similarly, the party offering a counter-affidavit must also file notice when serving the counter-affidavits.
H.B. 1693 does not clarify whether individuals other than medical doctors within the specific field of medical care produced in the initial affidavit may opine as to the reasonableness and necessity of medical expenses, leaving a looming question unanswered. In other words, whether chiropractors can opine on care rendered by a pain management physician remains unclear. See also Gunn v. McCoy, 554 S.W.3d 645 (2018) (holding the plain language of § 18.001 does not require affidavits be made by a records custodian for a medical provider); In re Brown, 2019 WL 1032458 (Tex. App.—Tyler 2019) (holding mandamus was appropriate for trial court's striking of counter-affidavits filed by defendant and counter-affidavits completed by nurse were sufficient under §18.001.
VI. Takeaways and Practical Considerations
Plaintiffs can no longer simply wait to submit 18.001 affidavits 30 days prior to evidence being submitted at trial. If a plaintiff was treating with a provider prior to a defendant filing an Answer, the plaintiff is required to serve its affidavit within 90 days of defendants Answer or plaintiff will be required to prove the care and expenses were reasonable and necessary at trial.
Defendants (and their insurers) should begin seeing more complete sets of medical records and bills at earlier points in litigation.
Since the new 18.001 language places stricter deadlines on plaintiffs, we anticipate seeing more Agreed Scheduling Orders from plaintiffs and defendants that establish agreed 18.001 deadlines, which will make life easier for all litigants.

redpajama_set_name: RedPajamaCommonCrawl


Gareth Shaw is eight shots off the lead in IndiaGareth Shaw was relieved to make the cut on his 2013 Challenge Tour debut but hopes he may now have the freedom to make a weekend charge and chase down leader Andrew McArthur.
Eight strokes behind the Scot following a second successive level par 72 in the Gujarat Kensville Challenge in India, the 27-year old from Lurgan is not giving up hope of a maiden victory.
"It is a bit of a relief," said Shaw, who made the three over par cut by three shots despite some nervous moments in his second round.
"I felt a bit nervous when I was one over with five left and had a couple of par saves and they were nice because you start to feel good about yourself.
Tournament leader Andrew McArthur. Credit: Karolina Gembara"You come all this way and then if you were to miss the cut you have to stay around all weekend so it would have been a bit annoying but it's my first tournament of the year so I have got to be pleased with my start.
"It's completely different to what I'm used to but course management is key here and that has always been one of my strengths.
McArthur, meanwhile, added a 69 to his opening 67 to move two shots clear of Shiv Kapur and into pole position for a first European Challenge Tour title in five years.
Home favourite Kapur appeared inspired by a visit from Indian cricket legend Sachin Tendulkar to Kensville Golf and Country Club, carding a one under par 71 to enter the weekend in second place on six under.
** M Singh Pathania (Ind) 80 RT, C Ford (Eng) 73 DQ.
Ulsterman Gareth Shaw repaid the faith shown in him by stablemate Graeme McDowell when he grabbed a share of fourth place in the Challenge of Ireland at Glasson Golf Hotel and Country Club.
Austin Domingo. Photo by Karolina Gembara.Gareth Shaw opened with a pair of level par 72s to make the cut on his 2013 Challenge Tour debut in India.
India's Shiv Kapur. Picture by Karolina Gembara.Gareth Shaw crashed to a third round 80 as India's Shiv Kapur fired a brilliant course record 65 in the Gujarat Kensville Challenge to move four shots clear with a round to play.
Shiv Kapur with the Gujarat Kensville Challenge trophy at Kensville Golf and Country Club. Photo by Karolina Gembara.Gareth Shaw was looking on the bright side despite finishing well down the field in his opening Challenge Tour start of the season.
Czech Challenge leader Adam Gee. Picture by Getty Images. Gareth Shaw fired his third successive 69 to move into the top 20 with a round to play in D+D Real Czech Challenge Open.


text:
Robert Endre Tarjan (Pomona (Californië), 30 april 1948) is een Amerikaans informaticus.

Hij heeft tijdens zijn loopbaan veel werk gedaan aan de ontwikkeling van algoritmen en datastructuren. Hij heeft een aantal bekende graafalgoritmes ontwikkeld, waaronder het Tarjan's off-line least common ancestors algoritme.

Tarjan studeerde wiskunde aan het California Institute of Technology, waar hij in 1969 zijn bachelor behaalde. Zijn mastersdiploma behaalde hij aan de Stanford-universiteit in 1971 in de informatica, waarna hij een promotie in de informatica en wiskunde deed in 1972 -- zijn promotiewerk was An Efficient Planarity Algorithm (handeled over een efficiënt algoritme om de planariteit van een graaf te bepalen). Zijn promotoren in Stanford waren Donald Knuth en Robert W. Floyd, beide bekende informatici.

Na zijn studie heeft Tarjan een uitgebreide loopbaan gehad, zowel in academische als in commerciële kringen. Hij heeft gewerkt aan de Cornell University te New York, het California Institute of Technology ofwel Caltech en tussen 1974 en 1980 was hij docent in Stanford. Daarna werkte hij gelijktijdig aan het AT&T Bell Laboratories en de New York University. In 1985 keerde hij als hoogleraar terug naar Princeton, waar hij nog steeds werkt (hij bekleedt de leerstoel van de James S. McDonnell Distinguished University Professor of Computer Science). Tegelijkertijd met zijn werk voor Princeton heeft hij gewerkt bij NEC, MIT, InterTrust, Compaq en Hewlett-Packard (ook hier werkt hij nu nog).

Tarjan heeft twee boeken gepubliceerd en 55 artikelen en conferentiestukken gepubliceerd. Hij heeft ook zo'n 155 publicaties beoordeeld voor officiële publicaties. Daarnaast heeft hij zich als redacteur, lid of referee verdienstelijk gemaakt voor 26 organisaties binnen de Association for Computing Machinery.

Tarjan is tijdens zijn loopbaan geëerd met zo'n 20 prijzen en fellowships. Een hiervan was de Turing Award van 1986, die hij samen met John Hopcroft won voor fundamentele resultaten in het ontwerp en de analyse van algoritmen en datastructuren.

Amerikaans wiskundige
Winnaar van de A.M. Turing Award
Amerikaans informaticus

redpajama_set_name: RedPajamaWikipedia


Over the past few years I've racked up quite a collection of beer related t-shirts. From breweries I've been to, general craft beer shirts and random swag I've been given, my closet is a good indication of my love for all things beer related.
One thing I've noticed when going to beer festivals is that there are tons of other people out there like me who love to rock shirts dedicated to the greatest beverage on earth.
I've found a lot of great companies online and my favorite is I Love Apparel and their collection of beer t-shirts. Below, you can find 10 of my favorite shirts they offer.
#3 I Brew Beer What's Your Super Power?
This is definitely a nice change from the usual brewery shirt! Thanks for sharing, cheers!


text:
Async JS Control Flow Showcase
==============================

This is a project designed to showcase different ways to handle asynchronous
control flow in Javascript. If you're familiar with this concept, you might
want to skip to the [list of projects](#alternatives) or the [description of
callback issues](#issues).

Note that this is meant to be an informational, not a competitive, guide to
all the approaches to flow control on offer.

Background
----------
Javascript applications, including Node.js-based software, are most frequently
structured around event-driven or asynchronous methods. It's possible that
a function `foo` or `bar` could kick off some logic that is not yet complete
when the functions themselves complete. One common example of this is
Javascript's `setTimeout()`. `setTimeout`, as the name implies, doesn't
actually pause execution for a designated amount of time. Instead, it schedules
execution for a later time, and meanwhile returns control to the script:

```js
var done = function() {
    console.log("set timeout finished!");
};

setTimeout(done, 1000);
console.log("hello world");
```

The output of this script is:

```
hello world
set timeout finished!
```

Callbacks
---------
Node.js has generalized this asynchronous control flow idea through the use of
callbacks. This is a convention whereby an asynchronous function takes
a parameter which is itself a function. This function, called a callback, is
then called whenever the asynchronous result is ready. In Node, callbacks are
called with the convention that an Error object is passed as the first
parameter for use in error handling, and further results are sent as subsequent
parameters. Let's take a look at an example:

```js
var fs = require('fs');

var readFileCallback = function(err, fileData) {
    if (err) {
        console.log("We got an error! Oops!");
        return;
    }
    console.log(fileData.toString('utf8'));
};

fs.readFile('/path/to/my/file', readFileCallback);
```

In this example, we use a callback-based method `fs.readFile()` to get the
contents of a file. The function `readFileCallback` is called when the file
data has been retrieved. If there was an error, say because the file doesn't
exist, we get that as the first parameter, and can log a helpful message.
Otherwise, we can display the file contents.

Because we can use anonymous functions, it's much more common to see code that
looks like this:

```js
var fs = require('fs');

fs.readFile('/path/to/my/file', function(err, fileData) {
    if (err) {
        console.log("We got an error! Oops!");
        return;
    }
    console.log(fileData.toString('utf8'));
});
```

This architecture can be quite powerful because it is non-blocking. We could
easily read two files at the same time just by putting calls to `fs.readFile`
one after the other:

```js
var fs = require('fs');

var readFileCallback = function(err, fileData) {
    if (err) {
        console.log("We got an error! Oops!");
        return;
    }
    console.log(fileData.toString('utf8'));
};

fs.readFile('/path/to/my/file', readFileCallback);
fs.readFile('/path/to/another/file', readFileCallback);
```

In this example, the file contents will be printed out in an undetermined order
because they're kicked off at roughly the same time, and their callbacks will
be called when the system is done reading each one, which could vary based on
many factors.

The impact of callbacks
-----------------------
There are a number of issues that arise as part of a callback-based
architecture. These issues range from the aesthetic to the practical (e.g.,
some argue callbacks lead to less readable or less maintainable code).

### Rightward drift

It often happens that you want to run a number of asynchronous methods, one
after the other. In this case, each method must be called in the callback of
the previous method. Using the anonymous function strategy detailed above, you
end up with code that looks like this:

```js
asyncFn1(function() {
    asyncFn2(function() {
        asyncFn3(function() {
            asyncFn4(function() {
                console.log("We're done!");
            });
        });
    });
});
```

To some people, once you start filling these functions out with their own
particular logic, it's very easy to lose track of where you are in the logical
flow.

### Branching logic

Sometimes you might want to call a function `bar()` only if the result of
another function `foo()` matches some criteria. If these are synchronous
functions, the logic looks like this:

```js
var res = foo();
if (res === "5") {
    res = bar(res);
}
res = baz(res);
console.log("After transforming, res is " + res);
```

If `foo` and `bar` are asynchronous functions, however, it gets a little more
complicated. One option is to duplicate code:

```js
foo(function(res) {
    if (res === "5") {
        bar(res, function(res2) {
            baz(res2, function(res3) {
                console.log("After transforming, res is " + res3);
            });
        });
        return;
    }
    baz(res, function(res2) {
        console.log("After transforming, res is " + res2);
    });
});
```

In this case, we've duplicated the calls to `baz`. An alternative is to create
a `next` function that encapsulates the `baz` call and subsequent log
statement:

```js
var next = function(res) {
    baz(res, function(res2) {
        console.log("After transforming, res is " + res2);
    });
};

foo(function(res) {
    if (res === "5") {
        bar(res, function(res2) {
            next(res2);
        });
        return;
    }
    next(res);
});
```

This is more DRY, but at the cost of creating a function whose only purpose is
to continue the logical flow of the code, called in multiple places.

### Looping

If you need to perform an async method on a number of objects, it can be
a little mind-bending. Synchronously, we can do something like this:

```js
var collection = [objA, objB, objC];
var response = [];
for (var i = 0; i < collection.length; i++) {
    response.push(transformMyObject(collection[i]));
}
console.log(response);
```

If `transformMyObject` is actually asynchronous, and we need to transform each
object one after the other, we need to do something more like this:

```js
var collection = [objA, objB, objC];
var response = [];
var doTransform = function() {
    var obj = collection.unshift();
    if (typeof obj === "undefined") {
        console.log(response);
    } else {
        transformMyObject(obj, function(err, newObj) {
            response.push(newObj);
            doTransform();
        });
    }
};
doTransform();
```

### Error handling

You can't use Javascript's basic error handling techniques (try/catch) to
handle errors in callbacks, even if they're defined in the same scope. In other
words, this doesn't work:

```js
var crashyFunction = function(cb) {
    throw new Error("uh oh!");
};

var runFooBar = function(cb) {
    foo(function() {
        crashyFunction(function() {
            bar(function() {
                cb();
            });
        });
    });
};

try {
    runFooBar(function() {
        console.log("We're done");
    });
} catch (err) {
    console.log(err.message);
}
```

This is why Node.js uses a convention of passing errors into callbacks so they
can be handled:

```js
var crashyFunction = function(cb) {
    try {
        throw new Error("uh oh!");
    } catch (e) {
        cb(e);
    }
};

var runFooBar = function(cb) {
    foo(function(err) {
        if (err) return cb(err);
        crashyFunction(function(err) {
            if (err) return cb(err);
            bar(function(err) {
                if (err) return cb(err);
                cb();
            });
        });
    });
};

runFooBar(function(err) {
    if (err) return console.log(err.message);
    console.log("We're done!");
});

```

As you can see, the result of this is that we have to check the error state in
every callback so we can short-circuit the chain and pass the error to the
top-level callback. This is a bit redundant at best.

Node.js now has domains, which makes this problem a little easier to
handle.

Alternatives to callbacks
-------------------------
Of course, callbacks aren't the only way to do asynchronous control flow. There
are many helpful libraries that make using callbacks less prone to the issues
above. There are also alternatives which aren't callback-based at all, though
they might rely on callbacks under the hood. The point of this project is to
enable a side-by-side comparison of these approaches.

The [callbacks directory](callbacks/) of this repo has a number of reference
Javascript files which demonstrate in code how callback-based flow control
works. These files can all be run using Node.js.

The following projects have implemented, or are in the process of implementing,
revisions of the reference scripts using their particular approach to
asynchronous control flow. Please check them out, read the directory's README
to see how they address the issues above, run the code, and make an informed
decision about which approach to adopt in your own projects!

Hint: take a look at the "kitchen sink" example file in each of the projects to
see how they handle all the issues in one script.

* [Callbacks](callbacks/) (i.e., the "standard" or "naive" approach above)

Other approaches:

* [Bluebird](promises-bluebird/) [[project](https://github.com/petkaantonov/bluebird)]
* Caolan/async [[project](https://github.com/caolan/async)]
* Co [[project](https://github.com/visionmedia/co)]
* IcedCoffeeScript [[project](http://maxtaco.github.io/coffee-script/)]
* [Max Ogden style callbacks](maxogden-style/) [[website](http://callbackhell.com)]
* [Monocle-js](monocle-js/) [[project](https://github.com/jlipps/monocle-js)]
* Q [[project](https://github.com/kriskowal/q)]
* When [[project](https://github.com/cujojs/when)]
* bevacqua/contra [[project](https://github.com/bevacqua/contra)]

[![Bitdeli Badge](https://d2weczhvl823v0.cloudfront.net/jlipps/async-showcase/trend.png)](https://bitdeli.com/free "Bitdeli Badge")

redpajama_set_name: RedPajamaGithub


text:
The Evans Family had a vaudeville family dance act in the mid-1900s. The Evans were the only complete American family in a war zone during World War II in the course of their performance tours of US military bases. The Evans family continued touring the US through 1960, playing engagements in all major cities and making television appearances.

Background
Evan E. Evans began dancing as a child in Pittsburgh, Pennsylvania. In 1910, Evan married Helen Hartz, a fellow vaudeville circuit dancer. The married couple toured together and continued to tour following the birth of their first child, Maryetta Evans, in 1912, then settled back in Pittsburgh around the time of the birth of their second child, Lester Evans. Evan and Helen operated a dance studio in Homestead, and Maryetta and Lester were educated in Pittsburgh. Maryetta went on to study at the Art Institute of Pittsburgh, and Lester at University of Pittsburgh. The family developed their new touring act and took to the stage as "Four Evans: Two Generations of Dance."

"The Four Evans"
In 1942, The Evans Family were scouted by the United Service Organizations (USO) to perform at American military service locations. Between 1942 and 1953, the Four Evans completed USO tours of Europe, Africa, Japan, Korea, Greenland, and the United States. The Evans performed in Bastogne during the Battle of the Bulge, and escaped Belgium with Pennsylvania's 28th Division. Between 1946 and 1960, the Four Evans danced in major cities throughout the United States and played extended engagements at New York's Paramount Theatre. In 1944, the family performed for the Lord Mayor of London, England; in 1947, they danced for the Premier of Canada; in 1949, they appeared on WDTV, Pittsburgh's (and Pennsylvania's) first television station. In 1953, while traveling internationally, the Evans family survived a plane crash in the sea of Japan.

After "The Four Evans"
From 1960, the Evans family operated a dance studio in Homestead. In 1962, Evan E. Evans died in Homestead at age 73. Lester Evans taught at Point Park University, and at Pittsburgh Creative and Performing Arts School, and he owned the Homestead studio from 1962. In 1974, Lester and Maryetta appeared on Mister Rogers' Neighborhood. Also in 1974, Helen Evans died at age 80. In the 1980s, Lester and Maryetta Evans toured again as "The Four Evans," with younger Evans family members. After Lester Evans died in 1989, Maryetta moved to Florida, where she continued to dance and instruct. In the late 1990s, while living in Palm Springs, Florida, Maryetta danced with The Fabulous Palm Springs Follies. In 1999, The Guinness Book of World Records named her the World's Oldest Professional Show Dancer at age 86. Maryetta Evans died in 2009.

References

People from Homestead, Pennsylvania
Musical groups from Pennsylvania
Vaudeville performers
Musicians from Pittsburgh
Culture of Pittsburgh


text:
Houornis is a genus of enantiornithean birds from the Jiufotang Formation of Liaoning, People's Republic of China. It is known from a single species, Houornis caudatus, which had been once been classified as a species of Cathayornis, and has also been regarded as a nomen dubium.

Description
Houornis caudatus was a small enantiornithean with a slightly elongated, toothy snout and perching feet. It is known only from a single specimen, the slab and counter-slab of a fossil catalogued as number IVPP V10917/2 in the collections of the Institute of Vertebrate Paleontology and Paleoanthropology in Beijing. The specimen was found in 1993 by Zhou Zhonghe near the town of Boluochi in Liaoning Province, China. The actual bones of this specimen were not preserved, but rather can be seen by the impressions they left in the surrounding rock. It was originally thought to have a relatively long, bony tail intermediate in length between modern birds and long-tailed birds like Archaeopteryx, and so was in 1997 by Hou Lianhu given the name Cathayornis caudatus, meaning "tailed Cathay bird". This interpretation was later found to be in error, though it does appear to have an unusually long pygostyle (a component of the tail made of fused vertebrae).

While some researchers have considered the species dubious due to the poor preservation quality and incomplete nature of the fossil, a 2015 study by Wang Min and Liu Di was complete enough to be compared to similar species, including Cathayornis, and so they assigned it to its own genus, Houornis, the generic name honouring Hou. Wang and Liu found that Houornis can be told apart from similar species by several anatomical details, including the large pygostyle that gave it its name. Specimen IVPP V10533, the rear of a skeleton, had in 1997 been referred to the species by Hou and this was confirmed in 2015. Two additional but very fragmentary specimens, IVPP V9936 and V10896, have been referred to C. yandica in the past, but cannot be directly compared with the type specimen because they do not preserve any of the same key parts of the skeleton.

Classification
Cathayornis caudatus was so named for its supposedly long bony tail lacking a pygostyle, and was further differentiated by its small size (the humerus, or upper arm bone, is less than  long). In a 2010 paper, O'Connor and Dyke re-examined the specimen and showed that it is in fact only slightly smaller than the type specimen of C. yandica, and that a normal enantiornithean tail with a pygostyle is clearly visible in one of the fossil slabs, parts of the hip bones having been mistaken for unfused tail vertebrae. O'Connor and Dyke therefore considered C. caudatus a nomen dubium. However, in a 2015 re-evaluation of supposed "cathayornithids", Wang and Liu determined that C. caudatus could be differentiated from Cathayornis, but could not determine its relationships with other members of Enantiornithes using a phylogenetic analysis. They placed Houornis as incertae sedis.

References

Bird genera
Early Cretaceous birds of Asia
Euenantiornitheans
Fossil taxa described in 1997
Fossil taxa described in 2015


text:
package httpbinding

import (
	"encoding/base64"
	"math"
	"math/big"
	"net/url"
	"strconv"
)

// QueryValue is used to encode query key values
type QueryValue struct {
	query  url.Values
	key    string
	append bool
}

// NewQueryValue creates a new QueryValue which enables encoding
// a query value into the given url.Values.
func NewQueryValue(query url.Values, key string, append bool) QueryValue {
	return QueryValue{
		query:  query,
		key:    key,
		append: append,
	}
}

func (qv QueryValue) updateKey(value string) {
	if qv.append {
		qv.query.Add(qv.key, value)
	} else {
		qv.query.Set(qv.key, value)
	}
}

// Blob encodes v as a base64 query string value
func (qv QueryValue) Blob(v []byte) {
	encodeToString := base64.StdEncoding.EncodeToString(v)
	qv.updateKey(encodeToString)
}

// Boolean encodes v as a query string value
func (qv QueryValue) Boolean(v bool) {
	qv.updateKey(strconv.FormatBool(v))
}

// String encodes v as a query string value
func (qv QueryValue) String(v string) {
	qv.updateKey(v)
}

// Byte encodes v as a query string value
func (qv QueryValue) Byte(v int8) {
	qv.Long(int64(v))
}

// Short encodes v as a query string value
func (qv QueryValue) Short(v int16) {
	qv.Long(int64(v))
}

// Integer encodes v as a query string value
func (qv QueryValue) Integer(v int32) {
	qv.Long(int64(v))
}

// Long encodes v as a query string value
func (qv QueryValue) Long(v int64) {
	qv.updateKey(strconv.FormatInt(v, 10))
}

// Float encodes v as a query string value
func (qv QueryValue) Float(v float32) {
	qv.float(float64(v), 32)
}

// Double encodes v as a query string value
func (qv QueryValue) Double(v float64) {
	qv.float(v, 64)
}

func (qv QueryValue) float(v float64, bitSize int) {
	switch {
	case math.IsNaN(v):
		qv.String(floatNaN)
	case math.IsInf(v, 1):
		qv.String(floatInfinity)
	case math.IsInf(v, -1):
		qv.String(floatNegInfinity)
	default:
		qv.updateKey(strconv.FormatFloat(v, 'f', -1, bitSize))
	}
}

// BigInteger encodes v as a query string value
func (qv QueryValue) BigInteger(v *big.Int) {
	qv.updateKey(v.String())
}

// BigDecimal encodes v as a query string value
func (qv QueryValue) BigDecimal(v *big.Float) {
	if i, accuracy := v.Int64(); accuracy == big.Exact {
		qv.Long(i)
		return
	}
	qv.updateKey(v.Text('e', -1))
}


UMBC (3-8) returns to the court after completing the final examination period on Sat., Dec. 21 when they take the short trip down I-295 to face a red-hot George Washington (9-1) squad. Tip-off time is set for 2:30 p.m. and Paul Mittermeier brings fans all the action on Q1370 radio or www.q1370.com. Links are also available for live stats and live streaming of the contest.
RETRIEVER UPDATE: UMBC will complete its four-game road swing (over 2.5 weeks) still searching for its first victory away from home. After five halves of outstanding shooting, the Retrievers cooled off dramatically in a 91-71 setback at Coppin State on Dec. 11. Freshman guard Rodney Elliott led UMBC with 16 points and earned his second America East Rookie of the Week honor on Dec. 16. Elliott leads UMBC with 14.1 points per game. SR G Quentin Jones is averaging 10.0 ppg and shooting 66.7% from the floor in his last four outings.
COLONIAL UPDATE: In its latest outing on Dec. 11, the Colonials rallied from an eight-point halftime deficit to defeat Boston University, 70-60, at the Charles E. Smith Center.GW, winner of five straight, is now 9-1 - its best start since 2005-06 and tied for the eighth-best start in its 100 seasons of intercollegiate basketball. The victory moved the Colonials to 5-0 at home this season and was the sixth straight win at Smith Center. Graduate student Maurice Creek leads a potent offense with 15.7 points per game and is 26-of-56 (46.4%) from behind the arc.
WHO'S UP NEXT: UMBC returns from holiday break to host Navy in the back end of a home-and-home series vs. the Midshipmen. The game is set for Mon., Dec. 30 with a 7:00 p.m. tip at the RAC Arena.


At the time of writing this post, Oracle Forms 11g installations are configured by default to work with a specific JPI (Java Plug-In) version: 1.6.0_12.
Save the formsweb.cfg file (no restarts necessary).
Your solution will work, but if you want to retain the minimum JPI version check, just replace "jpi-version" with "version". JRE 6 update 10 introduced the change to jpi-version and you should now use "version". Oracle forms just hasn't caught up with Oracle java yet.
In this example, the use of version is similar to using the Dynamic CLSID for IE. This example would permit any version 1.4 or newer to be used. It is important to not include the third digit (1.4.x) in order for this to work correctly.
Thank you very much, you are a genious, everything works fine :D,I love your tutorials.


Manufacturer Printable type 2 diabetes Coupon. Start saving now by printing your new savings card and taking it to your pharmacy with your prescription.
Eligible patients 18 years or older may pay as little as $0 with a maximum savings up to $250 For monthly prescription. card is valid for 12 months.
Any question regarding this card, Please call 1-866-279-8990.
Synjardy is from Boehringer Ingelheim Pharmaceuticals, Inc to improve blood sugar in adults with type 2 diabetes.
SYNJARDY is not for people with type 1 diabetes.
Prices for 60 tablets of Synjardy 12.5mg/1000mg is from $438.91-$537.44.
Synjardy Reusable Discount Card: Save up to 75% off retail price on your prescription medication!
Acceptable at over 63,000 pharmacies including all major chains (Walmart, CVS Pharmacy, Publix, Walgreens, Rite-Aid, etc.), price may little vary. Synjardy price look up, Check Synjardy discount price with card.
#Still Can not afford Synjardy? Get Generic from This Reliable Cheap Generic Site, additional EXCLUSIVE 10% discount.
After struggling to get my levels steady, the doctor had me try Synjardy. His hope was to lower the A1C and my blood sugar levels. I was very happy with how this medication helped with my diabetes management. My A1C and blood sugar levels have both dropped considerably. Finally, I feel like my blood sugar is not dangerously high. Its a good feeling to not be so worried. Im also very careful about my diet and I walk every day. Sometimes, I forget to take my afternoon dose which I know is not good. I have set an alarm now to remind me to take it.
Ever since I have started taking Synjardy, I feel so much more comfortable about my type 2 diabetes treatment. Synjardy is much more effective than the other medications that I tried. It helped me lose weight and my blood glucose levels are kept within target range. My A1C level is down twenty points already. I hope it goes down more. I am hopeful that it keeps working this well. The only side effect that I have experienced is being a bit more thirsty than usual which, of course, means I have to urinate more often.


Growing up in Ventura, Evan Bloom of Wise Sons Jewish Delicatessen had seders that were reminiscent of most Americans' Passover traditions: brisket seasoned with Lipton Onion soup mix, a haggadah courtesy of Maxwell House and sponge cake for dessert.
They aren't Bloom's favorite gastronomic memories, but they are his most formative: They helped to inspire San Francisco's only farm-to-table Jewish comfort food restaurant and its popular Passover Seders. The holiday begins at sundown on Monday, and the waiting list for the Mission District deli's sold-out dinners continues to grow.
It's easy to see why: Bloom and Wise Sons co-founder Leo Beckerman have developed a mouthwatering menu, including wine-braised brisket, pho-inspired matzo ball soup; bittersweet chocolate torte, and handmade matzo from Beauty's Bagels in Oakland.
Some recipes are borrowed from bubbes, some are sourced from like-minded Jewish chefs and others are the result of serious research and development.
How do you craft the best matzo ball? You test it against 20 others, which is what Bloom and Beckerman did when they started Wise Sons as a pop-up in San Francisco. "Streit's and schmaltz turned out to be the secret," Bloom says. Last year, they made 600 of those savory, springy balls.
The Wise Sons brisket, for instance, is salted two days ahead and simmered with fennel to make a fumet that is reduced to concentrate the flavors and then used as a sauce. The stock for their chicken soup is on the stove for 10 hours, simmering with chicken feet to give it a deep, dense flavor.
Before the pop-ups and brick-and-mortars — Bloom and Beckerman currently operate the deli on 24th Street and a cafe inside the Jewish Contemporary Museum — the Wise Sons met in the kitchen at UC Berkeley's Hillel, where they threw epic kosher barbecues together and eventually held Passover Seders in their apartment for up to 50 friends.
In 2010, a few years after graduation, they smoked their first pastrami in a San Francisco backyard. The two Los Angeles natives (Beckerman hails from Studio City) were frustrated by the lack of Jewish deli food in the Bay Area and realized there was only one solution: to make their own.
Like so many burgeoning local chefs, Bloom turned to incubator La Cocina for commercial kitchen time. In return, he put his Cal architecture degree to use, contributing to the construction of La Cocina's first San Francisco Street Food Festival.
Eager to test out their recipes, Bloom and Beckerman gathered folks together for deli dinners, and when the parties quickly expanded from 20 to 200 people, it was clear they weren't alone in their desire for good babkas and gefilte fish.
Over the years, their modern take on classic Jewish food has evolved — vegetarians fall in love with the smoked trumpet mushroom Reuben — but some of those original childhood recipes have found a place on the deli's Passover menu, including Bloom's grandmother's mock chopped liver, made with peas, string beans, caramelized onions and ground walnuts.
Sounds like pretty good gastronomic memories after all.
The Pasta Shop: Carryout feasts include house-made charoset, horseradish, chopped liver, matzo ball soup, savory potato kugel, gefilte fish and dark chocolate-covered matzo. Available through April 15 at both the Oakland and Berkeley locations. Go to www.rockridgemarkethall.com and click on The Pasta Shop.
Perbacco: Guest chef Joyce Goldstein will join San Francisco's Perbacco chef Staffan Terje for their seventh annual Seder, cooking recipes from her book, "Cucina Ebraica," for this four-course Italian dinner featuring crispy fried artichokes and Venetian sweet and sour mackerel. $52. April 16-17. Reservations: 415-955-0663, www.perbaccosf.com.
Comal: This Berkeley treasure is offering its second annual Seder event with two multicourse family-style dinners. Executive chef Matt Gandin has created a Mexican menu with jalapeno matzo balls and beef brisket in adobo. Dinners follow Sephardic traditions, incorporating rice, beans and corn into the meal. No haggadahs, just lively conversation. $60. April 14-15. www.comalberkeley.com.
Saul's Delicatessen: Takeout or reserve to dine in the Berkeley deli and enjoy a traditional Seder plate and a host of starters and entrees, including pureed beet with labne and za'atar and Marin Sun Farms braised brisket. April 15-19 (Saturday night is the Broadway singalong Seder) $52. saulsdeli.com.
Find San Francisco's Wise Sons Jewish Delicatessen at the Contemporary Jewish Museum, 736 Mission St., at the Ferry Building Market on Tuesdays, and at the original site, 3150 24th St., San Francisco; wisesonsdeli.com.


text:
Phibss: Molecular Gas Content and Scaling Relations in z 1-3 Massive, Main-sequence Star-forming Galaxies
L. J. Tacconi, R. Neri, R. Genzel, F. Combes, A. Bolatto, M. C. Cooper, S. Wuyts, F. Bournaud, A. Burkert, J. Comerford, P. Cox, M. Davis, N. M. Förster Schreiber, S. García-Burillo, J. Gracia-Carpio, D. Lutz, T. Naab, S. Newman, A. Omont, A. Saintonge
K. Shapiro Griffin, A. Shapley, A. Sternberg, B. Weiner
390 Citations (SciVal)
We present PHIBSS, the IRAM Plateau de Bure high-z blue sequence CO 3-2 survey of the molecular gas properties in massive, main-sequence star-forming galaxies (SFGs) near the cosmic star formation peak. PHIBSS provides 52 CO detections in two redshift slices at z ~ 1.2 and 2.2, with log(M *(M ☉)) ≥ 10.4 and log(SFR(M ☉/yr)) ≥ 1.5. Including a correction for the incomplete coverage of the M* -SFR plane, and adopting a "Galactic" value for the CO-H2 conversion factor, we infer average gas fractions of ~0.33 at z ~ 1.2 and ~0.47 at z ~ 2.2. Gas fractions drop with stellar mass, in agreement with cosmological simulations including strong star formation feedback. Most of the z ~ 1-3 SFGs are rotationally supported turbulent disks. The sizes of CO and UV/optical emission are comparable. The molecular-gas-star-formation relation for the z = 1-3 SFGs is near-linear, with a ~0.7 Gyr gas depletion timescale; changes in depletion time are only a secondary effect. Since this timescale is much less than the Hubble time in all SFGs between z ~ 0 and 2, fresh gas must be supplied with a fairly high duty cycle over several billion years. At given z and M *, gas fractions correlate strongly with the specific star formation rate (sSFR). The variation of sSFR between z ~ 0 and 3 is mainly controlled by the fraction of baryonic mass that resides in cold gas.
Astrophysical Journal
https://doi.org/10.1088/0004-637X/768/1/74
galaxies: evolution
galaxies: high redshift
galaxies ISM
ISM: molecules
10.1088/0004-637X/768/1/74
http://iopscience.iop.org/article/10.1088/0004-637X/768/1/74/meta
Dive into the research topics of 'Phibss: Molecular Gas Content and Scaling Relations in z 1-3 Massive, Main-sequence Star-forming Galaxies'. Together they form a unique fingerprint.
main sequence stars Physics & Astronomy 100%
molecular gases Physics & Astronomy 92%
galaxies Physics & Astronomy 60%
scaling Physics & Astronomy 57%
star formation Physics & Astronomy 46%
gases Physics & Astronomy 42%
gas Earth & Environmental Sciences 42%
star formation rate Physics & Astronomy 36%
Tacconi, L. J., Neri, R., Genzel, R., Combes, F., Bolatto, A., Cooper, M. C., Wuyts, S., Bournaud, F., Burkert, A., Comerford, J., Cox, P., Davis, M., Förster Schreiber, N. M., García-Burillo, S., Gracia-Carpio, J., Lutz, D., Naab, T., Newman, S., Omont, A., ... Weiner, B. (2013). Phibss: Molecular Gas Content and Scaling Relations in z 1-3 Massive, Main-sequence Star-forming Galaxies. Astrophysical Journal, 768(1). https://doi.org/10.1088/0004-637X/768/1/74
Phibss: Molecular Gas Content and Scaling Relations in z 1-3 Massive, Main-sequence Star-forming Galaxies. / Tacconi, L. J.; Neri, R.; Genzel, R. et al.
In: Astrophysical Journal, Vol. 768, No. 1, 01.05.2013.
Tacconi, LJ, Neri, R, Genzel, R, Combes, F, Bolatto, A, Cooper, MC, Wuyts, S, Bournaud, F, Burkert, A, Comerford, J, Cox, P, Davis, M, Förster Schreiber, NM, García-Burillo, S, Gracia-Carpio, J, Lutz, D, Naab, T, Newman, S, Omont, A, Saintonge, A, Shapiro Griffin, K, Shapley, A, Sternberg, A & Weiner, B 2013, 'Phibss: Molecular Gas Content and Scaling Relations in z 1-3 Massive, Main-sequence Star-forming Galaxies', Astrophysical Journal, vol. 768, no. 1. https://doi.org/10.1088/0004-637X/768/1/74
Tacconi LJ, Neri R, Genzel R, Combes F, Bolatto A, Cooper MC et al. Phibss: Molecular Gas Content and Scaling Relations in z 1-3 Massive, Main-sequence Star-forming Galaxies. Astrophysical Journal. 2013 May 1;768(1). Epub 2013 Apr 16. doi: 10.1088/0004-637X/768/1/74
Tacconi, L. J. ; Neri, R. ; Genzel, R. et al. / Phibss: Molecular Gas Content and Scaling Relations in z 1-3 Massive, Main-sequence Star-forming Galaxies. In: Astrophysical Journal. 2013 ; Vol. 768, No. 1.
@article{c48e3ac6497346728b7f8f26adb90808,
title = "Phibss: Molecular Gas Content and Scaling Relations in z 1-3 Massive, Main-sequence Star-forming Galaxies",
abstract = "We present PHIBSS, the IRAM Plateau de Bure high-z blue sequence CO 3-2 survey of the molecular gas properties in massive, main-sequence star-forming galaxies (SFGs) near the cosmic star formation peak. PHIBSS provides 52 CO detections in two redshift slices at z ~ 1.2 and 2.2, with log(M *(M ☉)) ≥ 10.4 and log(SFR(M ☉/yr)) ≥ 1.5. Including a correction for the incomplete coverage of the M* -SFR plane, and adopting a {"}Galactic{"} value for the CO-H2 conversion factor, we infer average gas fractions of ~0.33 at z ~ 1.2 and ~0.47 at z ~ 2.2. Gas fractions drop with stellar mass, in agreement with cosmological simulations including strong star formation feedback. Most of the z ~ 1-3 SFGs are rotationally supported turbulent disks. The sizes of CO and UV/optical emission are comparable. The molecular-gas-star-formation relation for the z = 1-3 SFGs is near-linear, with a ~0.7 Gyr gas depletion timescale; changes in depletion time are only a secondary effect. Since this timescale is much less than the Hubble time in all SFGs between z ~ 0 and 2, fresh gas must be supplied with a fairly high duty cycle over several billion years. At given z and M *, gas fractions correlate strongly with the specific star formation rate (sSFR). The variation of sSFR between z ~ 0 and 3 is mainly controlled by the fraction of baryonic mass that resides in cold gas.",
keywords = "galaxies: evolution, galaxies: high redshift, galaxies ISM, ISM: molecules",
author = "Tacconi, {L. J.} and R. Neri and R. Genzel and F. Combes and A. Bolatto and Cooper, {M. C.} and S. Wuyts and F. Bournaud and A. Burkert and J. Comerford and P. Cox and M. Davis and {F{\"o}rster Schreiber}, {N. M.} and S. Garc{\'i}a-Burillo and J. Gracia-Carpio and D. Lutz and T. Naab and S. Newman and A. Omont and A. Saintonge and {Shapiro Griffin}, K. and A. Shapley and A. Sternberg and B. Weiner",
doi = "10.1088/0004-637X/768/1/74",
journal = "Astrophysical Journal",
publisher = "IOP Publishing",
T1 - Phibss: Molecular Gas Content and Scaling Relations in z 1-3 Massive, Main-sequence Star-forming Galaxies
AU - Tacconi, L. J.
AU - Neri, R.
AU - Genzel, R.
AU - Combes, F.
AU - Bolatto, A.
AU - Cooper, M. C.
AU - Wuyts, S.
AU - Bournaud, F.
AU - Burkert, A.
AU - Comerford, J.
AU - Cox, P.
AU - Davis, M.
AU - Förster Schreiber, N. M.
AU - García-Burillo, S.
AU - Gracia-Carpio, J.
AU - Lutz, D.
AU - Naab, T.
AU - Newman, S.
AU - Omont, A.
AU - Saintonge, A.
AU - Shapiro Griffin, K.
AU - Shapley, A.
AU - Sternberg, A.
AU - Weiner, B.
N2 - We present PHIBSS, the IRAM Plateau de Bure high-z blue sequence CO 3-2 survey of the molecular gas properties in massive, main-sequence star-forming galaxies (SFGs) near the cosmic star formation peak. PHIBSS provides 52 CO detections in two redshift slices at z ~ 1.2 and 2.2, with log(M *(M ☉)) ≥ 10.4 and log(SFR(M ☉/yr)) ≥ 1.5. Including a correction for the incomplete coverage of the M* -SFR plane, and adopting a "Galactic" value for the CO-H2 conversion factor, we infer average gas fractions of ~0.33 at z ~ 1.2 and ~0.47 at z ~ 2.2. Gas fractions drop with stellar mass, in agreement with cosmological simulations including strong star formation feedback. Most of the z ~ 1-3 SFGs are rotationally supported turbulent disks. The sizes of CO and UV/optical emission are comparable. The molecular-gas-star-formation relation for the z = 1-3 SFGs is near-linear, with a ~0.7 Gyr gas depletion timescale; changes in depletion time are only a secondary effect. Since this timescale is much less than the Hubble time in all SFGs between z ~ 0 and 2, fresh gas must be supplied with a fairly high duty cycle over several billion years. At given z and M *, gas fractions correlate strongly with the specific star formation rate (sSFR). The variation of sSFR between z ~ 0 and 3 is mainly controlled by the fraction of baryonic mass that resides in cold gas.
AB - We present PHIBSS, the IRAM Plateau de Bure high-z blue sequence CO 3-2 survey of the molecular gas properties in massive, main-sequence star-forming galaxies (SFGs) near the cosmic star formation peak. PHIBSS provides 52 CO detections in two redshift slices at z ~ 1.2 and 2.2, with log(M *(M ☉)) ≥ 10.4 and log(SFR(M ☉/yr)) ≥ 1.5. Including a correction for the incomplete coverage of the M* -SFR plane, and adopting a "Galactic" value for the CO-H2 conversion factor, we infer average gas fractions of ~0.33 at z ~ 1.2 and ~0.47 at z ~ 2.2. Gas fractions drop with stellar mass, in agreement with cosmological simulations including strong star formation feedback. Most of the z ~ 1-3 SFGs are rotationally supported turbulent disks. The sizes of CO and UV/optical emission are comparable. The molecular-gas-star-formation relation for the z = 1-3 SFGs is near-linear, with a ~0.7 Gyr gas depletion timescale; changes in depletion time are only a secondary effect. Since this timescale is much less than the Hubble time in all SFGs between z ~ 0 and 2, fresh gas must be supplied with a fairly high duty cycle over several billion years. At given z and M *, gas fractions correlate strongly with the specific star formation rate (sSFR). The variation of sSFR between z ~ 0 and 3 is mainly controlled by the fraction of baryonic mass that resides in cold gas.
KW - galaxies: evolution
KW - galaxies: high redshift
KW - galaxies ISM
KW - ISM: molecules
UR - http://iopscience.iop.org/article/10.1088/0004-637X/768/1/74/meta
U2 - 10.1088/0004-637X/768/1/74
DO - 10.1088/0004-637X/768/1/74
JO - Astrophysical Journal
JF - Astrophysical Journal


"it should be a car that you can drive across a ploughed field while it's loaded up with trays of eggs, without breaking the eggs". This idea touches upon something important to us all. It's about having a car that becomes part of the way we live. At Riversimple we have been busy designing that car. We think of it as a local car.Continue Reading..
At the beginning of November, Team Riversimple were to be found at the National Exhibition Centre in Birmingham.
Riversimple at NEC. Presentation by Richard Coltart, Programme Manager, bringing the new car to production.
The annual Advanced Engineering Show has acquired an international reputation, attracting and demonstrating the latest developments in engineering. We had Riversimple's Alpha Mk2 rolling chassis (the entire Hydrogen car minus external body shell) on show and it certainly attracted plenty of interest.
At present the design of the body shell is being kept under wraps, but from the point of view of the engineer it is the nuts and bolts of the interior that really fascinate.
This is the culmination of fifteen years development at Riversimple. Designing around hydrogen fuel cell technology has allowed us to re-invent the car for the modern world. We have four electric motors, one in each wheel and these motors are also the brakes – recovering over 50% of kinetic energy when braking. There are super-capacitors to store this energy and the recovered energy is fed back into the system to provide 80% of the power for acceleration. The primary power source is a relatively low powered hydrogen fuel cell ( 8.5 kW) housed in a beautifully constructed framework of lightweight composites.
Our overall design gives us a groundbreaking efficiency and range, many times better than inserting fuel cells into conventional, heavy, vehicles. This also means it will be agile and fun to drive, and with a massive feel good factor, as we strive towards zero cost for the environment.


text:
Q: python says "no module named nest" when it is in the $PATH import nest gives the 'no module named nest' error when it is in the $PATH, which means that there is a /opt/nest/lib/python2.7/site-packages: in my system $PATH. At this location there is a directory named nest and the structure inside the nest directory is looks like:

, where there is an __init__.py obviously. So why can't python find nest?
more information:
I am sure that I installed nest with python2.7, and run it with the same python2.7.

A: According to the docs, there are several ways to install python packages:

*

*using distutils - running python setup.py install installs the package to site-packages of your current distribution;

*passing --user to setup.py install installs module to ~/.local/lib/python2.7/site-packages on Unix, and this directory in under normal conditions always included in sys.path;

*passing --home=$HOME to setup.py install installs module under $HOME directory. This directory should be included to sys.path explicitly;

*modifying python search path:

you can do either
   import sys
   sys.path.append('/opt/nest/lib/python2.7/site-packages')

in the beginning of your script; or your can add
PYTHONPATH=/opt/nest/lib/python2.7/site-packages
export PYTHONPATH

in the end of your ~/.bash_profile file.
UPDATE:
Just tried to install nest and found that it comes in two flavours - 32bit (under /opt/nest/lib) and 64bit (under /opt/nest/lib64). You might have tried to use 32-bit python package with 64-bit python distribution. Try to change the string in ./zshrc to
PYTHONPATH=/opt/nest/lib64/python2.7/site-packages and see if it works. It works for me at least.

A: To set relevant environment variables correctly, NEST installs have a config that you can just source
source <installpath>/bin/nest_vars.sh

That sets the PATH and PYTHONPATH correctly and points NEST to the right directories for dynamically loaded content (modules, help pages, …)

redpajama_set_name: RedPajamaStackExchange


Are you wondering who Daniel Jovanov "Human Car Sounds" is? You're in the right place!
I am Daniel Jovanov, better known as "Human Car Sounds".
I live in Sydney, Australia but you've probably seen me all over youtube, facebook and instagram making car sounds!
My brother was always a car nut, this laid the foundations for my passion for anything with a motor!
What has making car sounds allowed you to achieve?
Doing live car sounds has allowed me to travel the world doing what i love, some personal highlights include traveling to Russia to film an advertisement, USA to appear at the prestigious SEMA car show and the Middle East to appear at private functions.
I'm assuming that because you're a rev head you drive a pretty cool car?
Your assumption would be correct! I've recently completed the first phase of modifications on my JZX80 Toyota Supra! You can follow the progress of this through my social media links!
Favorite car sound to make?
Easily the rotary! Who doesn't love a good brap!
Where can i find more Human Car Sounds content?
More content can be found via my YouTube, Instagram and Facebook.
Are you available for private functions and corporate events?
Of course! I love performing my car sounds, if you are interested in reaching out to me regarding any private functions or corporate events please contact me through the "Contact Us" form.


As in previous occasions in our conference, the Spanish Group of Fracture (GEF) will concede the following awards (see award rules in http://www.gef.es/web/concursos.asp).
When submitting the paper, the candidate must request to be considered to the award.
Recommended poster dimensions is DIN A1 size (59.4 cm width and 84.1 cm height). It should be taken into consideration that the panels are 2 m in width and 1m in height.
Send the picture in digital format to Prof. Jesús M. Alegre (jalegre@ubu.es) before March 27th. The quality of the picture should be adequate for printing in DIN A4 size. In any case, the author could bring the printed picture on paper and DIN A4 and give it to the organizers during the first day of the conference.
This award will be given for the first time in Sevilla's conference. Details can be downloaded from the link.
* Registrations after March 1st 2019 will have an increment of 75 euros.


text:
// Copyright (c) Microsoft Corporation. All rights reserved.
// Licensed under the MIT License.
// Code generated by Microsoft (R) AutoRest Code Generator.

package com.azure.resourcemanager.recoveryservicesbackup.implementation;

import com.azure.core.annotation.ExpectedResponses;
import com.azure.core.annotation.Get;
import com.azure.core.annotation.HeaderParam;
import com.azure.core.annotation.Headers;
import com.azure.core.annotation.Host;
import com.azure.core.annotation.HostParam;
import com.azure.core.annotation.PathParam;
import com.azure.core.annotation.QueryParam;
import com.azure.core.annotation.ReturnType;
import com.azure.core.annotation.ServiceInterface;
import com.azure.core.annotation.ServiceMethod;
import com.azure.core.annotation.UnexpectedResponseExceptionType;
import com.azure.core.http.rest.PagedFlux;
import com.azure.core.http.rest.PagedIterable;
import com.azure.core.http.rest.PagedResponse;
import com.azure.core.http.rest.PagedResponseBase;
import com.azure.core.http.rest.Response;
import com.azure.core.http.rest.RestProxy;
import com.azure.core.management.exception.ManagementException;
import com.azure.core.util.Context;
import com.azure.core.util.FluxUtil;
import com.azure.resourcemanager.recoveryservicesbackup.fluent.RecoveryPointsClient;
import com.azure.resourcemanager.recoveryservicesbackup.fluent.models.RecoveryPointResourceInner;
import com.azure.resourcemanager.recoveryservicesbackup.models.RecoveryPointResourceList;
import reactor.core.publisher.Mono;

/** An instance of this class provides access to all the operations defined in RecoveryPointsClient. */
public final class RecoveryPointsClientImpl implements RecoveryPointsClient {
    /** The proxy service used to perform REST calls. */
    private final RecoveryPointsService service;

    /** The service client containing this operation class. */
    private final RecoveryServicesBackupClientImpl client;

    /**
     * Initializes an instance of RecoveryPointsClientImpl.
     *
     * @param client the instance of the service client containing this operation class.
     */
    RecoveryPointsClientImpl(RecoveryServicesBackupClientImpl client) {
        this.service =
            RestProxy.create(RecoveryPointsService.class, client.getHttpPipeline(), client.getSerializerAdapter());
        this.client = client;
    }

    /**
     * The interface defining all the services for RecoveryServicesBackupClientRecoveryPoints to be used by the proxy
     * service to perform REST calls.
     */
    @Host("{$host}")
    @ServiceInterface(name = "RecoveryServicesBack")
    private interface RecoveryPointsService {
        @Headers({"Content-Type: application/json"})
        @Get(
            "/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.RecoveryServices"
                + "/vaults/{vaultName}/backupFabrics/{fabricName}/protectionContainers/{containerName}/protectedItems"
                + "/{protectedItemName}/recoveryPoints")
        @ExpectedResponses({200})
        @UnexpectedResponseExceptionType(ManagementException.class)
        Mono<Response<RecoveryPointResourceList>> list(
            @HostParam("$host") String endpoint,
            @QueryParam("api-version") String apiVersion,
            @PathParam("vaultName") String vaultName,
            @PathParam("resourceGroupName") String resourceGroupName,
            @PathParam("subscriptionId") String subscriptionId,
            @PathParam("fabricName") String fabricName,
            @PathParam("containerName") String containerName,
            @PathParam("protectedItemName") String protectedItemName,
            @QueryParam("$filter") String filter,
            @HeaderParam("Accept") String accept,
            Context context);

        @Headers({"Content-Type: application/json"})
        @Get(
            "/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.RecoveryServices"
                + "/vaults/{vaultName}/backupFabrics/{fabricName}/protectionContainers/{containerName}/protectedItems"
                + "/{protectedItemName}/recoveryPoints/{recoveryPointId}")
        @ExpectedResponses({200})
        @UnexpectedResponseExceptionType(ManagementException.class)
        Mono<Response<RecoveryPointResourceInner>> get(
            @HostParam("$host") String endpoint,
            @QueryParam("api-version") String apiVersion,
            @PathParam("vaultName") String vaultName,
            @PathParam("resourceGroupName") String resourceGroupName,
            @PathParam("subscriptionId") String subscriptionId,
            @PathParam("fabricName") String fabricName,
            @PathParam("containerName") String containerName,
            @PathParam("protectedItemName") String protectedItemName,
            @PathParam("recoveryPointId") String recoveryPointId,
            @HeaderParam("Accept") String accept,
            Context context);

        @Headers({"Content-Type: application/json"})
        @Get("{nextLink}")
        @ExpectedResponses({200})
        @UnexpectedResponseExceptionType(ManagementException.class)
        Mono<Response<RecoveryPointResourceList>> listNext(
            @PathParam(value = "nextLink", encoded = true) String nextLink,
            @HostParam("$host") String endpoint,
            @HeaderParam("Accept") String accept,
            Context context);
    }

    /**
     * Lists the backup copies for the backed up item.
     *
     * @param vaultName The name of the recovery services vault.
     * @param resourceGroupName The name of the resource group where the recovery services vault is present.
     * @param fabricName Fabric name associated with the backed up item.
     * @param containerName Container name associated with the backed up item.
     * @param protectedItemName Backed up item whose backup copies are to be fetched.
     * @param filter OData filter options.
     * @throws IllegalArgumentException thrown if parameters fail the validation.
     * @throws ManagementException thrown if the request is rejected by server.
     * @throws RuntimeException all other wrapped checked exceptions if the request fails to be sent.
     * @return list of RecoveryPoint resources along with {@link PagedResponse} on successful completion of {@link
     *     Mono}.
     */
    @ServiceMethod(returns = ReturnType.SINGLE)
    private Mono<PagedResponse<RecoveryPointResourceInner>> listSinglePageAsync(
        String vaultName,
        String resourceGroupName,
        String fabricName,
        String containerName,
        String protectedItemName,
        String filter) {
        if (this.client.getEndpoint() == null) {
            return Mono
                .error(
                    new IllegalArgumentException(
                        "Parameter this.client.getEndpoint() is required and cannot be null."));
        }
        if (vaultName == null) {
            return Mono.error(new IllegalArgumentException("Parameter vaultName is required and cannot be null."));
        }
        if (resourceGroupName == null) {
            return Mono
                .error(new IllegalArgumentException("Parameter resourceGroupName is required and cannot be null."));
        }
        if (this.client.getSubscriptionId() == null) {
            return Mono
                .error(
                    new IllegalArgumentException(
                        "Parameter this.client.getSubscriptionId() is required and cannot be null."));
        }
        if (fabricName == null) {
            return Mono.error(new IllegalArgumentException("Parameter fabricName is required and cannot be null."));
        }
        if (containerName == null) {
            return Mono.error(new IllegalArgumentException("Parameter containerName is required and cannot be null."));
        }
        if (protectedItemName == null) {
            return Mono
                .error(new IllegalArgumentException("Parameter protectedItemName is required and cannot be null."));
        }
        final String accept = "application/json";
        return FluxUtil
            .withContext(
                context ->
                    service
                        .list(
                            this.client.getEndpoint(),
                            this.client.getApiVersion(),
                            vaultName,
                            resourceGroupName,
                            this.client.getSubscriptionId(),
                            fabricName,
                            containerName,
                            protectedItemName,
                            filter,
                            accept,
                            context))
            .<PagedResponse<RecoveryPointResourceInner>>map(
                res ->
                    new PagedResponseBase<>(
                        res.getRequest(),
                        res.getStatusCode(),
                        res.getHeaders(),
                        res.getValue().value(),
                        res.getValue().nextLink(),
                        null))
            .contextWrite(context -> context.putAll(FluxUtil.toReactorContext(this.client.getContext()).readOnly()));
    }

    /**
     * Lists the backup copies for the backed up item.
     *
     * @param vaultName The name of the recovery services vault.
     * @param resourceGroupName The name of the resource group where the recovery services vault is present.
     * @param fabricName Fabric name associated with the backed up item.
     * @param containerName Container name associated with the backed up item.
     * @param protectedItemName Backed up item whose backup copies are to be fetched.
     * @param filter OData filter options.
     * @param context The context to associate with this operation.
     * @throws IllegalArgumentException thrown if parameters fail the validation.
     * @throws ManagementException thrown if the request is rejected by server.
     * @throws RuntimeException all other wrapped checked exceptions if the request fails to be sent.
     * @return list of RecoveryPoint resources along with {@link PagedResponse} on successful completion of {@link
     *     Mono}.
     */
    @ServiceMethod(returns = ReturnType.SINGLE)
    private Mono<PagedResponse<RecoveryPointResourceInner>> listSinglePageAsync(
        String vaultName,
        String resourceGroupName,
        String fabricName,
        String containerName,
        String protectedItemName,
        String filter,
        Context context) {
        if (this.client.getEndpoint() == null) {
            return Mono
                .error(
                    new IllegalArgumentException(
                        "Parameter this.client.getEndpoint() is required and cannot be null."));
        }
        if (vaultName == null) {
            return Mono.error(new IllegalArgumentException("Parameter vaultName is required and cannot be null."));
        }
        if (resourceGroupName == null) {
            return Mono
                .error(new IllegalArgumentException("Parameter resourceGroupName is required and cannot be null."));
        }
        if (this.client.getSubscriptionId() == null) {
            return Mono
                .error(
                    new IllegalArgumentException(
                        "Parameter this.client.getSubscriptionId() is required and cannot be null."));
        }
        if (fabricName == null) {
            return Mono.error(new IllegalArgumentException("Parameter fabricName is required and cannot be null."));
        }
        if (containerName == null) {
            return Mono.error(new IllegalArgumentException("Parameter containerName is required and cannot be null."));
        }
        if (protectedItemName == null) {
            return Mono
                .error(new IllegalArgumentException("Parameter protectedItemName is required and cannot be null."));
        }
        final String accept = "application/json";
        context = this.client.mergeContext(context);
        return service
            .list(
                this.client.getEndpoint(),
                this.client.getApiVersion(),
                vaultName,
                resourceGroupName,
                this.client.getSubscriptionId(),
                fabricName,
                containerName,
                protectedItemName,
                filter,
                accept,
                context)
            .map(
                res ->
                    new PagedResponseBase<>(
                        res.getRequest(),
                        res.getStatusCode(),
                        res.getHeaders(),
                        res.getValue().value(),
                        res.getValue().nextLink(),
                        null));
    }

    /**
     * Lists the backup copies for the backed up item.
     *
     * @param vaultName The name of the recovery services vault.
     * @param resourceGroupName The name of the resource group where the recovery services vault is present.
     * @param fabricName Fabric name associated with the backed up item.
     * @param containerName Container name associated with the backed up item.
     * @param protectedItemName Backed up item whose backup copies are to be fetched.
     * @param filter OData filter options.
     * @throws IllegalArgumentException thrown if parameters fail the validation.
     * @throws ManagementException thrown if the request is rejected by server.
     * @throws RuntimeException all other wrapped checked exceptions if the request fails to be sent.
     * @return list of RecoveryPoint resources as paginated response with {@link PagedFlux}.
     */
    @ServiceMethod(returns = ReturnType.COLLECTION)
    private PagedFlux<RecoveryPointResourceInner> listAsync(
        String vaultName,
        String resourceGroupName,
        String fabricName,
        String containerName,
        String protectedItemName,
        String filter) {
        return new PagedFlux<>(
            () ->
                listSinglePageAsync(vaultName, resourceGroupName, fabricName, containerName, protectedItemName, filter),
            nextLink -> listNextSinglePageAsync(nextLink));
    }

    /**
     * Lists the backup copies for the backed up item.
     *
     * @param vaultName The name of the recovery services vault.
     * @param resourceGroupName The name of the resource group where the recovery services vault is present.
     * @param fabricName Fabric name associated with the backed up item.
     * @param containerName Container name associated with the backed up item.
     * @param protectedItemName Backed up item whose backup copies are to be fetched.
     * @throws IllegalArgumentException thrown if parameters fail the validation.
     * @throws ManagementException thrown if the request is rejected by server.
     * @throws RuntimeException all other wrapped checked exceptions if the request fails to be sent.
     * @return list of RecoveryPoint resources as paginated response with {@link PagedFlux}.
     */
    @ServiceMethod(returns = ReturnType.COLLECTION)
    private PagedFlux<RecoveryPointResourceInner> listAsync(
        String vaultName, String resourceGroupName, String fabricName, String containerName, String protectedItemName) {
        final String filter = null;
        return new PagedFlux<>(
            () ->
                listSinglePageAsync(vaultName, resourceGroupName, fabricName, containerName, protectedItemName, filter),
            nextLink -> listNextSinglePageAsync(nextLink));
    }

    /**
     * Lists the backup copies for the backed up item.
     *
     * @param vaultName The name of the recovery services vault.
     * @param resourceGroupName The name of the resource group where the recovery services vault is present.
     * @param fabricName Fabric name associated with the backed up item.
     * @param containerName Container name associated with the backed up item.
     * @param protectedItemName Backed up item whose backup copies are to be fetched.
     * @param filter OData filter options.
     * @param context The context to associate with this operation.
     * @throws IllegalArgumentException thrown if parameters fail the validation.
     * @throws ManagementException thrown if the request is rejected by server.
     * @throws RuntimeException all other wrapped checked exceptions if the request fails to be sent.
     * @return list of RecoveryPoint resources as paginated response with {@link PagedFlux}.
     */
    @ServiceMethod(returns = ReturnType.COLLECTION)
    private PagedFlux<RecoveryPointResourceInner> listAsync(
        String vaultName,
        String resourceGroupName,
        String fabricName,
        String containerName,
        String protectedItemName,
        String filter,
        Context context) {
        return new PagedFlux<>(
            () ->
                listSinglePageAsync(
                    vaultName, resourceGroupName, fabricName, containerName, protectedItemName, filter, context),
            nextLink -> listNextSinglePageAsync(nextLink, context));
    }

    /**
     * Lists the backup copies for the backed up item.
     *
     * @param vaultName The name of the recovery services vault.
     * @param resourceGroupName The name of the resource group where the recovery services vault is present.
     * @param fabricName Fabric name associated with the backed up item.
     * @param containerName Container name associated with the backed up item.
     * @param protectedItemName Backed up item whose backup copies are to be fetched.
     * @throws IllegalArgumentException thrown if parameters fail the validation.
     * @throws ManagementException thrown if the request is rejected by server.
     * @throws RuntimeException all other wrapped checked exceptions if the request fails to be sent.
     * @return list of RecoveryPoint resources as paginated response with {@link PagedIterable}.
     */
    @ServiceMethod(returns = ReturnType.COLLECTION)
    public PagedIterable<RecoveryPointResourceInner> list(
        String vaultName, String resourceGroupName, String fabricName, String containerName, String protectedItemName) {
        final String filter = null;
        return new PagedIterable<>(
            listAsync(vaultName, resourceGroupName, fabricName, containerName, protectedItemName, filter));
    }

    /**
     * Lists the backup copies for the backed up item.
     *
     * @param vaultName The name of the recovery services vault.
     * @param resourceGroupName The name of the resource group where the recovery services vault is present.
     * @param fabricName Fabric name associated with the backed up item.
     * @param containerName Container name associated with the backed up item.
     * @param protectedItemName Backed up item whose backup copies are to be fetched.
     * @param filter OData filter options.
     * @param context The context to associate with this operation.
     * @throws IllegalArgumentException thrown if parameters fail the validation.
     * @throws ManagementException thrown if the request is rejected by server.
     * @throws RuntimeException all other wrapped checked exceptions if the request fails to be sent.
     * @return list of RecoveryPoint resources as paginated response with {@link PagedIterable}.
     */
    @ServiceMethod(returns = ReturnType.COLLECTION)
    public PagedIterable<RecoveryPointResourceInner> list(
        String vaultName,
        String resourceGroupName,
        String fabricName,
        String containerName,
        String protectedItemName,
        String filter,
        Context context) {
        return new PagedIterable<>(
            listAsync(vaultName, resourceGroupName, fabricName, containerName, protectedItemName, filter, context));
    }

    /**
     * Provides the information of the backed up data identified using RecoveryPointID. This is an asynchronous
     * operation. To know the status of the operation, call the GetProtectedItemOperationResult API.
     *
     * @param vaultName The name of the recovery services vault.
     * @param resourceGroupName The name of the resource group where the recovery services vault is present.
     * @param fabricName Fabric name associated with backed up item.
     * @param containerName Container name associated with backed up item.
     * @param protectedItemName Backed up item name whose backup data needs to be fetched.
     * @param recoveryPointId RecoveryPointID represents the backed up data to be fetched.
     * @throws IllegalArgumentException thrown if parameters fail the validation.
     * @throws ManagementException thrown if the request is rejected by server.
     * @throws RuntimeException all other wrapped checked exceptions if the request fails to be sent.
     * @return base class for backup copies along with {@link Response} on successful completion of {@link Mono}.
     */
    @ServiceMethod(returns = ReturnType.SINGLE)
    private Mono<Response<RecoveryPointResourceInner>> getWithResponseAsync(
        String vaultName,
        String resourceGroupName,
        String fabricName,
        String containerName,
        String protectedItemName,
        String recoveryPointId) {
        if (this.client.getEndpoint() == null) {
            return Mono
                .error(
                    new IllegalArgumentException(
                        "Parameter this.client.getEndpoint() is required and cannot be null."));
        }
        if (vaultName == null) {
            return Mono.error(new IllegalArgumentException("Parameter vaultName is required and cannot be null."));
        }
        if (resourceGroupName == null) {
            return Mono
                .error(new IllegalArgumentException("Parameter resourceGroupName is required and cannot be null."));
        }
        if (this.client.getSubscriptionId() == null) {
            return Mono
                .error(
                    new IllegalArgumentException(
                        "Parameter this.client.getSubscriptionId() is required and cannot be null."));
        }
        if (fabricName == null) {
            return Mono.error(new IllegalArgumentException("Parameter fabricName is required and cannot be null."));
        }
        if (containerName == null) {
            return Mono.error(new IllegalArgumentException("Parameter containerName is required and cannot be null."));
        }
        if (protectedItemName == null) {
            return Mono
                .error(new IllegalArgumentException("Parameter protectedItemName is required and cannot be null."));
        }
        if (recoveryPointId == null) {
            return Mono
                .error(new IllegalArgumentException("Parameter recoveryPointId is required and cannot be null."));
        }
        final String accept = "application/json";
        return FluxUtil
            .withContext(
                context ->
                    service
                        .get(
                            this.client.getEndpoint(),
                            this.client.getApiVersion(),
                            vaultName,
                            resourceGroupName,
                            this.client.getSubscriptionId(),
                            fabricName,
                            containerName,
                            protectedItemName,
                            recoveryPointId,
                            accept,
                            context))
            .contextWrite(context -> context.putAll(FluxUtil.toReactorContext(this.client.getContext()).readOnly()));
    }

    /**
     * Provides the information of the backed up data identified using RecoveryPointID. This is an asynchronous
     * operation. To know the status of the operation, call the GetProtectedItemOperationResult API.
     *
     * @param vaultName The name of the recovery services vault.
     * @param resourceGroupName The name of the resource group where the recovery services vault is present.
     * @param fabricName Fabric name associated with backed up item.
     * @param containerName Container name associated with backed up item.
     * @param protectedItemName Backed up item name whose backup data needs to be fetched.
     * @param recoveryPointId RecoveryPointID represents the backed up data to be fetched.
     * @param context The context to associate with this operation.
     * @throws IllegalArgumentException thrown if parameters fail the validation.
     * @throws ManagementException thrown if the request is rejected by server.
     * @throws RuntimeException all other wrapped checked exceptions if the request fails to be sent.
     * @return base class for backup copies along with {@link Response} on successful completion of {@link Mono}.
     */
    @ServiceMethod(returns = ReturnType.SINGLE)
    private Mono<Response<RecoveryPointResourceInner>> getWithResponseAsync(
        String vaultName,
        String resourceGroupName,
        String fabricName,
        String containerName,
        String protectedItemName,
        String recoveryPointId,
        Context context) {
        if (this.client.getEndpoint() == null) {
            return Mono
                .error(
                    new IllegalArgumentException(
                        "Parameter this.client.getEndpoint() is required and cannot be null."));
        }
        if (vaultName == null) {
            return Mono.error(new IllegalArgumentException("Parameter vaultName is required and cannot be null."));
        }
        if (resourceGroupName == null) {
            return Mono
                .error(new IllegalArgumentException("Parameter resourceGroupName is required and cannot be null."));
        }
        if (this.client.getSubscriptionId() == null) {
            return Mono
                .error(
                    new IllegalArgumentException(
                        "Parameter this.client.getSubscriptionId() is required and cannot be null."));
        }
        if (fabricName == null) {
            return Mono.error(new IllegalArgumentException("Parameter fabricName is required and cannot be null."));
        }
        if (containerName == null) {
            return Mono.error(new IllegalArgumentException("Parameter containerName is required and cannot be null."));
        }
        if (protectedItemName == null) {
            return Mono
                .error(new IllegalArgumentException("Parameter protectedItemName is required and cannot be null."));
        }
        if (recoveryPointId == null) {
            return Mono
                .error(new IllegalArgumentException("Parameter recoveryPointId is required and cannot be null."));
        }
        final String accept = "application/json";
        context = this.client.mergeContext(context);
        return service
            .get(
                this.client.getEndpoint(),
                this.client.getApiVersion(),
                vaultName,
                resourceGroupName,
                this.client.getSubscriptionId(),
                fabricName,
                containerName,
                protectedItemName,
                recoveryPointId,
                accept,
                context);
    }

    /**
     * Provides the information of the backed up data identified using RecoveryPointID. This is an asynchronous
     * operation. To know the status of the operation, call the GetProtectedItemOperationResult API.
     *
     * @param vaultName The name of the recovery services vault.
     * @param resourceGroupName The name of the resource group where the recovery services vault is present.
     * @param fabricName Fabric name associated with backed up item.
     * @param containerName Container name associated with backed up item.
     * @param protectedItemName Backed up item name whose backup data needs to be fetched.
     * @param recoveryPointId RecoveryPointID represents the backed up data to be fetched.
     * @throws IllegalArgumentException thrown if parameters fail the validation.
     * @throws ManagementException thrown if the request is rejected by server.
     * @throws RuntimeException all other wrapped checked exceptions if the request fails to be sent.
     * @return base class for backup copies on successful completion of {@link Mono}.
     */
    @ServiceMethod(returns = ReturnType.SINGLE)
    private Mono<RecoveryPointResourceInner> getAsync(
        String vaultName,
        String resourceGroupName,
        String fabricName,
        String containerName,
        String protectedItemName,
        String recoveryPointId) {
        return getWithResponseAsync(
                vaultName, resourceGroupName, fabricName, containerName, protectedItemName, recoveryPointId)
            .flatMap(res -> Mono.justOrEmpty(res.getValue()));
    }

    /**
     * Provides the information of the backed up data identified using RecoveryPointID. This is an asynchronous
     * operation. To know the status of the operation, call the GetProtectedItemOperationResult API.
     *
     * @param vaultName The name of the recovery services vault.
     * @param resourceGroupName The name of the resource group where the recovery services vault is present.
     * @param fabricName Fabric name associated with backed up item.
     * @param containerName Container name associated with backed up item.
     * @param protectedItemName Backed up item name whose backup data needs to be fetched.
     * @param recoveryPointId RecoveryPointID represents the backed up data to be fetched.
     * @param context The context to associate with this operation.
     * @throws IllegalArgumentException thrown if parameters fail the validation.
     * @throws ManagementException thrown if the request is rejected by server.
     * @throws RuntimeException all other wrapped checked exceptions if the request fails to be sent.
     * @return base class for backup copies along with {@link Response}.
     */
    @ServiceMethod(returns = ReturnType.SINGLE)
    public Response<RecoveryPointResourceInner> getWithResponse(
        String vaultName,
        String resourceGroupName,
        String fabricName,
        String containerName,
        String protectedItemName,
        String recoveryPointId,
        Context context) {
        return getWithResponseAsync(
                vaultName, resourceGroupName, fabricName, containerName, protectedItemName, recoveryPointId, context)
            .block();
    }

    /**
     * Provides the information of the backed up data identified using RecoveryPointID. This is an asynchronous
     * operation. To know the status of the operation, call the GetProtectedItemOperationResult API.
     *
     * @param vaultName The name of the recovery services vault.
     * @param resourceGroupName The name of the resource group where the recovery services vault is present.
     * @param fabricName Fabric name associated with backed up item.
     * @param containerName Container name associated with backed up item.
     * @param protectedItemName Backed up item name whose backup data needs to be fetched.
     * @param recoveryPointId RecoveryPointID represents the backed up data to be fetched.
     * @throws IllegalArgumentException thrown if parameters fail the validation.
     * @throws ManagementException thrown if the request is rejected by server.
     * @throws RuntimeException all other wrapped checked exceptions if the request fails to be sent.
     * @return base class for backup copies.
     */
    @ServiceMethod(returns = ReturnType.SINGLE)
    public RecoveryPointResourceInner get(
        String vaultName,
        String resourceGroupName,
        String fabricName,
        String containerName,
        String protectedItemName,
        String recoveryPointId) {
        return getWithResponse(
                vaultName,
                resourceGroupName,
                fabricName,
                containerName,
                protectedItemName,
                recoveryPointId,
                Context.NONE)
            .getValue();
    }

    /**
     * Get the next page of items.
     *
     * @param nextLink The URL to get the next list of items
     *     <p>The nextLink parameter.
     * @throws IllegalArgumentException thrown if parameters fail the validation.
     * @throws ManagementException thrown if the request is rejected by server.
     * @throws RuntimeException all other wrapped checked exceptions if the request fails to be sent.
     * @return list of RecoveryPoint resources along with {@link PagedResponse} on successful completion of {@link
     *     Mono}.
     */
    @ServiceMethod(returns = ReturnType.SINGLE)
    private Mono<PagedResponse<RecoveryPointResourceInner>> listNextSinglePageAsync(String nextLink) {
        if (nextLink == null) {
            return Mono.error(new IllegalArgumentException("Parameter nextLink is required and cannot be null."));
        }
        if (this.client.getEndpoint() == null) {
            return Mono
                .error(
                    new IllegalArgumentException(
                        "Parameter this.client.getEndpoint() is required and cannot be null."));
        }
        final String accept = "application/json";
        return FluxUtil
            .withContext(context -> service.listNext(nextLink, this.client.getEndpoint(), accept, context))
            .<PagedResponse<RecoveryPointResourceInner>>map(
                res ->
                    new PagedResponseBase<>(
                        res.getRequest(),
                        res.getStatusCode(),
                        res.getHeaders(),
                        res.getValue().value(),
                        res.getValue().nextLink(),
                        null))
            .contextWrite(context -> context.putAll(FluxUtil.toReactorContext(this.client.getContext()).readOnly()));
    }

    /**
     * Get the next page of items.
     *
     * @param nextLink The URL to get the next list of items
     *     <p>The nextLink parameter.
     * @param context The context to associate with this operation.
     * @throws IllegalArgumentException thrown if parameters fail the validation.
     * @throws ManagementException thrown if the request is rejected by server.
     * @throws RuntimeException all other wrapped checked exceptions if the request fails to be sent.
     * @return list of RecoveryPoint resources along with {@link PagedResponse} on successful completion of {@link
     *     Mono}.
     */
    @ServiceMethod(returns = ReturnType.SINGLE)
    private Mono<PagedResponse<RecoveryPointResourceInner>> listNextSinglePageAsync(String nextLink, Context context) {
        if (nextLink == null) {
            return Mono.error(new IllegalArgumentException("Parameter nextLink is required and cannot be null."));
        }
        if (this.client.getEndpoint() == null) {
            return Mono
                .error(
                    new IllegalArgumentException(
                        "Parameter this.client.getEndpoint() is required and cannot be null."));
        }
        final String accept = "application/json";
        context = this.client.mergeContext(context);
        return service
            .listNext(nextLink, this.client.getEndpoint(), accept, context)
            .map(
                res ->
                    new PagedResponseBase<>(
                        res.getRequest(),
                        res.getStatusCode(),
                        res.getHeaders(),
                        res.getValue().value(),
                        res.getValue().nextLink(),
                        null));
    }
}