Open khaeru opened 4 years ago
Postponing to after v3.0.
No one was assigned to do this by the feature freeze for v3.2.0, so we postpone to v3.3 (or later).
No one was assigned to do this by the feature freeze for v3.3.0, so we postpone to v3.4 (or later).
No one was assigned to do this for v3.4.0, so we postpone to v3.5 (or later).
No one was assigned to do this by the feature freeze for v3.5.0, so we postpone to v3.6 (or later).
Removing the milestone entirely. It can be re-added if/when the team decides to schedule/assign the work.
To complete the code added #223, address the point raised there by @gidden:
(To clarify: message_ix.macro code was transcribed from an R script. The unit conversions were carried into the Python code. This is undesirable since the code should operate with whichever units the user inputs.)
This can be resolved in one or more of the following ways:
TODO
s inline in message_ix.macro: read, parse, and follow the existing units in the Scenario being modified.