Custom Query (3269 matches)


Show under each result:

Results (37 - 39 of 3269)

3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23
Ticket Resolution Summary Owner Reporter
#168 fixed 6 hourly FAMOUS output variables are separated into several ones jeff m.yoshioka@…

6 hourly FAMOUS output variables should have 120 time steps in a monthly output file like var(120). But each of those variables is actually stored in several different variables like var(60), var_1(30), var_2(26), var_3(3), and var_4(1). This is how it looks in a converted NetCDF file. In original files viewed with xconv the same variables are simply repeated and they have timesteps of 60, 30, …. This happened in the pj files of my job tcmis:

I wrote an IDL script to connect these variables into one and output a fixed NetCDF file, so I'm Ok with working with it for now. But this may be a problem when I run simulations where I will have to use many of these data. But before that this is not the way it should work. So I ask for a help for this issue.

Thanks. Masaru

#2217 fixed 60km run job problem um_support sam89

Hi Willie

I am trying to run a 60km grid spacing job (due to the resolution the Met Office saves the MOGREPS perturbation files) and i am having issues at the run stage. I am just trying to run it for 3 hours and then dump out and reconfigure to 25km but I can't get this initial 3 hour run to work.

???????????????????????????????????????????????????????????????????????????????? ???!!!???!!!???!!!???!!!???!!!???!!! ERROR ???!!!???!!!???!!!???!!!???!!!???!!!? ? Error in routine: mppio:buffin ? Error Code: 25 ? Error Message: Error in buffin errorCode= 0. len= 0 / 140800 ? Error generated from processor: 0 ? This run generated 0 warnings ???????????????????????????????????????????????????????????????????????????????? /projects/diamet/saclar/xnndf/bin/qsmaster: Failed in qsatmos in job xnndf

The job is xnndf

and the output file is xnndf000.xnndf.d17186.t054354.leave



#2234 answered 60km run job xnndf um_support sam89


I am trying to run a job at 60km resolution.

I am getting a segmentation fault right at the start of the run, what could be causing this? I cannot work it out from the .leave file. xnndf000.xnndf.d17208.t205930.leave



3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23
Note: See TracQuery for help on using queries.