Opened 11 months ago

Last modified 2 weeks ago

#2167 assigned Task

ENHANCE-04_AndrewC-reporting

Reported by: acc Owned by: acc
Priority: high Milestone: 2019 WP
Component: env Version: trunk
Severity: minor Keywords:
Cc: Review:
MP ready?:
Progress: Most of the basic functionality has been implemented post-merge (2018) and is already in both the trunk and release. See: wiki:2019WP/ENHANCE-04_AndrewC-reporting for details. There is more that can be done to improve and enhance options and the task is likely to be revisited before the next merge (2019). The key further development planned is to implement single-core read and broadcast for common, small-volume inputs (e.g: EMPave.dat, namelists etc.).

Description (last modified by acc)

Summary

Action ${ACTION_NAME} Subject
PI(S) Andrew Coward
Digest Investigate ways of improving the code's reporting facilities. Currently, errors away from the lead process are not fully reported and the ln_ctl mechanism produces an overwhelming volume of output for large processor counts. Options are needed to produce more selective output (either by output type or processor range). his is an un-started task from the 2018WP (formerly ROBUST-06_AndrewC-reporting) that has been carried forward to 2019.
Dependencies
Branch NEMO/branches/$YEAR/dev_r{REV}_{ACTION_NAME}
Previewer(s)
Reviewer(s)
Wiki wiki:2019WP/ENHANCE-04_AndrewC-reporting

Abstract

This section should be completed before starting to develop the code, in order to find agreement with the previewer(s) on the method beforehand.

Description

Describe the goal of development, and the methodology.
Add reference documents or publications if relevant.

Implementation

Describe flow chart of the changes in the code.
List the .F90 files and modules to be changed.
Detailed list of new variables (including namelists) to be defined, give for each the chosen name (following coding rules) and definition.

Reference manual and web pages updates

Using part 1 and 2, define the summary of changes to be done in reference manuals (tex files), guide (rst files) and in the content of web pages.

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.

Commit History (4)

ChangesetAuthorTimeChangeLog
11614acc2019-09-30T14:34:34+02:00

New development branch: 2019/dev_r11613_ENHANCE-04_namelists_as_internalfiles to try out improvements to namelist handling. See wiki:2019WP/ENHANCE-04_AndrewC-reporting/Internal_Namelists for the initial ideas. This work forms part of #2167

10575acc2019-01-24T17:10:21+01:00

sette_test-cases.sh changes after trunk update to implement finer control over the choice of text report files generated. See ticket: #2167

10573acc2019-01-24T16:40:58+01:00

sette.sh changes after trunk update to implement finer control over the choice of text report files generated. See ticket: #2167

10570acc2019-01-24T16:14:49+01:00

Trunk update to implement finer control over the choice of text report files generated. See ticket: #2167

Change History (9)

comment:1 Changed 9 months ago by nemo

  • Priority changed from low to high

comment:2 Changed 9 months ago by acc

  • Description modified (diff)
  • Status changed from new to assigned

comment:3 Changed 9 months ago by acc

In 10570:

Trunk update to implement finer control over the choice of text report files generated. See ticket: #2167

comment:4 Changed 9 months ago by acc

In 10573:

sette.sh changes after trunk update to implement finer control over the choice of text report files generated. See ticket: #2167

comment:5 Changed 9 months ago by acc

In 10575:

sette_test-cases.sh changes after trunk update to implement finer control over the choice of text report files generated. See ticket: #2167

comment:6 Changed 6 weeks ago by acc

  • Progress modified (diff)

comment:7 Changed 6 weeks ago by acc

  • Progress modified (diff)

comment:8 Changed 2 weeks ago by acc

In 11614:

New development branch: 2019/dev_r11613_ENHANCE-04_namelists_as_internalfiles to try out improvements to namelist handling. See wiki:2019WP/ENHANCE-04_AndrewC-reporting/Internal_Namelists for the initial ideas. This work forms part of #2167

comment:9 Changed 2 weeks ago by andmirek

Would it be possible to open namelist in read only mode? By default namelist is open in read/write, this apparently may have some implication on performance, especially with Lustre system and many processors reading at the same time.

Note: See TracTickets for help on using tickets.