New URL for NEMO forge!   http://forge.nemo-ocean.eu

Since March 2022 along with NEMO 4.2 release, the code development moved to a self-hosted GitLab.
This present forge is now archived and remained online for history.
ticket/1328/review (diff) – NEMO

Changes between Version 1 and Version 2 of ticket/1328/review


Ignore:
Timestamp:
2014-10-13T12:41:52+02:00 (10 years ago)
Author:
avidard
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • ticket/1328/review

    v1 v2  
    44 
    55== For completion by the Sci/Tech/Code reviewer == 
    6 '''Reviewer:''' [ Enter your name here ] 
     6'''Reviewer:''' [ A. Vidard ] 
    77 
    88=== Ticket Details, Documentation and Code changes === 
    9 ||Do you understand the area of code being altered and the reasoning why it is being altered?||YES/NO|| 
    10 ||Do the proposed code changes correspond with the stated reason for the change?||YES/NO|| 
    11 ||Is the in-line documentation accurate and sufficient?||YES/NO|| 
    12 ||Do the code changes comply with NEMO coding standards?||YES/NO|| 
    13 ||Is the Ticket documented with sufficient detail for others to understand the impact of the change?||YES/NO|| 
    14 ||Does any corresponding external documentation require updating?||YES/NO|| 
    15 ||If yes, which docs and have the updates been drafted?||YES/NO|| 
    16 ||Are namelist changes required for this change?||YES/NO|| 
    17 ||If yes, have they been done?||YES/NO|| 
    18 ||Has a completed Ticket Summary template been appended to the ticket to aid code reviews||YES/NO|| 
    19 ||Does this summary correspond with your understanding of the full ticket?||YES/NO|| 
     9|| Do you understand the area of code being altered and the reasoning why it is being altered? || YES || 
     10|| Do the proposed code changes correspond with the stated reason for the change? || YES || 
     11|| Is the in-line documentation accurate and sufficient? || YES || 
     12|| Do the code changes comply with NEMO coding standards? || NO || 
     13|| Is the Ticket documented with sufficient detail for others to understand the impact of the change? || YES || 
     14|| Does any corresponding external documentation require updating? || YES || 
     15|| If yes, which docs and have the updates been drafted? || OBS/? || 
     16|| Are namelist changes required for this change? || YES || 
     17|| If yes, have they been done? || YES || 
     18|| Has a completed Ticket Summary template been appended to the ticket to aid code reviews || YES || 
     19|| Does this summary correspond with your understanding of the full ticket? || YES || 
    2020 
    2121Ticket, Documentation and Code comments 
     
    2424 
    2525=== Testing === 
    26 ||Has the NVTK and other jobs been tested with this change?||YES/NO|| 
    27 ||Have the required bit comparability tests been run?||YES/NO|| 
    28 ||Can this change be shown to have a null impact? (if option not selected)||YES/NO|| 
    29 ||If no, is reason for the change valid/understood?||YES/NO/NA|| 
    30 ||If no, ensure that the ticket details the impact this change will have on model configurations .||YES/NO/NA|| 
    31 ||Is this change expected to preserve all diagnostics?||YES/NO|| 
    32 ||If no, is reason for the change valid/understood?||YES/NO/NA|| 
    33 ||Are there significant changes in run time/memory?||YES/NO|| 
    34  
    35 Testing Comments 
    36  
    37 Add specific testing comments here 
    38  
    39 Add specific testing comments here 
     26see !https://forge.ipsl.jussieu.fr/nemo/wiki/ticket/1328 
    4027 
    4128=== Code Review === 
    42 ||Do the code changes comply with NEMO coding standards?||YES/NO|| 
    43 ||Are code changes consistent with the design of NEMO?||YES/NO|| 
    44 ||Is the code free of unwanted TABs?||YES/NO|| 
    45 ||Has the code been wholly (100%) produced by NEMO developers working on NEMO?||YES/NO|| 
    46 ||If no, ensure collaboration agreement has been added to the ticket keywords|||| 
     29|| Do the code changes comply with NEMO coding standards? || NO || 
     30|| Are code changes consistent with the design of NEMO? || YES || 
     31|| Is the code free of unwanted TABs? || YES || 
     32|| Has the code been wholly (100%) produced by NEMO developers working on NEMO? || NO || 
     33|| If no, ensure collaboration agreement has been added to the ticket keywords || 
    4734 
    4835Add specific code comments or suggested alterations here. 
    4936 
    5037=== Review Summary === 
    51 Add summary here 
     38There are some breaches to the NEMO coding norm, in the variable names. Actually they are quite common in the pre-existing OBS code. 
     39 
     40It is a bit of a shame that OBS is not able to use NEMO's standard IO library and has to use netcdf statements. Maybe some internal discussions about updating the IO library for coping with OBS needs would be beneficial. 
    5241 
    5342=== Approval for the trunk === 
    54 YES/NO 
     43YES 
    5544 
    5645The code reviewer may approve the change for the NEMO trunk when: