Rename ProcessProperties variables to consistent process_props naming#1175
Rename ProcessProperties variables to consistent process_props naming#1175
process_props naming#1175Conversation
|
Hi there, this is jenkins continuous integration... |
1 similar comment
|
Hi there, this is jenkins continuous integration... |
Rename all ProcessProperties variable names to `process_props`: - `processor_props` → `process_props` - `processor_procs` → `process_props` - `procs_props` → `process_props` - `run_properties` → `process_props` - `parallel_props` → `process_props` Rename functions for consistency with class name: - `get_processor_properties` → `get_process_properties` - `_get_processor_properties` → `_get_process_properties` - `get_processor_properties_for_run` → `get_process_properties_for_run` Fix error message typos: - "ProcessorProperties" → "ProcessProperties" Agent-Logs-Url: https://github.com/C2SM/icon4py/sessions/dde2809d-488a-4766-9cc1-cfb8aeedc7eb Co-authored-by: jcanton <5622559+jcanton@users.noreply.github.com>
process_props naming
|
@copilot what about the bonus task? "Bonus: consider if ProcessProperties is the same as Communicator?" |
The actual communication happens through So the separation is:
|
Perhaps needs some in-person discussion, but an MPI communicator also contains the rank and size (and it obviously is the communication handle), so I'm not quite convinced by this argument. I think the main reason to keep some sort of wrapper around the MPI communicator class is if we want some level of abstraction 1. to allow e.g. NCCL communicators in the future (I'm not sure we need this anytime soon, GHEX handles this internally and NCCL communicators will most of the time need to be derived from MPI communicators) or 2. to allow adding properties functionality that is not directly available in the MPI commnunicator class ( |
…sor_properties Agent-Logs-Url: https://github.com/C2SM/icon4py/sessions/55210dc7-c18e-46ad-abf8-eac0d97384a7 Co-authored-by: msimberg <42977+msimberg@users.noreply.github.com>
|
@copilot fix the conflicts with main. |
…sproperties-variables # Conflicts: # model/driver/tests/driver/fixtures.py # model/standalone_driver/tests/standalone_driver/fixtures.py Co-authored-by: msimberg <42977+msimberg@users.noreply.github.com>
Agent-Logs-Url: https://github.com/C2SM/icon4py/sessions/6b4a3f9b-3dcc-4afa-9989-ab4e54a7c358 Co-authored-by: msimberg <42977+msimberg@users.noreply.github.com>
|
|
||
|
|
||
| def get_processor_properties_for_run( | ||
| def get_process_properties_for_run( |
There was a problem hiding this comment.
Should this be get_process_props or get_process_properties? I'm fine with the current version.
There was a problem hiding this comment.
The current name get_process_properties matches the class name ProcessProperties, so it reads naturally. get_process_props would be an abbreviated form. Since you're fine with it, I'll leave it as-is.
Agent-Logs-Url: https://github.com/C2SM/icon4py/sessions/a5390647-a39e-4115-aa3c-5fd119678341 Co-authored-by: msimberg <42977+msimberg@users.noreply.github.com>
|
@copilot can you fix the formatting? The "ICON4Py Quality Assurance" check is currently failing. |
Agent-Logs-Url: https://github.com/C2SM/icon4py/sessions/1421024c-459e-4bc1-917e-81732d2f77d9 Co-authored-by: msimberg <42977+msimberg@users.noreply.github.com>
|
@copilot I think you made the formatting worse. Please fix the failing CI workflows. |
Agent-Logs-Url: https://github.com/C2SM/icon4py/sessions/13320c45-f902-4b06-963b-9902e1058623 Co-authored-by: msimberg <42977+msimberg@users.noreply.github.com>
Fixed in 68fdb96. The previous formatting commit used a newer ruff version (0.15.x) instead of the project-pinned 0.8.3 from Warning Firewall rules blocked me from connecting to one or more addresses (expand for details)I tried to connect to the following addresses, but was blocked by firewall rules:
If you need me to access, download, or install something from one of these locations, you can either:
|
|
I'll try to fix the remaining mess that copilot has left locally. I think this is 95% there, but needs a bit of care to get to 100%. |
|
cscs-ci run default |
|
cscs-ci run distributed |
|
@copilot take care of conflicts. |
…sproperties-variables # Conflicts: # tools/tests/tools/conftest.py Co-authored-by: msimberg <42977+msimberg@users.noreply.github.com>
|
cscs-ci run default |
Agent-Logs-Url: https://github.com/C2SM/icon4py/sessions/427256a2-a3b5-4f34-8b1e-2958c72cf2cb Co-authored-by: msimberg <42977+msimberg@users.noreply.github.com>
|
Mandatory Tests Please make sure you run these tests via comment before you merge!
Optional Tests To run benchmarks you can use:
To run tests and benchmarks with the DaCe backend you can use:
To run test levels ignored by the default test suite (mostly simple datatest for static fields computations) you can use:
For more detailed information please look at CI in the EXCLAIM universe. |
processor_props→process_props(~408 occurrences)run_properties→process_props(~35 occurrences)parallel_props→process_props(~11 occurrences)processor_procs→process_props(7 occurrences)procs_props→process_props(3 occurrences)props→process_propsin function parameters and variablesself._props→self._process_propsinhalo.pyget_processor_properties→get_process_properties, etc."Unknown ProcessorProperties type"→"Unknown ProcessProperties type""Processor properties"→"Process properties"GlobalReductions.props→GlobalReductions.process_propsbindings/tests/conftest.pyhadprocessor_propsregression — fixed)🔒 GitHub Advanced Security automatically protects Copilot coding agent pull requests. You can protect all pull requests by enabling Advanced Security for your repositories. Learn more about Advanced Security.