Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issue with parameter based Monte Carlo Simulations #1289

Open
1 task done
haha1508 opened this issue May 17, 2024 · 0 comments
Open
1 task done

Issue with parameter based Monte Carlo Simulations #1289

haha1508 opened this issue May 17, 2024 · 0 comments
Labels
bug Issues/PRs related to bugs

Comments

@haha1508
Copy link

haha1508 commented May 17, 2024

Updating AB

  • Yes, I have updated AB and still experience this issue

What happened?

Was trying to perform a parameter based Monte Carlo simulations but kept getting a value error of size mismatch when the tech vectors was being overwritten by the changed parametrized exchanges. After going through the code, realized that the error actually stems from somewhere within the database, I have an activity that has 2 same exchanges (electricity from the US) with different amounts (In the comments, these were used for different purposes). However, these were static inputs and parameter based (the parameter that had no defined uncertainty). Yet, the parameter MCRandomNumberGenerator somehow identified these exchanges to be randomly generated for the Monte Carlo Simulation. However, whenever the indexes are identified in the code, there is filtering to only consider unique activities, leading to one of these exchanges to get dropped and causing the error. In the meantime, combining those exchanges into one fixes the issue, but from a user friendly perspective, it is more preferable to have to 'separate' exchanges representing electricity consumption for different processes (with the comments adding more information on which process is used for what). I noticed that having duplicate exchanges also causes issue with Scenario based LCA, so maybe this is an overarching issue. If the capability isn't there, maybe can add a warning whenever a user has a duplicate exchange within an activity. I noticed that it doesn't break anything within the standard LCA, only for the more involved calculations in Monte Carlo or Scenario based LCA.

image

Relevant errors

No response

Operating system

Windows 10

Conda environment

No response

@haha1508 haha1508 added the bug Issues/PRs related to bugs label May 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Issues/PRs related to bugs
Projects
None yet
Development

No branches or pull requests

1 participant