Summary for GH #275
See below the table for a key. The table currently includes:
All files in the message_single_country directory
models/modules/.
Todo
Expand the table to include:
All (groups of) files modified by commits on the SSP_Dev_2023 branch of message_single_country.
All (groups of) files modified by commits on the ssp_dev branch of message_data.
Name |
m_data |
…country |
…models |
Pick |
PR/issue |
|---|---|---|---|---|---|
|
? |
? |
TODO |
? |
|
|
? |
? |
TODO |
? |
|
|
? |
? |
TODO |
? |
|
|
? |
? |
TODO |
? |
|
|
? |
? |
TODO |
? |
|
|
? |
? |
TODO |
? |
|
|
? |
? |
TODO |
? |
|
|
? |
? |
TODO |
? |
|
|
? |
? |
TODO |
? |
|
|
? |
? |
TODO |
? |
|
|
? |
? |
TODO |
? |
|
|
? |
? |
TODO |
? |
|
|
? |
? |
TODO |
? |
|
|
? |
? |
TODO |
? |
|
|
? |
? |
TODO |
? |
|
|
? |
? |
TODO |
? |
|
|
? |
? |
TODO |
? |
|
|
? |
? |
TODO |
? |
|
|
? |
? |
TODO |
? |
|
|
? |
? |
TODO |
? |
|
|
? |
? |
TODO |
? |
|
|
? |
? |
TODO |
? |
|
|
None |
message_data |
|||
|
? |
? |
TODO |
? |
|
|
? |
? |
TODO |
? |
|
|
? |
? |
TODO |
? |
|
|
? |
? |
TODO |
? |
How to use
Keep the list in alphabetical order.
In each row, enter:
- Name
A short name for the module, function, or collection of such.
- m_data
Link to one code or data file on the
ssp_devbranch ofmessage_data, if any. If there are multiple files, choose one.- …country
Link to one code or data file on the
SSP_Dev_2023branch ofmessage_single_country, if any. If there are multiple files, choose one. If the file is present in both message_data and message_single_country, these links should correspond in order to support diff of the two versions.- …models
Link to one code or data file on the
mainbranch ofmessage-ix-models, for instance if the item has already been migrated as a dependency of other code. If this migration has not happened yet, put “None”.- Pick
Either “m_data”, “m_single_country”, or “m-ix-models”, indicating which version of the code/data files will be preferred.
- PR/issue
Link to, at minimum, a message-ix-models pull request that adds or updates the item, or an issue gathering more info than appears in the table. Use the usual GitHub features to:
Track the assignees, review assignments, status, checklist items, etc. associated with the PR.
Cross-reference additional PRs that remove the corresponding files or code from message_data and/or message_single_country.