Here are two series which were included in PAGES 2017 - both from Pakistan (from about same latitude as bristlecone pines.) One went up in late 20th, one went down. Guess which one was selected into PAGES 2019. Cherry-picking by climatists has gone well beyond being a joke.
2/ here's another example from PAGES2K Asian network: two juniper (JUSP) sites at different elevations in Bagrot Valley, Pakistan. One had upspike at very end, the other had decline. No points for guessing which is in PAGES2019.
3/ another contradiction: in the SW US at near-identical latitude, lower boundary trees said to be precipitation proxies, while upper boundary (higher altitude) more temperature related. Even at upper boundary, very dry in US and validity as temperature proxy questionable.
4/ from 229 Asia tree ring sites in PAGES 2019 (already screened), PAGES 2019 selected 47 sites according to criteria which accentuated 20th century increase. More sites from each of Mongolia and Pakistan than either Russia or China
5/ of 8 Russian tree ring series in PAGES 2019, 7 (!?!) come from exactly the same site: Ust Koksa Hill, Altai (ring width, early width, late width, max density, min density, late density, early density). Site at tricorner of Russia, Kazakh and Mongolia. Other site EAST of Japan.
6/ the Briffa troika of Russian tree ring sites (Yamal, Taimyr and the bodged version of Polar Urals) are used in PAGES2019 Arctic network, rather than Asia network.
7/ here's another puzzling and potentially serious PAGES 2019 problem -one which also impacts PAGES 2017 and PAGES 2013. I spot checked tree ring series with highest 2005 values - two over 4.4 SD units - paki033 and indo005. Note that a couple of authors over-represented.
most extreme (over 5 SD units in 2005) was paki033, a PIGE series from Pakistan (35 30N; 74 45E). It is used in PAGES 2013, PAGES 2017 and PAGES 2019. PAGES version has dramatic upspike, since 1991 and especially since 2002.
measurement data is at NOAA . Examining the underlying data, there are some issues. Usually, tree ring specialists require 10+ cores for valid chronology (exceptionally 5+ cores). paki033 doesn’t have 5 cores until 1776, only 2 cores as late as 1762. www1.ncdc.noaa.gov/pub/data/paleo…
but there's something MUCH worse. paki033 chronology NOT archived, only measurements. I calculated chronology using standard technique. Totally different result: no huge late upspike. Instead long decline with modest late recovery. ??!?? @onturenio, you should look at this
@onturenio I had similar problem when I tried to replicate chronology for INDO005: instead of the dramatic upspike of PAGES2K series, I obtained only a minor recovery from long decline.
@onturenio The Asian tree ring series in PAGES2017 were identical to the Asia tree ring data in PAGES 2013. To my knowledge, the PAGES 2013 chronologies had not been previously published in a technical publication, instead appearing first in PAGES 2013.
@onturenio I've triple checked the calculations. While the versions differ dramatically, they also clearly come from the same data (due to high frequency similarity). Where did PAGES2K chronologies for paki033 and indo005 come from? How were they calculated?
@onturenio this doesn't impact ALL the series. Chronology for nearby paki027 site is easily replicated. Not sure what's going on with the two series shown above. They emerged from spot check of high closers, not cherry pick from examining numerous series.
@onturenio here's another PAGES tree ring chronology PAKI021 - where PAGES version goes up, while chronology calculated from underlying measurement data at NOAA goes down.
Kalash Valley Bumburet - PIGE. Used in P13, P17 and P19.
@onturenio one more Pakistan tree ring series (PAKI036) in which PAGES version is more HS than chronology calculated from underlying data according to standard method. Less dramatic difference than others, but still very distinct.
@onturenio the NOAA archive for this measurement data gives PAGES2K (2013) as academic citation -NOT a specialist publication of the Pakistan tree ring data.
• • •
Missing some Tweet in this thread? You can try to
force a refresh
Some readers have probably noticed that Microsoft has recently become one of the leading retailers of lurid allegations about "Russian influence operations targeting U.S. elections".
What is being overlooked is the lead author of the Microsoft articles is none other than Clint Watts, the founder (fpri.org/news/2017/08/f…) of the infamous Hamilton 68 dashboard, which was exposed by @mtaibbi in #TwitterFiles 15 (x.com/mtaibbi/status…) as the "next great media fraud".
Taibbi comprehensively exposed the total sham of the Hamilton 68 dashboard. Nonetheless, Clint Watts, the main proponent of the sham Hamilton 68 dashboard, has risen to a more lucrative and more prominent platform at Microsoft, where he continues to propagate the same warmonging claims as he has for more than a decade.
less well known is that Watts also had a curious role in the original Russiagate hoax. Christopher Steele had met Kathleen Kavalec, a senior State Department official on October 11, 2016, where he spun an even more lurid fantasy than the "dossier" itself, adding in Sussmann's false Alfa Bank hoax and naming Millian as a supposed source (notwithstanding his supposed reluctance to identify sources because of "danger".) Kavalec later met with Bruce Ohr, who became Steele's conduit to FBI after November 1, 2016.
Kavalec read Watts' lurid November 6, 2016 article entitled "Trolling for Trump" and, after meeting with Ohr et al on Nov 21, 2016, called Watts in for a meeting on December 7, 2016. warontherocks.com/2016/11/trolli…
Kavalec was so impressed with Watts that she sent a copy of "Trolling for Trump" to Victoria Nuland and other high-level State Department officials including Daniel Fried, John Heffern, Athena Katsoulos, Naz Durakoglu, Jonathan Cohen, Bridget Brink, Eric Green, Christopher Robinson, Conrad Tribble. Earlier in 2016, Brink and Nuland had been involved in the Biden/State Department putsch to remove Shokin as Ukrainian Prosecutor General.
Clint Watts' "Trolling for Trump" article warontherocks.com/2016/11/trolli…, which had so enthralled senior State Department official Kavalec and her associates, said that their interest in "trolls" had arisen as follows: "When experts published content criticizing the Russian-supported Bashar al Assad regime, organized hordes of trolls would appear to attack the authors on Twitter and Facebook."
So who were the "experts" whose feelings had been hurt by online criticism? It turned out to be January 2014 article foreignaffairs.com/articles/syria… co-authored by Watts himself entitled "The Good and Bad of Ahrar al-Sham: An al Qaeda–Linked Group Worth Befriending."
At the time of Watts' article, ISIS was still very new. It was written in the same month as Obama had called ISIS the "jayvee". At the time, U.S. (through separate CIA and DoD operations) and Gulf States allies were funneling cash and weapons to jihadis of every persuasion as the Obama administration attempted to implement its regime change coup in Syria.
But despite Beltway support for arming Al Qaeda and its allies (including Ahrar al-Sham as advocated by Clint Watts), the larger public has never entirely understood the higher purpose supposedly served by arming Al Qaeda and its allies to carry out regime change in Syria. Mostly, they find it hard to believe that U.S. would carry out such an iniquitous policy. So Watts ought to have expected some blowback to his advocacy of arming AlQaeda allies, but instead, Watts blamed "Russia" for online criticism, ultimately falsely accusing simple opponents of US allying with AlQaeda allies as Russian agents or dupes.
actually, the lesson from Helene is the opposite from that being promoted.
In 1933, the Tennessee Valley Authority was given the mandate for flood control in the valley of the Tennessee River and its tributaries. Over the next 40 years, they built 49 dams, which, for the most part, accomplished their goal. Whereas floods in the Tennessee were once catastrophic, younger people are mostly unaware of them.
The French Broad River (Asheville) is an upstream tributary where flood control dams weren't constructed due to local opposition.
Rather than the devastation of Hurricane Helene on Asheville illustrating the effect of climate change, the success of the flood control dams in other sectors of the Tennessee Valley illustrates the success of the TVA flood control program where it is implemented.
Hurricane Helene did not show the effect of climate change, but what happens to settlements in Tennessee Valley tributaries under "natural" flooding (i.e. where flood control dams have been rejected.)
I should add that, in its first 40 years, the TVA built 49 flood control dams, of which 29 were power-generating. In the subsequent 50 years, TVA built 0 flood control dams,
However, in the 1980s, they established the Carbon Dioxide Information Centre (CDIAC) under their nuclear division, which sponsored much influential climate research, including the CRU temperature data (Phil Jones) and Michael Mann's fellowship from which Mann et al 1998 derived.
In 1990, the parents of Crowdstrike's Dmitri Alperovich moved from Russia to Chattanooga, Tennessee, where his father was a TVA nuclear engineer. Dmitri moved to Tennessee a few years later.
One can't help but wonder whether TVA's original mandate for flood control got lost in the executive offices, attracted by more glamorous issues, such as climate change research.
If so, one could reasonably say that a factor in the seeming abandonment of TVA efforts to complete its original flood control mandate (e.g. to French Broad River which inundated Asheville) was partly attributable to diversion of TVA interest to climate change research, as opposed to its mandate of flood control.
another thought. As soon as the point is made, it is obvious that flood control dams have reduced flooding. Not just in Appalachia. I've looked at long data for water levels in Great Lakes and the amount of fluctuation (flooding) after dams installed is much reduced.
And yet my recollection of public reporting of climate is that weather extremes, including flooding, is getting worse. But in areas with flood control dams, it obviously //isn't// getting worse than before. It's better. Note to self: check IPCC reports for their specific findings on flooding.
as readers are aware, @walkafyre has a long-term project of decoding the Mueller investigation through the laborious project of identifying the interviewees underneath the redactions. Some of the identifications are so ingenious that it's fun. Yesterday was an interesting example, which I'll narrate since it's interesting. (There are many other equally interesting examples.) It is the identification of the interviewee of Bates number B2997, interviewed on Aug 15, 2018 (302 filed on Dec 17, 2018). The 302 was published in volume 11 (page 92) - online at walkafyre's website here:
The 302 has 6 pages. The last 4 pages are totally redacted of information. All identifying information has been redacted from the first two pages except for the presence of Mueller attorney Aaron Zelinsky. Take a look.
And yet from this meagre information, walkafyre has made a firm identification of the interviewee.
first step. The 302s are in non-proportional font (Courier) and characters can be counted. Last name has 8 characters and praenomen has 9-10 characters.
second step. B2995 previously identified as Ali, Hesham and B3005 previously identified as Bartholomew, Vanessa. 302s are //locally// in alpha order, thus pinning surname to alpha range Ali to Bar.
third step. the interviewee (LN8) interacts with a LN9 frequently.
fourth. the interview was in summer 2018 with Zelinsky in attendance. This indicates that interview was connected to Roger Stone.
fifth, LN9 has given money to "the ___". Probably "the PAC". Public data on Roger Stone's PAC shows that the largest contributor (by far) was John Powers Middleton (9-character last name.)
So the interviewee is a LN8 in alpha range Ali-Bar with some sort of regular connection to Middleton. Walkafyre had this figured out a long time ago, but was stuck.fec.gov/data/receipts/…
a few days ago, @walkafyre took a look at documents related to a sordid lawsuit between Middleton and Roy Lee, an estranged associate. Case number shown below. One of the motions demanded deposition of "Alex Anderson", a Middleton employee. Alexander Anderson had previously made a deposition in support of Middleton.
As a coup de grace, one of the production requests in the pleadings was for "all communications related to Middleton's relationship with Roger Stone".
The redacted interviewee the August 15, 2018 grand jury notice was convincingly Middleton's employee Alexander Anderson.
in 2019 and 2020, there was a huge amount of interest in the Strzok-Page texts, but almost no attention was paid to the fact that the texts had been heavily "curated" before reaching the public and that some key topics were missing.
One of the key topics that was missing from the Strzok-Page texts (as curated) was any mention of the interview of Steele's Primary Sub-Source in late January 2017. Given that the FBI had insisted on inclusion of Steele dossier allegations in the Intelligence Community Assessment dated January 6, 2017, this was a central FBI issue at the time and the lack of any reference in the Strzok-Page texts as originally presented is noteworthy.
Readers may recall that the very first tranche of Strzok-Page texts, released in Feb 2018, contained a long gap from mid-December 2017 to mid-May 2018 - from the ICA to appointment of Mueller. This is the very period in which the Crossfire investigation metastasized into the lawfare that undermined the incoming administration. The fact that this period was separately missing from both Strzok and Lisa Page has never been adequately explained. As an aside, it seems odd that the FBI can retrieve emails and texts from targets, but not from their own employees.
Subsequently, a tranche of texts from the missing period was released, but these were also heavily curated and contained no texts that relate to the Primary Subsource.
However, from an an exhibit in the Flynn case , we //KNOW// that, in the late evening of January 13, 2017, Strzok and Page texted about the Primary Subsource, less than two weeks prior to the interview (which began on January 24, 2017). The message wasn't interpretable in real time, but we (Hans Mahncke) were subsequently able to connect it to the Danchenko interview via the reference to the "Womble" law firm, with which Danchenko's lawyer, Mark Schamel, was then associated. We also learned that Schamel was friends with and namedropped Lisa Monaco.
But other than this single excerpt from the Flynn exhibits, I haven't located anything in any of the other Strzok texts than can be plausibly connected to the critical interviews of the Primary Subsource.
I think that there are some Strzok emails from Jan 19 and Jan 22, 2017 that may refer to the pending Primary Subsource interview, that I'll discuss next.
One useful thing that the Weaponization Committee could do would be to publish a complete and unexpurgated set of Strzok-Page texts. Given the interest created by the highly expurgated version, one wonders what an expurgated and unbowdlerized version might yield.courtlistener.com/docket/6234142…
In the volume of Strzok emails released on October 31, 2019, there was an almost entirely redacted thread dated January 19 and January 22, 2017, a couple of days before the Primary Subsource interview on January 24, 2017, which look to me like they have a good chance of relating to the PSS interview.
The thread began with an email from FBI Office of General Council (OGC) - Sally Anne Moyer or Kevin Clinesmith - to Strzok and a CD subordinate, with a very short subject line.
We know that the PSS interview was lawyered up and carried out under a sweetheart queen-for-a-day deal that was usually only available to highly placed Democrats (Huma Abedin, Cheryl Mills etc.) So involvement of OGC in negotiation of the PSS interview is expected.
at 6:47 pm on Thursday, Jan 19, 2017, Strzok's CD subordinate wrote back that "here's what we have to decide ASAP". The issue is totally redacted, naturally. (This is one day before inauguration.)
in April 2022, Mark Steyn, on his GB News show
,
commented on recently released UK COVID data, claiming "the third booster shots so zealously promoted by the British state, and its groupthink media has failed, and in fact exposed you to significantly greater risk of infection, hospitalization and death."
Steyn showed images of five tables from official statistical publications to support his claims.
In April 2023, Ofcom, which, in addition to its ordinary regulatory role, had taken a special interest in vaccine advocacy, ruled that Steyn's "presentation of UK Health Security Agency data
and their use to draw conclusions materially misled the audience. In breach of Rule 2.2 of the Broadcasting Code" - a very damaging finding that Steyn has appealed.
I haven't followed this case. However, as it happens, I had taken an interest in UK COVID data about 3 months earlier, as it was one of the few jurisdictions that published case and hospitalization rates by vaccination status.
Also, to refresh readers on the contemporary context, early 2022 was the period in which COVID lockdowns and overall alarm began to decline.
At the time, I observed that the UK data showed that the case rate for triple vax was //higher// than among unvax. Three months later, Steyn (as discussed below) made a similar claim, for which he was censured.
Although the UK authorities conspicuously refrained from including this result in their summary or conclusions, they were obviously aware of the conundrum, since their publication included a curious disclaimer by UK authorities that actual case data "should not be used" to estimate vaccine effectiveness. I pointed this odd disclaimer out in this earlier thread, also noting that health authorities in Ontario and elsewhere had previously used such data to promote vaccine uptake and that the reasoning behind this disclaimer needed to be closely examined and parsed.
All of these issues turned up later in the Ofcom decision re Steyn.
Ofcom ruled that Steyn's presentation was "materially misleading" because (1) he failed to take account of "fundamental biases" in age structure of vax and unvax groups i.e. unvax group was skewed younger, vax group skewed older; and (2) he failed to include the disclaimer that "This raw data should not be used to estimate vaccine effectiveness as the data does not take into account inherent biases present such as differences in risk, behaviour and testing in the vaccinated and unvaccinated populations”.steynonline.com/mark-steyn-sho… ofcom.org.uk/__data/assets/…
in this thread, I'll re-examine Steyn's analysis. I've transcribed all the numbers in the tables and done further calculations to check his claims.
First, case rates. Steyn first showed an important table showing the population by 5-year age group and vax status, observing that the total population of triply vax (boosted) was approximately equal to the population of unboosted, observing that this facilitated comparison. Steyn: "Let's take a look at this, as you can see from a pool of 63 million down at the bottom there, 63 million, there are 32 million who are triple vaccinated. That leaves just under 31 million, who are either double single or unvaccinated. So we have two groups of similar size, 31, 32 million. So it's relatively easy to weigh the merits of the third shot upon Group A versus group B."
He then showed a table of cases by age group and vax status, pointing out that the total number of boosted cases was approximately double the number of unboosted cases: "So the triple vaccinated in March were responsible for just over a million COVID cases and everybody else 475,000 COVID cases. So the triple vaccinated are contracting COVID at approximately twice the rate of the double, single and unvaccinated. Got that? If you get the booster shot, you've got twice as high a chance of getting the COVID. In the United Kingdom, there's twice as many people with the third booster shot who got the COVID, as the people who never had the booster shot."
Ofcom purported to rebut Steyn's analysis as shown in excerpt below. They observed that proportion of unvax in younger age groups was much higher than in older age groups and that the "simple comparison between the two groups made by Mark Steyn failed to take into account these inherent biases".
However, Ofcom failed to show that there would be a different outcome in the more complex analysis in which age groups were allowed for.
As it turns out, in regard to case rates, Steyn's conclusions, if anything, under-stated the phenomenon, as shown next.
here is a thread from 2023 in which Eric Ciaramella's "yikes" is placed in a more detailed context.
In this thread, I suggested that the linkage was connected to Jan 21, 2016 meeting of Ukrainian prosecutors with State Dept officials, noting that Jamie Gusack (reporting to Bridget Brink) had distributing the first demand for Shokin's head (Nov 22 TPs)
as pointed out in that thread, Gusack (State Dept) had been coordinating with Ciaramella (NSC) prior to arrival of Ukr prosecutors in Jan 2016, referring to Shokin replacement.
State Dept cited "diamond prosecutors case" as big deal. But what happened to it next? A long story.
Bridget Brink, Jamie Gusack's boss, reported to Victoria Nuland. Brink was appointed Ambassador to Ukraine in April 2022. Unanimous approval by Senate in early days of war at the exact time that US and UK were sabotaging the peace deal negotiated in Istanbul