@jkikstra @Jihoon @adrivinca @awais307 would appreciate some comment here on things like:

• how you use R code as part of workflows (e.g. do you run an entire script? Interactively? Call it from somewhere?)
• Which ones are used most heavily, or more likely to be of interest to others to (re)use.
• Whether the above ideas would be helpful/usable in your workflows.

@khaeru, thanks for creating this issue to start discussions - from a first look i think at least option 2 could be really useful, option 1 maybe too but i don't know enough to give a good judgement there.

Detailed input from my side will have to wait a bit until after I return from holidays (probably will only get to it around 14 January).

In general, I was thinking until data becomes public, in message_data I would want to try to select the most useful Rscripts from DLE packages and integrate them in a DLE workflow that uses rpy2.
For instance, I'm imagining that a "build" command could first run basic message, then use Rscripts to create a DLE scenario based on that, and then do a MESSAGE-DLE run after that.

More to follow in the new year.

In the nexus work, we have some R scripts that need to be run to process raw data into data then used by other python scripts.
Since these R scripts need to be run just once -and sometimes link to large spatial data on the P drive- we do not include or call them from any python script. A user could just run them to generate new scenario configurations (SSP, SDGs), but otherwise all the output data of those scripts are already included in the message_data/data folder.