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

[Bug] Input sliders not visible for transition paths that contains private scenarios #34

Open
robcalon opened this issue Apr 25, 2023 · 4 comments
Assignees

Comments

@robcalon
Copy link

When creating a transition path from private scenarios, I'm unable to see any values in the 'input slider' section of the GUI. This issue does not occur when I create a transition path from public scenarios.

After creating a copy of a scenario I'm aware that no sliders are shown in the 'input slider' section. I normally make these visible by reuploading a subset of parameters of the original scenario. This approach does work for the public transition paths, but not for the private transition paths.

I'm able to modify the sliders within the GUI by clicking the 'year', these changes are persistent as it is still there after reopening the scenario after completing editing. Also, via the API I can modify the parameters of the individual scenarios without raising any errors.

@robcalon robcalon changed the title [Bug] Input sliders not visable for transition paths that contains private scenarios [Bug] Input sliders not visible for transition paths that contains private scenarios Apr 25, 2023
@mabijkerk
Copy link
Member

@noracato would you be able to look into this?

@noracato noracato added this to the Fixes for August milestone Jul 28, 2023
@robcalon
Copy link
Author

A small update:

  1. The option to change input parameters now results in an error 'energytransitionmodel.com is refusing to connect'.
  2. Mixing private and public session ids result in an application error.
  3. Graphs for private/mixed session ids do work and can be viewed.

@mabijkerk
Copy link
Member

@noracato what is the status of this issue?

@mabijkerk mabijkerk assigned noracato and unassigned thomas-qah May 30, 2024
@noracato
Copy link
Member

There are some issues in authentication between the MYC and etengine. This is the result of one of them. My hope is that when I solve these authentication issues for the project I'm currently working on, the issues discussed here will get solved as a result.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants