Yes, with several more to come.

Dublin ??? Dubuque ???

frank

Dubai Area outlined in pink on map.

Aha, thanks. Might work for the 2022 World Cup in Qatar as well ...

This question shouldn't need to be asked again by me as:

(a) I have downloaded geophi's region map, and

(b) I have written a script to generate an image of the region from the namelist file downloaded with the model, as below.



... which is the same as that identified by geophi, though Dubai is not exactly central!

It's possible that parts of that large area can/may affect the weather in Dubai, so it's included as a "area of interest".
The area that actually gets used in any one experiment can be varied to suit "current thinking".

I've had a look at some of the other areas, Europe (50 km) for example:

... or it makes more sense viewed from space:


I haven't got the CPDN regions quite right yet, though the CORDEX regions do work - no doubt it will become clear as more regions are processed.

However, I only have:

AFR50, ANZ50, DUB25, EU25, EU50, PNW25, SAS50

Other regions would be appreciated, a MEX50 or anything else you can think of. I just need the small download data Zip (e.g. wah2_eu25_a6vc_198812_12_385_010461237.zip) via Dropbox, e-mail etc. - PM me with instructions.

[Edit: Google Earth file replaced by satellite view, as KML renders as XML - on Edge, anyway.]

Part of the size may be to eliminate boundary effects, but I've sent an email to ask about the size.

Information is forthcoming, but I don't know when.
Some for now: Some of "our" regions are CORDEX, and some aren't.

And, to make sure we're "on the same page", this is the page that we should be on: WCRP CORDEX

As far as I can see, none of the CPDN regions matches any CORDEX region exactly. Sometimes the rotated pole matches (EU, ANZ) or almost matches (SAS50, CPDN=236.68 vs CORDEX=236.66 pole longitude, typo?) but the grid extent is always different. None of that matters, as I'm simply trying to understand the general areas out of interest and as a means of crudely explaining the run times.

I now have a MEX50, which I think completes the set ...

I now have a MEX50, which I think completes the set ...

Good luck. May all the zips upload for you.

---

BTW The upload Zip from a DUB25 is a whopping 67.5 MB (Zip #1 of mine, at any rate) - which for Mac users is going to require 13 x 67.5 MB = 877.5 MB, plus the restart Zip, to be uploaded at the end. [If you are a Mac user:] It might be prudent to suspend/quit/restart BOINC Manager at suitable points, which will cause any waiting Zips to be uploaded before the model completes.

Here is a gallery of region images as viewed from space (in order to give an area indication):















The boundary colours are intended to match the existing region map (supplied by geophi) plus the animation on the main site. However, EU50 doesn't appear to match any of the regions on the map; all the others do. Of course, regions might change for all sorts of reasons and I might have made an error.

Some new WAH2 models today for South America.

It looks like the new SAM50 model (at least on my machines and for the batch analysed) has a rather pessimistic GFLOPS estimate:

Region..Resolution..Months..GFLOPS........Normalised GFLOPS/sec
DUB.......25...............13..........3,327,828......0.92
EU.........25...............12..........1,903,330......0.85
EU.........25...............13..........2,061,502......0.86
MEX.......50...............12..........784,376.........0.86
MEX.......50...............13..........849,559.........0.88
MEX.......25...............13..........4,172,902......n/a
PNW......25...............16..........1,277,597.......n/a
PNW......25...............24..........1,915,068.......1.17
SAM......50...............13..........2,147,398.......1.68
SAS.......50...............13..........1,495,731.......1.08

[NB If all GFLOPS estimates were perfect for the machines and batches considered then the normalised GFLOPS/sec would be 1.00.]

Some new WAH2 models at 50 km resolution for Africa today. They cover the same area as for the HADAM3P example earlier.

The new WAH2 AFR50 model also seems to have a pessimistic GFLOPS estimate:

Region..Resolution..Months..GFLOPS........Normalised GFLOPS/sec
AFR.......50...............13..........1,924,645......1.62
DUB.......25...............13..........3,327,828......0.96
EU.........25...............12..........1,903,330......0.91
EU.........25...............13..........2,061,502......0.91
MEX.......50...............12..........784,376.........0.91
MEX.......50...............13..........849,559.........0.94
MEX.......25...............13..........4,172,902......n/a
PNW......25...............16..........1,277,597.......n/a
PNW......25...............24..........1,915,068.......1.22
PNW......25...............49..........n/a.................n/a
SAM......50...............13..........2,147,398.......1.67
SAS.......50...............13..........1,495,731.......1.14

In a mix of models, a model with a "normalised GFLOPS/sec" greater than 1.00 will finish earlier than expected.

The table has been updated with some more completed models, adding Windows runs to earlier Mac and Linux runs. There's also a new model configuration PNW25/49 that's come out but I haven't received any models of that type yet (and don't have the GFLOPS estimate - though the PNW series are usually scaled).

Hi Iain and everyone ... I'm now crunching two of the Weather At Home2 (wah2) 8.19

wah2_pnw25_c0eh_200312_49_452_010736499_1

does the _49_ signify 49 months and 49 Zip files?

just curiosity.

Weather At Home2 (wah2) 8.19

wah2_pnw25_c0eh_200312_49_452_010736499_1