MSimon,
Early days yet. A number of people I trust have looked at the data and think it has been manipulated.
The raw data has not been manipulated. D'Aleo and every site that talks about raw data manipulation needs to retract it, else they are spreading lies and disinformation.
The
adjustments to that raw data are based on peer reviewed suggestions. I am going to eventually get to reproducing those. If I have issues with them I will surely make note of it. But that's a ways down the line (software takes quite some time to make).
Note that I am not looking at any code whatsoever to reproduce the data sets. I am doing essentially a black box analysis with the data. I want to read the data and read the papers as to not be biased by the source code. This makes the job far harder to accomplish since it means my own interpretation of how a given thing should be done. e.g, my software will have options to round .5 to even and up and away from zero.
You are qualified to refute the charge. Gather your troops and do a study.
In due time, but first I must have references to show people how the raw data is separate from climate science (because it comes from meteorologists as opposed to climatologists), so that any further analysis is bolstered by the understanding that I'm not cooking the data nor anyone else.
It may turn out that I of course blow a cover on the whole thing, but I am finding that unlikely.
You have already found things you are not happy with. So I'm not yet convinced the charge of manipulation is in error.
The charge was not manipulation of data, the charge was manipulation of *raw* data. That is a major allegation. They're obviously working with the data, but they are doing so under the guise of analysis. The question for you then should become whether or not the operations they take on the data are suitable. Globally GHCN claims homogeneity attempts make little difference to the data, but that they show up more so on local levels. We'll test that, too.
There's so much that can be tested, but no one seems to be doing it. You wanted an open source method, you got one. But I guarantee you that I will look at the data critically. The rounding thing only proves that. Rounding half up stood out to me because as I'm writing the software to reproduce USHCN/GHCN from NCDC data, that is a software tactic I would never utilize. I was taught to round to even or to add a random number and round that. We'll see if it makes a difference, I'm not a statistician, so I don't know. This is where my software engineering skills come in, because I just do what I know is right, and I may not even be sure why it is right. I admit I hate statistics.
We already know of one example. (the manipulations done to create the hockey stick) so I'd say it is up to you to prove your case.
I don't understand why you keep calling scientific analysis manipulation.
In noise reduction you're manipulating the data, are you not? Using basic sound scientific principles, right?
If you do I will change my mind. And announce it.
I know you will, but I'm not really doing it for you, it's just a spare time thing for my own understanding. Plus I've not written code in awhile and I need the practice.
And one of the cabal said in the e-mails he was not giving the data to McIntyre just so he could show errors.
There's a difference between software and programs. Software must be effectively bug free, or at least, good enough so that the end user doesn't know or care. Programs, however, just have to run, and just have to perform the job they are supposed to do.
Programs have far more bugs, in that vein. My parsing software will certainly break if the wrong CSV format is introduced, for example. So you work as you go with relative trial and error.
This is why I am using ML rather than C, to help reduce to an extent the errors that will assuredly exist.
And indication that he knew of errors. Or even manipulation.
It was eventually released, and there was no hubhub over it. I personally wouldn't want to release my personal code for my personal projects because it is 1) embarrassing, and 2) buggy, with lots of hacks here and there to fix random bugs. The fact that I am going to release this code into the open will force me to do the exact opposite, make the code clean, and make sure it is bugfree. This adds many hours to the production time.
But I'm not going to take the word of the Hide The Decline cabal for any past or future work.
I do hope that I can use their papers at least.