Fullpos

Contents

Fullpos#

AlgoComponents for the next generation of Fullpos runs (based on the 903 configuration).

class vortex.nwp.algo.fpserver.FullPosServer(*args, **kwargs)[source]#

Fullpos Server for geometry transforms & post-processing in IFS-like Models.

Input/Output files are labelled as follows:

  • Let INPUTFILE_0 denote an input file name (the user can choose whichever name she/he wants provided that the associated input’s section has the “ModelState” role).

  • For FA files: the corresponding output file will be NPUTFILE_0.domain.out where domain is the domain name chosen by the user in the namelist. If a Surfex output file is also created (it depends on the namelist) it will be named NPUTFILE_0.domain.sfx.out

  • For GRIB files: the corresponding output file will be NPUTFILE_0.domain.grib.out.

  • Some or all output files may be pre-positionned (data generated by the c903 will be appended on them). The corresponding section’s role needs to be “OutputGuess”. The local filename of the section, needs to match the expected output filename. In our exemple it would be NPUTFILE_0.domain.out.

Note:

To use this algocomponent, the c903’s server needs to be activated in the namelist (NFPSERVER != 0).

Note:

With the current IFS/Arpege code, in order for the output’s polling to work properly, an ECHFP whiteness file have to be incremented by the server, in each of the output directories.

Note:

Climatology files are not managed (only few sanity checks are performed). The user needs to name the input climatology file consistently with the c903’ namelist. For role=”InitialClim” sections, the filename should be something like Const.Clim.m[month]. For role=”TargetClim” sections the filename should be something like const.clim.[domain].m[month] where [domain] corresponds to the name of the output domain (as specified in the namelist file) and [month] corresponds to the month being dealt with (on 2 digits).

Interesting features:

  • Input files can be expected (for on the fly processing)

  • Input files are dealt with in arbitrary order depending on their availability (useful for ensemble processing).

  • Output files can be promised

Contents