E-mail Archive

2010.08.09: CNRM-CM3 climate data (from Jens Heinke)
You may have noticed that for each climate variable of CNRM-CM3 there are two versions of year 2000 files available on the website: One in the 20C3M folder and one in each of the scenario folders (SRESA2, SRESB1). According to the CNRM-CM3 simulation protocol the SRES A2 and B1 simulations start from year 1999 of the 20C3M simulation. Hence, year 2000 from 20c3m should be used when conjoining 20c3m and scenario runs. Despite this fact we (Ingjerd, Stefan, Jens) have decided to use year 2000 of the 20C3M simulation which should then be followed by year 2001 of the scenario simulations. This has been done in order to be cosistent with the WaterMIP simulation protocol and the other GCMs where year 2000 is considered as belonging to the control run. The README file has been updated accordingly and all year 2000 files of the scenario runs have been deleted from the ftp site. By the way, for those of you who require LWnet I have uploaded this variable for WFD for the 1901 - 1957 period to the FTP site. The values have been derived in the same way as for the 1958 - 2001 period.

2010.08.09: Bias corrected data, Tmax/Tmin (from Jan Haerter)
For those of you using the daily maximum and minimum temperatures of the bias corrected model data I would like to point out a possible obstacle when feeding the data into hydrological or other impact models: Due to the interpolation routine (that makes smooth transitions between the monthly correction factors) there is a small number of cases where the corrected T_max<T_mean, where T_max is the daily maximum of the corrected data, and T_mean is the daily mean. In these cases, the value of T_max can become slightly less than T_mean (on the order of <1K). This is not noticeable in all practical cases, including those that we tested before releasing the bias correction algorithm or the data. However, if your hydrological model makes the assumption T_max>=T_mean>=T_min, then this could lead to confusion or crashes. If this has occurred, please let me know! To fix any such problems, it is suitable to just include a statement in your code saying if Tmax < Tmean then Tmax = Tmean. If Tmin > Tmean then Tmin = Tmean. For those of you that don't use Tmax or Tmin or whose hydrological models aren't sensitive to this condition, this is not important of course. 

2010.07.30: WATCH daily disaggregator (from Graham Weedon)
The WATCH daily disaggregator code has been released. This allows creation of realistic subdaily data from the daily averages of the forcing variables from the 1960-2100 GCM runs. The code is available from the IIASA ftp server from the WFD_code directory within the WATCH_Forcing_Data section.

2010.06.03: WATCH forcing data on ftp site (from WATCH Programme Office)
The WATCH forcing data has been separated out from the rest of the WATCH material on the FTP site at IIASA. This should make it more straightforward for those needing to only download the forcing data. The folder this is located in has its own password (sorry for the extra password, but the aim is to make it clearer).

2010.02.05: FTP server 
The ftp server at IIASA is now available, and should be used when uploading files. The forcing files can also be found on the IIASA ftp server. Note that data is stored in separate places, and hence you may need to use several login names and passwords.

2009.07.30: WaterMIP: WATCH forcing data available (from Graham Weedon)
In her absence I have been asked by Ingjerd to let you know that the final variables (Rainf & Snowf) have been updated by Workblock 1 members and are now available for 1980-1999 on the WATCH Workblock1 ftp site. Thank you for your patience while we tackled a variety of important issues.

Please note that the README text file has been corrected and updated: the flux forcing variable values (precipitation and radiation) indicate average flux over the time interval FOLLOWING the timestamp (e.g. for 3-hour Rainf the 06:00:00 values cover 06:00:00 to 08:59:59).

WaterMIP will be concerned with GPCC version of the precipitation data rather than the CRU version. For those running models requiring sub-daily forcing data the "Interpolator" code will be made available shortly and we will contact the relevant groups when this happens.

Good luck with your model runs.