| Version 6 (modified by andmirek, 7 years ago) (diff) |
|---|
Met_Office-Mirek_XIOSread
The PI is responsible to closely follow the progress of the action, and especially to contact NEMO project manager if the delay on preview (or review) are longer than the 2 weeks expected.
Help
The action has to be detailed briefly in the 'Summary' section for later inclusion in other pages.
Edit the 'Summary' section as with an ordinary wiki page.
- Italic formatting shows the default values or help.
- Set specific TracLinks (development ticket and branch).
Out of this, the rest of the page can be edited on-line inside the form fields considering the following color code given hereafter.
| PI(S) | Previewer(s) | Reviewer(s) |
|---|
Record your modifications for the section you have edited by clicking on the corresponding button at the end of the section with 'Save ...' button. Just above, the log record will be updated.
The informations inside the form fields and this wiki page itself are stored in 2 separate databases.
As a consequence, there is absolutely no risk to make any modification in the page itself as long as you don't rename the page or modify the source code of {{{#!TracForm ... }}} processors.
Summary
| Action | Met_Office-Mirek_XIOSread |
| PI(S) | Miroslaw Andrejczuk (Mirek) |
Digest |
As the number of cores in NEMO increases parallel reading of single netcdf files (e.g. restarts, forcing, observations) is becoming increasingly slow. |
| Dependencies | XIOS development. Currently the number of NEMO CPUs which can be used when reading data via XIOS is limited to 3700 |
| Target | Major |
| Trac Ticket | #1953 and #1962 |
| SVN branch | [source:/branches/2017/dev_r8600_xios_read_write_v2 |
| Previewer(s) | Names |
| Reviewer(s) | Names |
| Status | Postponed |
| Link | ExtractUrl(.)? |
Abstract
This section should be completed before starting to develop the code, in order to find agreement on the method beforehand.
Once the PI has completed this section, he should send a mail to the previewer(s) asking them to preview the work within two weeks.
Preview
Since the preview step must be completed before the PI starts the coding, the previewer(s) answers are expected to be completed within the two weeks after the PI has sent his request.
For each question, an iterative process should take place between PI and previewer(s) in order to reach a "YES" answer for each of the following questions.
Once all "YES" have been reached, the PI can start the development into his development branch.
Tests
Once the development is done, the PI should complete this section below and ask the reviewers to start their review in the lower section.
Review
A successful review is needed to schedule the merge of this development into the future NEMO release during next Merge Party (usually in November).
Once review is successful, the development must be scheduled for merge during next Merge Party Meeting.
