Opened 5 years ago

Closed 5 years ago

#1745 closed help (answered)

output at selected locations

Reported by: ggxmy Owned by: willie
Component: UMUI Keywords: time series
Cc: pringle, gmann Platform: ARCHER
UM Version: 8.4


Dear CMS,

We were thinking to request STASH outputs of vertical profiles at ~200 locations using time series profile, but I noticed that in UMUI the number of Timeseries domains is limited to 100. Is it possible to somehow increase this limit, by including a hand edit or a FCM branch, for example?

My latest job is teafk if necessary. In this job I included STASH requests at 16 station locations.


Change History (8)

comment:1 Changed 5 years ago by ggxmy

still needing help…

comment:2 Changed 5 years ago by willie

Hi Masaru,

Could you let me know which STASH item you are trying to output and with what Domain Profile (in job teafk).


comment:3 Changed 5 years ago by willie

  • Owner changed from um_support to willie
  • Status changed from new to accepted

comment:4 Changed 5 years ago by ggxmy

Hi Willie

I'm currently requesting 3 hourly vertical profiles (85 levels) of 2-362 and 363, and hourly profiles of 34-101~126 and 38-440, 478, 479. However, this may be changed.


comment:5 Changed 5 years ago by willie

Hi Masaru,

The limit on the number of time series domains in a profile is hardwired in the UMUI, so there is no hand edit possible. Would it be possible to output the entire fields?


comment:6 Changed 5 years ago by ggxmy

Hi Willie,

We have now selected 64 locations to request vertical profiles, so the limit of 100 in UMUI is not a problem any more. However, in #1771, Simon says there is a limit in number of time series outputs and we are exceeding that by a factor of 100! (But I'm not sure if he is totally correct because my previous job ran OK with ¼ of time series outputs, which still exceeded the limit by factor of 25. The results appear OK as well.)

Because we are going to submit an ensemble of over 200 simulations, outputting 3-D fields at a high temporal resolution will in turn be limited by the disk space. So we are now discussing internally what we should do. Maybe I should reduce the number of time series outputs and try running short simulations to find out the *real* maximum. If you come up with any other idea please suggest it.


comment:7 Changed 5 years ago by ggxmy

  • priority changed from highest to low

After having done some experiments, it now seems that a job crashes including requests of time series output at 32 locations. This is true including much smaller numbers of diagnostics or vertical levels.

However, a job runs OK including output request at 28 locations. The numbers of diagnostics and vertical levels or time resolution do not seem to matter.

All that seems to matter is the number of locations at which time series outputs are requested, and the limit should be between 28 and 32. That's my conclusion, at least with the version of the model we are using and our model settings.


comment:8 Changed 5 years ago by willie

  • Resolution set to answered
  • Status changed from accepted to closed
Note: See TracTickets for help on using tickets.