Nemo merge requestshttps://forge.nemo-ocean.eu/nemo/nemo/-/merge_requests2023-11-29T01:12:55Zhttps://forge.nemo-ocean.eu/nemo/nemo/-/merge_requests/94Draft: Resolve "reducing communications in dynspg_ts"2023-11-29T01:12:55ZClement RoussetDraft: Resolve "reducing communications in dynspg_ts"Closes #60Closes #60GarbageClement RoussetClement Roussethttps://forge.nemo-ocean.eu/nemo/nemo/-/merge_requests/259Draft: Remove nn_hls Task2023-06-16T13:52:33ZItalo EpicocoDraft: Remove nn_hls TaskCloses #196Closes #1962023 WPItalo EpicocoItalo Epicocohttps://forge.nemo-ocean.eu/nemo/nemo/-/merge_requests/258Draft: NEMO performance tool2023-06-16T13:52:19ZSilvia MocaveroDraft: NEMO performance tool#### Related Issue: #208
#### Tests
Once the development is done, the PI should complete the tests section below and after ask the reviewers to start their review.
This part should contain the detailed results of ~SETTE tests (restar...#### Related Issue: #208
#### Tests
Once the development is done, the PI should complete the tests section below and after ask the reviewers to start their review.
This part should contain the detailed results of ~SETTE tests (restartability and reproducibility for each of the reference configuration) and detailed results of restartability and reproducibility when the option is activated on specified configurations used for this test.
**Regular checks**
- [ ] Can this change be shown to produce expected impact (option activated)?
- [ ] Can this change be shown to have a null impact (option not activated)?
- [ ] Results of the required bit comparability tests been run: are there no differences when activating the development?
- [ ] If some differences appear, is reason for the change valid/understood?
- [ ] If some differences appear, is the impact as expected on model configurations?
- [ ] Is this change expected to preserve all diagnostics?
- [ ] If no, is reason for the change valid/understood?
- [ ] Are there significant changes in run time/memory?
#### 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).
**Assessments**
- [ ] Is the proposed methodology now implemented?
- [ ] Are the code changes in agreement with the flowchart defined at preview step?
- [ ] Are the code changes in agreement with list of routines and variables as proposed at preview step?
- [ ] If, not, are the discrepancies acceptable?
- [ ] Is the in-line documentation accurate and sufficient?
- [ ] Do the code changes comply with NEMO coding standards?
- [ ] Is the development documented with sufficient details for others to understand the impact of the change?
- [ ] Is the project ~doc (manual, guide, web, ...) now updated or completed following the proposed summary in preview section?2023 WPSilvia MocaveroSilvia Mocaverohttps://forge.nemo-ocean.eu/nemo/nemo/-/merge_requests/326Draft: Resolve "change default sette options for the 4.2 branch and add warni...2023-06-13T09:49:59ZSebastien MassonDraft: Resolve "change default sette options for the 4.2 branch and add warnings for options that should not be used"Closes #260Closes #260Tag 4.2.1Sebastien MassonSebastien Massonhttps://forge.nemo-ocean.eu/nemo/nemo/-/merge_requests/123Draft: Resolve "summer 2022 work- DYN/TRA halo cleanup and optimization"2022-09-23T09:02:18ZSibylle TecheneDraft: Resolve "summer 2022 work- DYN/TRA halo cleanup and optimization"Closes #80Closes #802022 WPSibylle TecheneSibylle Techenehttps://forge.nemo-ocean.eu/nemo/nemo/-/merge_requests/119Draft: Resolve "summer 2022 work- DYN halo cleanup"2022-09-16T17:45:06ZSibylle TecheneDraft: Resolve "summer 2022 work- DYN halo cleanup"Deal with halo and reduce local memory by using 2D temporary arrays instead of 3D temporary arrays
Closes #80Deal with halo and reduce local memory by using 2D temporary arrays instead of 3D temporary arrays
Closes #80GarbageSibylle TecheneSibylle Techenehttps://forge.nemo-ocean.eu/nemo/nemo/-/merge_requests/112Resolve "summer 2022 work- SBC halo cleanup"2022-09-16T17:44:47ZClement RoussetResolve "summer 2022 work- SBC halo cleanup"Closes #72Closes #72GarbageClement RoussetClement Roussethttps://forge.nemo-ocean.eu/nemo/nemo/-/merge_requests/102Resolve "stress on T-points"2022-09-16T17:44:12ZClement RoussetResolve "stress on T-points"#### Tests
Once the development is done, the PI should complete the tests section below and after ask the reviewers to start their review.
This part should contain the detailed results of ~SETTE tests (restartability and reproducibili...#### Tests
Once the development is done, the PI should complete the tests section below and after ask the reviewers to start their review.
This part should contain the detailed results of ~SETTE tests (restartability and reproducibility for each of the reference configuration) and detailed results of restartability and reproducibility when the option is activated on specified configurations used for this test.
**Regular checks**
- [ ] Can this change be shown to produce expected impact (option activated)?
- [ ] Can this change be shown to have a null impact (option not activated)?
- [ ] Results of the required bit comparability tests been run: are there no differences when activating the development?
- [ ] If some differences appear, is reason for the change valid/understood?
- [ ] If some differences appear, is the impact as expected on model configurations?
- [ ] Is this change expected to preserve all diagnostics?
- [ ] If no, is reason for the change valid/understood?
- [ ] Are there significant changes in run time/memory?
#### 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).
**Assessments**
- [ ] Is the proposed methodology now implemented?
- [ ] Are the code changes in agreement with the flowchart defined at preview step?
- [ ] Are the code changes in agreement with list of routines and variables as proposed at preview step?
- [ ] If, not, are the discrepancies acceptable?
- [ ] Is the in-line documentation accurate and sufficient?
- [ ] Do the code changes comply with NEMO coding standards?
- [ ] Is the development documented with sufficient details for others to understand the impact of the change?
- [ ] Is the project ~doc (manual, guide, web, ...) now updated or completed following the proposed summary in preview section?Garbage