Update names of items that were renamed due to the mudularization of the LIMES GAMS code #2
Conversation
…exists in one of ('any') the dimensions of var
- Add new variable names where read from gdx
p_taulength -> pm_taulength
v_cap -> vm_cap
c_emicappathscen -> cm_emicappathscen
v_emi -> vm_emi
q_emicappath1 -> q30_emicappath1
q_emicappath2 -> q30_emicappath2
p_emifac -> p30_emifac
v_pedem -> vm_pedem
There was a problem hiding this comment.
There is still one note that should probably be removed.
Also, isn't it problematic to have the new name after the old name in readGDX? (for instance having readGDX(name = c("p_taulength", "pm_taulength", ...) insteand of readGDX(name = c("pm_taulength", "p_taulength", ...) ? What would happen if the gdx has the two parameters/variables because of inheritance issue? Would it then select the old parameter/variable?
Didn't think about this. How can that happen? And if both parameters are present in the gdx, why is the new one then the better one? |
Yes, I cant do it today. Hopefully tomorrow. |
For the time that the older LIMES version is still being used, having the vm/pm/q30 in the first position might be problematic for the reporting if both names are in the GDX (but I do not think a new gdx would be used for runs in the older LIMES version). Otherwise, I would think the risk of an old GDX used with the new LIMES version to be higher. |
No description provided.