Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
R
remind
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 19
    • Issues 19
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Redmine
    • Redmine
  • Merge Requests 0
    • Merge Requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Jerome Hilaire
  • remind
  • Issues
  • #41

Closed
Open
Created Jan 20, 2020 by Michaja Pehl@pehlContributor

Weired special case in q_emiTeDetail

https://github.com/remindmodel/remind/blob/08e58efe626352b7963575d3c6e13436e3322dd4/core/equations.gms#L478-L502

I don't see any point in (and am confused by) the OR (pe2se(enty,enty2,te) AND sameas(enty3,"cco2")) part. This would come into play for combinations of (pety,sety,te,"cco2") that are not present in emi2te yet have non-zero data in pm_emifac. This might happen if new data is included in ./core/input/generisdata_emi.put, but is not the case at the moment.
However, these entries would be excluded from the equation in any case, since it sums over emi2te, of which they are not a part. (Incidentally, this sum does nothing productive besides excluding the non-existent cases that were manually included.) Do you have any idea what was the reasoning behind this? I will delete it, unless there's some foreseeable edge-case where this is necessary.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None