We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Some table of strict variable name/location changes would benefit intermediate and above 5000 users quickly convert some examples to RS.
The text was updated successfully, but these errors were encountered:
In the form <parent-function>:<variable>:
<parent-function>:<variable>
NEKUSE:ux
codedFixedValueVelocity:bc->u
NEKUSE:uy
codedFixedValueVelocity:bc->v
NEKUSE:uz
codedFixedValueVelocity:bc->w
GEOM:ym1(i,1,1,1)
UDF_Setup:nrs->meshV->y[i]
ntot=SIZE:nelt*lx1*ly1*lz1
UDF_Setup:nrs->meshV->Nlocal
NEKNEK:valint(..., 1)
codedFixedValueVelocity:bc->uinterp
NEKNEK:valint(..., 2)
codedFixedValueVelocity:bc->vinterp
NEKNEK:valint(..., 3)
codedFixedValueVelocity:bc->winterp
ffx = <val>
platform->linAlg->fill(nrs->meshV->Nlocal, <val>, nrs->o_NLT + 0 * nrs->fieldOffset)
Sorry, something went wrong.
Difference in execution of multiple meshes combined, for Nek5000:
neknekb <components ...> <ranks...>
For Nekrs:
nekbmpi <session-file> <n-ranks>
@kzscisoft does this need looking at?
kzscisoft
No branches or pull requests
Some table of strict variable name/location changes would benefit intermediate and above 5000 users quickly convert some examples to RS.
The text was updated successfully, but these errors were encountered: