Expedition Navigation Software 
1 of 1- WoobaGooba
- Expert
Offline - Registered: 1/24/2016
- Posts: 101
NAM nest CONUS USA weirdness
Hi
Using NAM nest CONUS USA loaded by Exp from GC.
Loaded file name is not descriptive ... ARC?
Optimize result indicates GFS was used for the run.
Both those issues == confusion.
I've attached screen shots. Maybe not ... needs a URL.
Cheers
- WoobaGooba
- Expert
Offline
- Registered: 1/24/2016
- Posts: 101
Re: NAM nest CONUS USA weirdness
Links to screen captures.
[img]!Aogyrf3tyN8FjwleLhbHxwWtCBeQ[/img]
[img]!Aogyrf3tyN8FjwgUW47hlJrE64xu[/img]
- •
Thread Starter- Nick
- Moderator
Offline
- Registered: 9/16/2015
- Posts: 2,965
Re: NAM nest CONUS USA weirdness
It seems ok here. The default name in Exp will be "GC_NAM next USA_...."
- WoobaGooba
- Expert
Offline
- Registered: 1/24/2016
- Posts: 101
Re: NAM nest CONUS USA weirdness
Apologies for some confusion in my issue report.
Using the Expedition data loading and optimize functions...
Using NAM nest CONUS USA from GC, subsequent optimize result indicates Model: GFS
Using ECMWF 9km from GC, file is named GC_ARC ... (?), but optimize result does indicate Model: ECMWF
- •
Thread Starter- Nick
- Moderator
Offline
- Registered: 9/16/2015
- Posts: 2,965
Re: NAM nest CONUS USA weirdness
The model processes are coded inside the grib files.
It seems the NAM Nest is coded as being GFS. Will inform GC.
- WoobaGooba
- Expert
Offline
- Registered: 1/24/2016
- Posts: 101
Re: NAM nest CONUS USA weirdness
Thank you
- •
Thread Starter- pjl
- Expert
Offline
- From: Lake St. Clair, MI
- Registered: 11/09/2015
- Posts: 128
Re: NAM nest CONUS USA weirdness
Maybe a bit off topic, but this discussion is close to my query. Running weather scenarios prior to the Macs, and I'm getting a lot of "Expedition closing" incidents. Any comments? Are my settings off or is the old computer in need of a serious update? It's a three year old AMD chip HP that has been adequate until now.
Cheers and TIA for any comments.
pjl