Data is currently at
https://data.giss.nasa.gov/gistemp/tabledata_v4/GLB.Ts+dSST.csv
or
https://data.giss.nasa.gov/gistemp/tabledata_v4/GLB.Ts+dSST.txt
(or such updated location for this Gistemp v4 LOTI data)
January 2024 might show as 124 in hundredths of a degree C, this is +1.24C above the 1951-1980 base period. If it shows as 1.22 then it is in degrees i.e. 1.22C. Same logic/interpretation as this will be applied.
If the version or base period changes then I will consult with traders over what is best way for any such change to have least effect on betting positions or consider N/A if it is unclear what the sensible least effect resolution should be.
Numbers expected to be displayed to hundredth of a degree. The extra digit used here is to ensure understanding that +1.20C resolves to an exceed 1.195C option.
Resolves per first update seen by me or posted as long, as there is no reason to think data shown is in error. If there is reason to think there may be an error then resolution will be delayed at least 24 hours. Minor later update should not cause a need to re-resolve.
🏅 Top traders
# | Name | Total profit |
---|---|---|
1 | Ṁ2,541 | |
2 | Ṁ218 | |
3 | Ṁ55 | |
4 | Ṁ40 | |
5 | Ṁ24 |
People are also trading
@aenews He made something unbelievable strange, but what about PM? As i know you didnt buy winning bracket at all
@ScottSupak Too lazy to check, but yeah unlike GISS there's no straightforward way to determine NOAA anomalies. So there's pretty wide variance, in general. Not surprising when some months are significantly different.
@gonnarekt The preliminary point for the last day of ERA5 keeps July at 16.678 C.
In my ERA5->LOTI model the bias between the datasets is corrected with an adjustment of -0.04 C to 16.637 C to convert to LOTI for July (corresponding to a LOTI unadjusted of 0.973 C).
The LOTI is then adjusted by own past prediction errors for a point prediction of 0.984 C.
@gonnarekt I'm running it now, finally, should be done in 40 mins or so.
For note, on the ERA5-> LOTI final data, I ended up with a final point prediction of 0.984 C after adjusting for own past prediction errors (unadjusted is 0.973 C).
edit: I setup a new python environment recently and it looks like something has gone wrong . Going to delete the old files and rerun.
edit2: third time's the charm... running again
@gonnarekt close but not quite... edit: since the release is on the 8th (and assuming they dont run it the morning of) there are only 4 more runs left.
ghcnm.v4.0.1.20250802:
99.278
@parhizj That’s ok I lost last month cause I predicted 1.05 but it came 1.03, but after all correction they posted it 1.05 0_o
For future reference they used the ghcnm.tavg.v4.0.1.20250805 run which means they ran it on Wednesday.
this time, the (unadjusted) error was large from my ERA5->LOTI point prediction (~0.053)
@Weatherman 🤷 There is the GHCN daily but this is quite a bit different from the GCHN monthly dataset, although I haven't actually calculated how much. Not much motivation for me when there is no corresponding daily ERSST data to use (are you going to correlate on only the LAND data, or use some other dataset as a proxy for ERSST?)
Beyond that there is only 2 days of ERA5 data left, whatever difference of opinion more likely has to remain in the ERA5->LOTI model used:
These are the residuals that I've recorded for my own past LOTI prediction errors once all of ERA5 data is in (most of it is within the range of what might be determined by what run of ghcnm they randomly use):
At some point I started recording an extra-decimal point once I started outputting my own gistemp data that doesn't round the data since the numbers were too small:
own_data_error_residuals = np.array([-0.02, 0.01, 0.03, 0.01, 0.02, 0.03, 0.0, -0.01, 1.360 - 1.339, 1.225 - 1.173, 1.073 - 1.069, 1.032 - 1.045])
The bias is only 0.01 C....
@parhizj ERA5 data still could be off quite significantly, especially in 2024 with strong ENSO effect (El nino). The average of the daily GHCN's should give an idea how the monthly GHCN ends up though. I once looked into this data but it is a bit difficult how to process it and deal with data issues. I find this ncep reanalysis data interesting to look in as well http://www.karstenhaustein.com/climate
@Weatherman ERA5 is a reanalysis so I don’t know whether being “off” is the right idea; maybe you mean with just different biases, uncertainty than gistemp (and its input datasets)? (This should be accounted for in the ERA5->LOTI model though). You could use either dataset for ground truth.