<![CDATA[IEA-ETSAP Forum - Suggestions]]> https://forum.iea-etsap.org/ Fri, 23 Oct 2026 10:35:56 +0000 MyBB <![CDATA[Open-source Python companion for TIMES workflows (early release, feedback welcome)]]> https://forum.iea-etsap.org/thread-254.html Wed, 15 Apr 2026 01:58:03 -0400 mahmoudmobir]]> https://forum.iea-etsap.org/thread-254.html https://github.com/MMobir/times-data The main motivation is simple: I enjoy Python-first workflows and wanted a scriptable, transparent, version-control-friendly data layer for TIMES modeling. A few points to be fully clear: * This is complementary to established TIMES workflows and tools. * This is not a UI product (yet) — it is currently Python + CLI. * It is open source (MIT) and intended to stay open source. times-data currently supports two entry paths: 1. Build from scratch in Python, or 2. Import existing DD files and edit/validate/re-export. Current capabilities include: * typed model graph (commodities/processes/parameters) * schema + structural validation * DD export/compile for standard TIMES/GAMS runs Verification so far: * tested on all 12 official DemoS models * on models within my active GAMS community license limits, round-trip tests gave exact objective value matches * larger demos compile successfully but exceed solve-size limits in my current license environment I’m using this experimentally in my own global model workflow at Rhodium Group, and I’d really value community testing and feedback. If there is interest, I’m happy to record a short walkthrough video showing: * build-from-scratch path * DD import/edit/re-export path * validation and solve flow Issues, criticism, and contributions are all welcome:
https://github.com/MMobir/times-data Best,
Mahmoud Mobir]]> https://github.com/MMobir/times-data The main motivation is simple: I enjoy Python-first workflows and wanted a scriptable, transparent, version-control-friendly data layer for TIMES modeling. A few points to be fully clear: * This is complementary to established TIMES workflows and tools. * This is not a UI product (yet) — it is currently Python + CLI. * It is open source (MIT) and intended to stay open source. times-data currently supports two entry paths: 1. Build from scratch in Python, or 2. Import existing DD files and edit/validate/re-export. Current capabilities include: * typed model graph (commodities/processes/parameters) * schema + structural validation * DD export/compile for standard TIMES/GAMS runs Verification so far: * tested on all 12 official DemoS models * on models within my active GAMS community license limits, round-trip tests gave exact objective value matches * larger demos compile successfully but exceed solve-size limits in my current license environment I’m using this experimentally in my own global model workflow at Rhodium Group, and I’d really value community testing and feedback. If there is interest, I’m happy to record a short walkthrough video showing: * build-from-scratch path * DD import/edit/re-export path * validation and solve flow Issues, criticism, and contributions are all welcome:
https://github.com/MMobir/times-data Best,
Mahmoud Mobir]]> <![CDATA[IEA-ETSAP Website, Suggestions]]> https://forum.iea-etsap.org/thread-49.html Sat, 17 Aug 2013 02:52:15 -0400 gct]]> https://forum.iea-etsap.org/thread-49.html Delegates and users ask to improve our web site: what are your suggestions?

So far what was our target audience? Mainly users! How can we better serve them?

  • ·        Delegates?
  • ·        Licensed users?
  • ·        Modellers?
  • ·        Other experts?

Do you think that it is important to present our contributions also to non-users, who don't know anything about ETSAP and MARKAL-TIMES? How can our web site become a valuable and reliable source of information for:

  • ·        Journalists?
  • ·        Policy makers?
  • ·        Informed citizens?
  • ·        Associations?
  • ·        Students?

What are we trying to say? What contributions would you highlight and make available to non-users through our web site? ]]> Delegates and users ask to improve our web site: what are your suggestions?

So far what was our target audience? Mainly users! How can we better serve them?

  • ·        Delegates?
  • ·        Licensed users?
  • ·        Modellers?
  • ·        Other experts?

Do you think that it is important to present our contributions also to non-users, who don't know anything about ETSAP and MARKAL-TIMES? How can our web site become a valuable and reliable source of information for:

  • ·        Journalists?
  • ·        Policy makers?
  • ·        Informed citizens?
  • ·        Associations?
  • ·        Students?

What are we trying to say? What contributions would you highlight and make available to non-users through our web site? ]]> <![CDATA[Combine forums]]> https://forum.iea-etsap.org/thread-13.html Tue, 04 Jan 2011 20:17:36 -0500 Pernille.S]]> https://forum.iea-etsap.org/thread-13.html
Pernille
]]>
Pernille
]]>