update documentation FAQ about setting resources and turning off output #1608
Conversation
|
I just realized I skipped MOM6, so I will add that. I need to check w/ Jiande about what Jun's document had written. |
doc/UsersGuide/source/FAQ.rst
Outdated
| * compute tasks = ``x layout * y layout * number of tiles`` | ||
| * quilt tasks = ``write_groups * write_tasks_per_group`` if ``quilting==.true.`` | ||
| In the UFS WM, each component's MPI task information, including the | ||
| starting task and end ending task numbers and the number of threads, |
There was a problem hiding this comment.
'starting task and end ending task numbers and the number of threads,'
extra 'end'
and I think instead of 'task numbers' it's better to say 'task ranks'
doc/UsersGuide/source/FAQ.rst
Outdated
| FV3 | ||
| ^^^ | ||
| FV3ATM consists of one or more forecast grid components and a write | ||
| grid component. |
There was a problem hiding this comment.
write grid components
doc/UsersGuide/source/FAQ.rst
Outdated
|
|
||
| total tasks = number of forecast tasks + number of write grid component tasks | ||
|
|
||
| If ESMF-managed threading is used, the total number of tasks for |
There was a problem hiding this comment.
the total number of PETs for
doc/UsersGuide/source/FAQ.rst
Outdated
| :: | ||
|
|
||
| ATM_petlist_bounds 0 total_tasks*number_of_threads-1 | ||
| ATM_omp_num_threads number_of_threads |
There was a problem hiding this comment.
Maybe it will be clearer if we use number_of_threads_amt? I see we have "number_of_threads" for atm/wave/cmeps, we may let user know what the number_of_threads could be different for each component.
|
@junwang-noaa @DusanJovic-NOAA I've made changes based on your feedback. I'm probably still mis-using the task/ranks terminology (I find the terms a bit squidgy). I'm happy to try to be more precise, but I'll need a little guidance if I haven't got it quite right. |
|
@DeniseWorthen : a question (may not related to this PR), under section are we still support nemsio ? |
|
@jiandewang No the UFS does not support nemsio files any more.
…On Mon, Feb 13, 2023 at 12:28 PM jiandewang ***@***.***> wrote:
@DeniseWorthen <https://github.com/DeniseWorthen> : a question (may not
related to this PR), under section
How do I select the file format for the model output (netCDF or NEMSIO)?
In your run directory, there is a file named model_configure. Change the
variable output_file to 'netcdf' or 'nemsio'
are we still support nemsio ?
—
Reply to this email directly, view it on GitHub
<#1608 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AI7D6TOURWFHWMMSMM57EUDWXJVNHANCNFSM6AAAAAAUYIGRWQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
then we can take this chance to remove that in the doc |
|
@DeniseWorthen I will ask @binli2337 to combine in this pr. You can directly create a pr to his branch. Can you update the branch? |
|
@jkbk2004 I've updated but will wait for @binli2337 to update before making a PR. |
|
sure! I will leave a note to Bin's pr. |
|
Combined with #1597; closing |
Description
Updates FAQ section of documentation to describe how to set resources for coupled model.
Top of commit queue on: TBD
Input data additions/changes
Anticipated changes to regression tests:
Subcomponents involved:
Combined with PR's (If Applicable):
Commit Queue Checklist:
Linked PR's and Issues:
Test build can be seen here
Testing Day Checklist:
Testing Log (for CM's):