Wrong coordinates for U-velocity – in #10: INT2LM

in #10: INT2LM

Dear colleagues,
I have a problem with a nesting simulation cclm-to-cclm (13 km to 6.6 km). I have run the int2lm and become an error (see attached slurm-1071576.out). The error is ‘Wrong coordinates for U-velocity’. I didn’t see this error earlier. I have suggested thaint the problem is somewhere in coordinate system of coarse grid output, but I don’t know how to fix it. I have tried to add ‘lushift_in=.TRUE., lvshift_in=.TRUE.,’ to the INPUT , but result was the same (see attached slurm-1074010.out). Maybe, I didn’t prescribe something in coarse model output (attached INPUT _IO from the COSMO - CLM 13 km run).
Could you suggest something about this problem? Thank you!

  @vladimirplatonov in #ab33693

Dear colleagues,
I have a problem with a nesting simulation cclm-to-cclm (13 km to 6.6 km). I have run the int2lm and become an error (see attached slurm-1071576.out). The error is ‘Wrong coordinates for U-velocity’. I didn’t see this error earlier. I have suggested thaint the problem is somewhere in coordinate system of coarse grid output, but I don’t know how to fix it. I have tried to add ‘lushift_in=.TRUE., lvshift_in=.TRUE.,’ to the INPUT , but result was the same (see attached slurm-1074010.out). Maybe, I didn’t prescribe something in coarse model output (attached INPUT _IO from the COSMO - CLM 13 km run).
Could you suggest something about this problem? Thank you!

Wrong coordinates for U-velocity

Dear colleagues,
I have a problem with a nesting simulation cclm-to-cclm (13 km to 6.6 km). I have run the int2lm and become an error (see attached slurm-1071576.out). The error is ‘Wrong coordinates for U-velocity’. I didn’t see this error earlier. I have suggested thaint the problem is somewhere in coordinate system of coarse grid output, but I don’t know how to fix it. I have tried to add ‘lushift_in=.TRUE., lvshift_in=.TRUE.,’ to the INPUT , but result was the same (see attached slurm-1074010.out). Maybe, I didn’t prescribe something in coarse model output (attached INPUT _IO from the COSMO - CLM 13 km run).
Could you suggest something about this problem? Thank you!

View in channel

In the GRIBOUT namelist of CCLM for output files in directory out01 you set
luvmasspoint=.TRUE.,
This interpolates the U and V to mass points. For nesting a higher resolution CCLM U and V have to stay on the flux points.
Either re-run the 13km CCLM with
luvmasspoint=.FALSE.,
or just delete the luvmasspoint=.TRUE., line, since luvmasspoint=.FALSE., is the default.

  @burkhardtrockel in #e861a0c

In the GRIBOUT namelist of CCLM for output files in directory out01 you set
luvmasspoint=.TRUE.,
This interpolates the U and V to mass points. For nesting a higher resolution CCLM U and V have to stay on the flux points.
Either re-run the 13km CCLM with
luvmasspoint=.FALSE.,
or just delete the luvmasspoint=.TRUE., line, since luvmasspoint=.FALSE., is the default.

In the GRIBOUT namelist of CCLM for output files in directory out01 you set
luvmasspoint=.TRUE.,
This interpolates the U and V to mass points. For nesting a higher resolution CCLM U and V have to stay on the flux points.
Either re-run the 13km CCLM with
luvmasspoint=.FALSE.,
or just delete the luvmasspoint=.TRUE., line, since luvmasspoint=.FALSE., is the default.

So, can I make nesting simulation without re-run? Which parameters should I change in int2lm INPUT ? Sorry for the foolish question…

  @vladimirplatonov in #a844883

So, can I make nesting simulation without re-run? Which parameters should I change in int2lm INPUT ? Sorry for the foolish question…

So, can I make nesting simulation without re-run? Which parameters should I change in int2lm INPUT ? Sorry for the foolish question…

Hallo Vladimir,
I’m sorry, but I don’t know any int2lm namelist parameter which allows using u/v at masspoints in cosmo output for preparation of IBC s at higher resolution.
Burkhardt, did I oversee something?
Shall we contact Uli Schaettler?

If you do not have the computing time to resimulate everything, you have to interpolate u/v to the points at the boundaries of the grid boxes.
Additionally the dependencies and grid coordinates have to be corrected in the files.
Burkhardt, do you have a script for that? Me not.
The coordinates can be generated by producing one correct output file.
In this file you can see, which attributes need to be changed as well.

Regards, Andreas

  @andreaswill in #a30e63e

Hallo Vladimir,
I’m sorry, but I don’t know any int2lm namelist parameter which allows using u/v at masspoints in cosmo output for preparation of IBC s at higher resolution.
Burkhardt, did I oversee something?
Shall we contact Uli Schaettler?

If you do not have the computing time to resimulate everything, you have to interpolate u/v to the points at the boundaries of the grid boxes.
Additionally the dependencies and grid coordinates have to be corrected in the files.
Burkhardt, do you have a script for that? Me not.
The coordinates can be generated by producing one correct output file.
In this file you can see, which attributes need to be changed as well.

Regards, Andreas

Hallo Vladimir,
I’m sorry, but I don’t know any int2lm namelist parameter which allows using u/v at masspoints in cosmo output for preparation of IBC s at higher resolution.
Burkhardt, did I oversee something?
Shall we contact Uli Schaettler?

If you do not have the computing time to resimulate everything, you have to interpolate u/v to the points at the boundaries of the grid boxes.
Additionally the dependencies and grid coordinates have to be corrected in the files.
Burkhardt, do you have a script for that? Me not.
The coordinates can be generated by producing one correct output file.
In this file you can see, which attributes need to be changed as well.

Regards, Andreas